I’m getting an issue where the game inevitably consumes all avail VRAM (watching with SpecialK). Once it happens it drops to ~16-25fps and never recovers.
Is this a known issue? Is there any way to reduce the percentage of VRAM the game tries to use?
Also to note that I just reformatted the whole comp to see if it would help as I noticed DWM consuming ~1gig of VRAM. Did not help. DWM is a VRAM monster.
Playing at 4k with high settings and DLSS Balanced. I’ve also tried DLSS performance to see if that helps (doesn’t)
I’m sure it will, although with DLSS running on performance is equivalent of running 1080p IIRC and that was the first things I tried.
It seems pretty strange, like the game is leaking vram or misallocating more than is avail.
Seems like the game tried to allocate exactly 100% of VRAM, watched it happen - the problem being that DWM and some other stuff consumes at least ~500MB. It would just hover right above 16GB of consumption, no higher.
It seems to be a bug. It wasn’t diving into huge masses of VRAM that don’t exist; it would just comfortably site at like 5% greater than max killing performance.
Also of note: Game will run at 70+fps for 20m or so before it exhausts avail vram. There were no textures or anything that could be unloaded from VRAM in 20m to prevent exhaustion?
While debugging I also noticed that when using a dualshock wired the game appears to constantly flip between dinput and xinput and certain menu actions are broken, so going to switch to steam input to stick to xinput. Doubt it’s related, just another bug.
I suspect that the vram issue is a memory leak issue related to ray tracing at 4k, but will continue testing.
It’s an old problem that FS hasn’t been able to pin down:
It’s gotten even worse for me this patch with the game eating up VRAM while I’m in a party and in the Mourningstar or just entering any menu. I have to restart the game after every couple of games. For reference my specs are:
i7-10700
3070 8gb
32gb RAM
UWQHD screen
It’s hilariously bad when the game sits at 30 FPS and below looking at a static talent tree screen. I’ve noticed that the performance sometimes recovers when I’m by myself and successfully matchmake.
Ya those are similar to the issue I’m encountering.
Watching VRAM consumption using SpecialK, it’s pretty obvious that VRAM use spikes after menu use (sometimes recovered) and after loading any new area. Critically, even loading back to an area visited before compounds VRAM consumption. If opening a menu spikes you up to ~100% consumption, the game will not recover.
Base loading into game (now playing at 1440 w/ raytracing) starts me at ~5-6GB of VRAM. Loading any menu seems to spike me up 1GB which is sometimes (but not always) recovered after closing the menu. Loading into mission spikes 1-2GB at the beginning of the mission, more throughout (of course). Then loading back to base seems to spike ~4GB. Throughout all of it, very little VRAM appears to be recovered. With 16GB of VRAM you can play 1-2 missions before needing to restart the game.
Running at 1440 I get ~80-100fps without framegen using DLSS quality pre-vram exhaustion. Post exhaustion I get 50-60fps; but the frame pacing becomes terrible.
At 4k, I’m usually running 70-80fps (although have played less at 4k so probably varies by map) pre-vram exhaustion. Post exhaustion I get 20-40fps, sometimes dipping into teens if I continue to play.
Once exhausted it does seem like some kind of garbage collector kicks in but it lets you sit at 105% of VRAM capacity, presumably constantly swapping out of system ram.
Wondering if playing with gsync on a 120hz display impacts the rate of consumption; if it’s a bug, is it related to fps?
Something is broke. Garbage collection, or something, the game doesn’t seem to know how to recover vram effectively.
Hmm, I also play with g-sync (or more accurately a g-sync compatiable screen running g-sync, so no actual g-sync module). I have g-sync on and force global v-sync via Nvidia Control Panel, but was getting problems before I forced global v-sync. Though if it was a g-sync problem, you’d expect more reports, but maybe I’m overestimating the amount of people using it.
I kind of doubt it’s actually related, although gsync has been causing issues and crashes in other games as of the last few nvidia drivers. Reaching at straws but I’ll try disabling tomorrow, locking to 60hz, and see if I get any results.
That issue was a bug with nvidia’s drivers. It seems to have been fixed with the latest one as I’m not getting any crashes with it. There’s a megathread up top instructing players to not use specific driver version.
Ya it was grasping at straws and didn’t solve anything. In fact it uncovered other issues.
Running at 60hz frame pacing becomes terrible regardless of framegen being on or off, with 1% lows consistently being ~30fps. Uncapping the framerate by running again at 120hz got my 1% lows up to ~60fps with an avg fps ~90.
Further, experimenting with framegen uncovered issues there as well. Back to 120hz w/ gsync framegen actually lowers fps and further destabilizes the frame pacing. With framegen off I get ~90+fps in base. With framegen on I get ~70fps in the same. I tried starting the game fresh with framegen on and achieved the same results.
I suspect some of this is due to having ray tracing enabled, but it seems like there are deeper issues with VRAM garbage collection (or whatever the term in this context, in my field VRAM has garbage collection functions).
I also suspect that the VRAM issues were always present and are just exacerbated by ray tracing being on. Potentially the same for all the frame pacing issues.
For reference, I’m running the latest Nvidia driver at time of writing which is 576.80. Nvidia has notoriously had a lot of issues in the last handful of driver releases, worth investigating.
The users you referenced appear to be experiencing the exact same issues, although they weren’t measuring VRAM (not easy to do if you aren’t comfortable with tools like SpecialK).
Also communicating with support, all the same stuff as here.
Oh I didn’t know they had a vid on this. Just went and watched it (thanks) and what I’m experiencing seems far worse than what they uncovered. Maybe it got worse with updates.