Holy VRAM batman!!!

The freezing is related to the comms server, has been verified by many users (you can also check your log files) the issue isn't client side.

As far as Vram usage, this game has always been hungry. Am currently using 5gb on my 1080TI, that is in VR with everything cranked up, am out in the middle of nowhere parked up on planet.

I've been monitoring my VRAM usage, it'll creep up instance after instance as if the previous instances memory is not getting flushed. Once it hits the 7GB mark on my 1070 that's when freezing occurs.

Not saying the comms server thing isn't bugged either however it's definitely video memory causing the freezing from the behavior I'm seeing in MSI afterburners graph.

There is a temporary workaround though, if you go into the options>graphics and just hit "Apply" it'll force a flush of the VRAM.
 
I've been monitoring my VRAM usage, it'll creep up instance after instance as if the previous instances memory is not getting flushed. Once it hits the 7GB mark on my 1070 that's when freezing occurs.

Not saying the comms server thing isn't bugged either however it's definitely video memory causing the freezing from the behavior I'm seeing in MSI afterburners graph.

There is a temporary workaround though, if you go into the options>graphics and just hit "Apply" it'll force a flush of the VRAM.

Hi, yeah that Vram issue has been around for a while. At one stage is was terrible for many VR users, I had a 1070 at the time, the game would be unplayable unless I restarted the game after 10 jumps or so. Took them ages to fix it, it still does it, but nowhere near as bad (for me at least)

I can leave the game running for 48 hours without issues on my 1080TI. Nice tip about the Vram, wish I'd known back then

Here's an example https://forums.frontier.co.uk/showthread.php/296544-Freeze-amp-Crash-likely-due-to-VRAM-issues
 
Last edited:
Hi, yeah that Vram issue has been around for a while. At one stage is was terrible for many VR users, I had a 1070 at the time, the game would be unplayable unless I restarted the game after 10 jumps or so. Took them ages to fix it, it still does it, but nowhere near as bad (for me at least)

I can leave the game running for 48 hours without issues on my 1080TI. Nice tip about the Vram, wish I'd known back then

Here's an example https://forums.frontier.co.uk/showthread.php/296544-Freeze-amp-Crash-likely-due-to-VRAM-issues

My VRAM usage never went above 5GB prior to 3.3 even with supersampling enabled. With 3.3 I've been playing through Wine on Linux up until now, so haven't noticed the VRAM issue until I started using Windows again, I wouldn't say this is the same problem as in that thread. I can pretty much reproduce the freezing which correlates with almost running out of VRAM although I don't feel like uploading an hours worth of video jumping and landing on planets showing how.
 
Yeah I’ve been bumbling about doing pve stuff in spare time and it’s annoying enough (I also have the 1080ti which runs most things smoothly) but this will really suck for pvp. Been a steady thing since the update too. CZs are still completely broken as well. This time around nothing seems to spawn.

I thought that until I realised that your set 9km outside of the CZ. So there is nothing to see for a minute until you fly closer..

Flimley
 
the BBC micro did not have an internal disk drive. my father bought a 5 1/4 and it was cased into polystyrene, sitting near the bbc with the wires showing out. he had to cut into the bbc plastic casing to allow the controller to be connected to the floppy drive.
.............

Was his name Heath Robinson? - My disk drives were connected via the 1Mhz bus.
 

Deleted member 110222

D
the BBC micro did not have an internal disk drive. my father bought a 5 1/4 and it was cased into polystyrene, sitting near the bbc with the wires showing out. he had to cut into the bbc plastic casing to allow the controller to be connected to the floppy drive.
i played elite on a 80x86 though.
i remember though in 81 or 82, i used a drawing program on the bbc that allowed saving "frames" and then animate them. must be 82 because there were colors, when he bought it it was monochrome.

we re not getting younger, no, we re not.

also, it s not 25th birthday, it s 35th

It's the anniversary of Frontier Developments, not Elite 1984.
 
OK - back on topic

In my latest freeze \ pause I had gpu monitoring running - you can clearly see the pause period - note that the VRAM memory usage before and after the freeze was 3825 - I had not annotated it before posting, sorry. (Card is 1070 with 8GB)

mHMtQIi.jpg
 
In my latest freeze \ pause I had gpu monitoring running - you can clearly see the pause period - note that the VRAM memory usage before and after the freeze was 3825 - I had not annotated it before posting, sorry. (Card is 1070 with 8GB)

Interesting! What happened to your network bandwidth / drive activity during that period? Having task manager open as well as GPUz would be a useful comparison.
 
After spending the last two years exclusively in VR playing ED I must say that ED was the best VR experience and game out there.
After 1500 hours I experienced no problems with FPS or game visuals and was always blown away by how beautiful and great the game was in VR.
Now after the December update Frontier has totality ruined Elite Dangerous in VR, I will explain

1) Has-Res was fluid with no noticeable drop in FPS, after update I am getting a FPS of 45 that makes visuals distorted and blurry. Other ships id tag will ghost across the screen as you move your ship
2) I have many hours running around Dav’s Hope before the update in VR without any FPS drop off now after update I am getting 45 FPS, everything just gets blurry when driving around Dave’s Hope now it’s almost unplayable.
3) After update we are all getting game freezes, not good when in Has-Res and getting shot by pirate
4) With the VR screen so close to your eyes and now Looking at Spaceports or yellow mining hot spots it’s now so bright that it hurts your eyes. After looking at an opal hot spot and taking off my VR I saw white spots for a couple of minutes.



Getting a FPS of 45 in VR it’s very hard to play the game for very long, it messes with your head and eyes all the stuttering and blurriness, I start to get headaches very quickly.

The brightness must be harmful in VR it’s not like you can just look away with the headset on

We all see the game performance drop off and speculation to the cause of VRAM, server load, hardware ect. All I know for sure is this started after the last update and the main update change that may cause this is the new Lighting scheme.
With all the new cockpit lights, Has-Res fog, Skybox crazy colors it must put a higher demand on computer rendering.

The VR experience is what keeps me playing Elite Dangerous but now it feels like it’s totally broken and beyond repair.
It seems like this year may not be known as Beyond but BEYOND REPAIR.

My System
Vive then Vive Pro
Intel i7-8700K 3.7GHz gen 8
16 GB
1080 GTX Graphics Card
 
Last edited:
  • Like (+1)
Reactions: NW3
the BBC micro did not have an internal disk drive. my father bought a 5 1/4 and it was cased into polystyrene, sitting near the bbc with the wires showing out. he had to cut into the bbc plastic casing to allow the controller to be connected to the floppy drive.

Didn't notice anyone on this forum say it DID have an internal drive. I certainly didn't.


i played elite on a 80x86 though.
i remember though in 81 or 82, i used a drawing program on the bbc that allowed saving "frames" and then animate them. must be 82 because there were colors, when he bought it it was monochrome.

we re not getting younger, no, we re not.

also, it s not 25th birthday, it s 35th

I played on a BBC B. We had, as you say, an external SINGLE sided drive, in which one could actually take out the disc and insert it upside down to get the other side... like an LP, except floppy ...
There were double sided drives, but they were more expensive. Didn't have any polystyrene though, was a metal case with a twist-lock on the front... It looked a lot like:

product-111265.jpg


The Model B was released in 1982 with colour. Not sure what is this color thing you mention, but it sounds painful. The model A was released in, I think '81, but that had colour too.

You are right about the 35th year though... I saw it in another thread and it stuck. For that I apologise.
 
I can't really say much about VR experience (my headset hasn't arrived yet cause UPS are lazy ...) but I've spent a fair bit in ch4 Beta and had no issues at all. I went on my holidays on the day the live patch hit the servers.
After 3 weeks when I got back home and after update all the problems started. I updated all my drivers and so on and the freezing is still present. I think it's on FDev side, so they have to fix this mess.
 
I don't know if this is related to what the OP is saying but when I'm in the hanger or inside the starport, the heat on my graphics card goes up to the max or nearly max (~75C) what the card allows (afaik). ED is not the only game that has this. The tank warfare game added a blank background garage that helped some.

When I exit a port, the graphics card heat settles down and it drops about 40%. I try to keep this in mind when I step away from the game. I'll go to the System Map before leaving and switch to the desktop. The heat drops 30C or more when I do this.

Fwiw, I get the stuttering and short freeze-ups still since the last big update. I hope they fix that soon.
 
Oooooh it isn't just me??

I too have been getting some remarkably LONG freezes during gameplay, I'm out in deep space scanning, and I get freezes for up to 30 seconds now - not often, but at least 3-4 times I can recall. No reason for them, not doing anything special, but the game just...stops. And then comes back as if nothing has happened.

I'll try and grab info if it happens again now I know it isn't just me :p
 
My hunch is that there are two factors at play here: some older/lower VRAM GPUs are having trouble with something about the new graphics implementation, and at the same time something is going on server side to freeze the simulation on a global scale.
 
My hunch is that there are two factors at play here: some older/lower VRAM GPUs are having trouble with something about the new graphics implementation, and at the same time something is going on server side to freeze the simulation on a global scale.

I'm having trouble on a 1070, while not the most powerful or latest GPU on the market it's not exactly too old or a low end potato.

Strange thing though, with my alt account near Sag A* I'm not seeing VRAM go crazy and it's actually utilizing my system memory more. Maybe this is a bubble thing?
 
Haven’t checked but for the first time the game is frequently freezing up for me.

Same, I get like 10 second+ freezes now, then when it comes back it screws up my controls.

I will be sending a link of this to the Bug report section, this should be sufficient numbers to prove there is a problem.
 
Last edited:
Interesting! What happened to your network bandwidth / drive activity during that period? Having task manager open as well as GPUz would be a useful comparison.

I regularly leave task manager open on another screen to monitor activity (usually looking for bottlenecks) and network activity is usually unchanged. Certainly my PC doesn't shut down all activity, if I'm playing a youtube vid or downloading something that traffic is completely unaffected. I've yet to have a lockup while on the processes tab and am reluctant to click away from the game while it's locked up because that starts the engine running again in the background. There is no noticeable flurry of activity after the lockup either, nor any particular pattern of where or when it happens.

The game is waiting for something pretty small I think.
 
Back
Top Bottom