Yup:
2 Likes
Frame rate cap doesn’t prevent the issue, just makes it less noticeable if you throw away half your frames at all times instead of just when moving. If I put my settings up higher I get consistent 70 fps while the camera is still, but 35-40 when it is moving. If I limit to 60 fps, then I get 63 when the camera is still and 35-40 when it is moving. Not really an improvement. I have to lower my quality to get to 120+ fps when still, so that even when I move the camera I can keep steady at 60+. Then the issue will be masked if I set a 60 fps limit. But then I have to play with a low resolution, low framerate, low quality experience even though I could be playing at higher settings with good quality and decent framerate if not for this issue.
Here’s what my framerate graph looks like on decent settings and 60 fps limit (for some reason locks to 63 according to the game bar overlay). You can see I’m still dipping way down if I don’t lower my graphics a lot:
This is made even worse by the fact that there is another bug that makes all healthbars disappear if you set your gameplay resolution scale to anything other than 100%. So now I have to lower my entire screen resolution to get decent framerates which makes the UI ugly as well, and makes all my other windows get messed up every time I alt+tab.
1 Like
Well sh… I just created a new topic and didn’t see this one. I have frames limited via Nvidia’s Control Panel, not the in-game limiter. I’ll try switching that and see if that makes any difference.
it depends how powerful your GPU is, if 60 fps leaves about 40% utilisation free then panning doesnt cause the terrible frame times.
60 fps leaves the 40% headroom on my rig to completely eliminate this horrible issue. my workaround wont work for every system and is exactly that, a work around. They need to fix this as its an issue for everyone atm.
You need about 40% headroom for panning to be smooth. as a test cap at 30fps. although it wont look as smooth because … its 30fps it will stop all the juddering and skipping you get from the frame time issue.
Yeah, I suspected ~20% was not enough, but even if I go down in render scaling to 50 or less, I still get drops from 60fps. There’s something wrong with how the game engine handles panning right now because what should get taxed the most is the CPU as it should be the one recalculating what’s in the scene.
I think right now the engine has some issues with CPU under-utilization.
Don’t think it helps that the second you pan all the tree models start swapping 
noticed this too, it’s very distracting. But for me not all trees change models/LOD and I don’t have the fps stutter when panning the camera. Runing on Win10, 4790K, 1080ti, 16gb RAM
this is true. while capping the framerate made the game playable, I noticed the issue once the other day. Pressing the windows button (or alt tabbing) and going back made it go away but thats just an inconvenient workaround. The framerate cap will help but doesnt resolve the underlying issue.
any posibility to fix that sht… i want to play the game properly!
i cannot play the game in full low with a gtx 1660oc + ryzen 3600x
thats really bad!
it seems to happen with newer GPUs and/or on resolutions higher than 1080p. I have a very bad stutter when panning on a 3060 laptop 1440p resolution, but I get very smooth panning on my 5-year old PC with 1080ti and 1080p… both are running the game on ultra and 144Hz
Thanks, all! We are 100% aware of this and working on a fix. Appreciate the diligence!
5 Likes
reset nvidia options and dont change anything
after that select the first option
leave the app to decide 3D configs
thats it
vsync in 120 fps and enjoy
You mean Turn ON V-sync in-game and limit fps to 120 or just limit fps to 120 without turning on V-sync?
Turn vsync on with limit of 120fps
hope they fix it soon
please fix it!!! hope they fix it soon
We are aware of performance issues while panning and looking into it. Thanks, all!
1 Like