There are also weird things happening with framegen on Geforce Now, which users cannot fix and is completely totally 100% vanilla using a clean virtual machine. The FPS counter tells me that I’m getting 120fps but I can feel and see that it isn’t. Limiting my FPS to 60 and then turning on framegen suddenly drops the actual ingame FPS to 30, so something is messed up. Switching to Windowed mode as discussed above makes whatever is causing it to feel wrong to go away and it works as it should.
Just wanting to add onto this somewhat, I’ve noticed that with AMD FSR and AFMF both are disabled due to the the software not being able to properly detect the game or something? Not 100% sure but my performance is definitely lower than it used to be.
I’ve lowered my resolution to try and get FSR to work, but that shifts some of my ingame ui hud elements to different spots on the screen and the overall picture looks more blurry which hurts my eyes.
you should create a new topic in the Technical support forum
DLSS and FSR is two things totally different.
well it seems i have an update (between my own reaserch and reddit)
seems to be a VRR issiue. So it seems when they put on the multiframe gen options (x2,x3,x4) even thou for 40 series its greyed out for x3/x4 i think the game is switching between these techs (or trying to) which would explain why everything feels worse, and theres alot more imput lag when the game changes frame rate.
so for a stop gap, turn off VRR and use frame gen
OR turn off frame gen and keep on VRR
Obivously not a great soloution, but till fatshark fix this issiue, its a decent stopgap soloution. HOpefully we get a hotfix next week.
I’d say to help diagnose the problem, the teh team over at fatshark should use an older version of the game (pre nightmare and visions) and allow others to use this older patch (using the beta funtion) and see if the problem is gone.
So annoying. hopefully it gets fixed next week.
Can confirm that something’s definitely broken. I tested FG and it appears that Reflex is not working properly or at all. Notice how my Nvidia overlay shows my fps is at 173 - this should be impossible as reflex caps the frame rate somewhere below the monitor’s refresh rate, my refresh rate is set at 180hz and in all games I’ve tested the reflex cap is 171. So at the very least the cap isn’t working properly. I did try the fix recommended in this thread but it didn’t work. I’m also using G-sync and have an RTX 4060 btw.
Sorry for the low quality image idk why it’s compressed like this.
yeah seems like a placebo effect on my part.
played a round and even with gysnc off, the problem came back. it definaly is an issiue with dlss/framegen.
I did notice somat simlar like yourself @Syrax i cap my fps to 141 (as i got a 144hz monitor) and it was capped after hte patch at 138 which was wierd.
So again back to zero it would seem. HOpefully this gets adressed and fixed soon.
Its good this issiue is gaining some traction though, hopefully it aids in the speed of a fix
Okie scrap that: done two rounds with gsync off
Dlss on (quailty) Frame gen on (x2)
seems to be holding steady now (allthough without gsync game feels wierd.
SO YMMV but this temp soloution is working for me at least, if nothing else give it a try.
Tried FG (x2) with G-sync disabled and Reflex won’t even cap the fps at all, again this should be impossible unless I’m missing smth. Idk if this matters but I only disabled G-sync, without disabling the monitor’s VRR. Still given this, it seems to be a problem related to FG+Reflex implementation.
Note that when using FG+Reflex (Reflex is mandatory for FG to work) it implements its own fps cap that overrides your fps cap. It is different depending on your monitor’s refresh rate. In my case for my 180hz monitor the FG+Reflex cap is 171fps. In your case for 144hz it’s 138 fps so it makes sense, because the fps cap you set at 141 is overridden by the FG+Reflex cap.
100% is a reflex/fg issiue. Thank for you making sence of the FPS differences.
I would go into nvidea control panel (or RTSS if you wish) and cap the fps manually. I do it in nvidea control panel (3 fps below the refresh rate of my monitor) not sure about 180hz, could be 177 or 171 in your case.
Try capping it ureself and see if it makes the game playable for yourself.
but yeah that info you provided acctually helps me make sence aobut what is going on.
well i have fg on, and dlss and no gync, with a cap of 141, and my fps counter is 140-142 in game, so it seems to have done something? i no longer have the random FPS differences that happen just after a 1-2 ssecond hard stutter.
again YMMV, as everyone has different software,hardware, configs etc.
but 100% they did something in the update which messed with Framegen. Maybe they can figure it out for a more better soloution. i.e before the update as it was fine before then.
Based on further testing it appears that Reflex is working at the very least without FG enabled as using it lowers latency. But the FG+reflex fps cap most definitely doesn’t. I have no idea if this is intended behavior as this is the first game I’m aware of that forgoes the FG+reflex fps cap (be it intentionally or not)
Regardless I don’t know if this should be considered its own issue and needs its own forum thread or if it goes hand in hand with the frame gen issue. I will create a separate post if deemed necessary. Anyway it would be helpful if the devs could confirm whether the reflex fps cap removal is a feature or a bug.
TLDR: for folks scrolling, Take off gync, Cap FPS to 3-4 fps below ure monitors cap, Turn on frame gen, and turn on dlss. The problem goes away, but its not perfect, but tis better then the stuttering thats happening.
So i went down the rabbit hole again.
seems there is an issiue with others (not everyone) and various adhoc fixes solve the issiue but do not fix it. THis problem only started to happen when fatshark introduced the x3/x4 options in the options menu. Its got to be there.
EIther disabling g sync or frame gen fixes the problem, but then it creates its own issiues, but is 100% better then random hard stutters which lock the FPS at lower values which looks like abouslte trash.
Perosnally? I think they should remove the multiframegen option in the game. Revert back to the previous iteration (which was just on and off) and see if the problem is gone.
even if it was put into the beta branch just for us to test, as the problem starts off pretty much immeidatly, so would be easy to see if this fixes it.
We’re looking in to this! 
2 Likes
excellent =]
Nvidia GFN FPS counter going all over the place and reporting impossible and untrue numbers with VRR off and 2x Framegen on, all while feeling like 60-80fps (i.e. what I am getting without framegen). Watch FPS all over the place | Streamable
This was with ingame FPS cap of 120. Something is very wrong with framegen.
thats a bit of ajumpy situation there. jesus.
Well there investigating it, but if i was in charge of technical side, i’d just roll back the changes on the options side (the “new” dlss changes) and see if its fine.
Was before the update anyway. but yeah those numbers… something is very wrong
heya team
My FPS is horid.
Since yesterday 15-20 fps no matter what I turn off/on on the options
darktide_launcher.log (689.7 KB)
I have intel and Nvidia. no AMD anywhere.
After the last patch, suddenly I am runing the game on 15 fps
DLSS on only, Cap 90, settings on low
Hi Julia, any news? (Hotfix hasn’t changed anything yet)
1 Like
Let me see where we’re at!
Waiting to hear back from QA. 
2 Likes