Edit:
I upgraded the motherboard, CPU, and PSU, split 32GB RAM to 16GB for two system, and moved NVMe drive without clean install. Also, ReBAR isn't in use for both setups.
With this, 30 fps it looks to stutter a bit, but unlocked up to 60 fps, it doesn't stutter or I can't see it at Ultra with DLSS DLAA (after a few minutes, as the first few minutes it does). Tested twice to same result. Its possible with the previous older combo of parts that this may be the same as higher fps wasn't tested there. But, went all over the map and after the first few minutes, couldn't see any stutters at higher fps. With a clean install, they do a full shader compilation so it should be the same that way.
There are people that understand performance incorrectly with this game such as seen on Steam. If you have an AMD or Intel GPU, you will have worse performance as CPU usage will be far higher without DLSS. They don't have the others implemented. Maybe they will do another patch with one or both of the other two in time but that is unknown. It could be that a higher core and thread CPU may offest lack of DLSS but this wasn't tested. Fantastic CPU cooling or alternative to stop throttling may as well but also not tested.
RAM speed has no influence*. Tested with higher values and lower values at 30 fps to no difference.
Using NVMe at plenty of speed so storage speed also has no influence*.
PSU has no influence*.
Motherboard has no influence*.
OS version has no influence* as I've previously tested the demo on Linux although the demo is not reflective of the release since many performance changes in the game were made since then.
CPU. High end, high cores and threads might offset needing DLSS. But, I'm not testing that. If you have a lower core and thread CPU, and AMD or Intel GPU, you have a double negative disadvantage here. However, a CPU that doesn't throttle either high or low end will do better at higher usage anyway and will have an advantage there.
GPU. From what I understand from other posts, GPU high end vs low end ultimately isn't of any real influence with stutters. Just produces higher or lower fps. All my tests and reflections here here are run on the same GPU. Not testing another at this time.
Mostly it looks like DLSS and how fps is used are necessary for less stutters. Certain monitors may possibly also introduce a problem. System problems like cooling not working properly, dust, bad OCing, issues with the hardware itself such as Intel 13900k and 14900k CPUs, or other issues could also be a problem for stutters. In-game quality settings may be useful in helping depending on the system.
*Obviously, problems where these things are not working correctly with the above no influences could influence. No influence is to be understood within reason.
As there's a lot of stuff in computing today, I may have missed something.
Original:
The simple answer is: Yes it still stutters. More or less depending on the computer. Stuttering is not really a simple answer though.
They tried their best, working on it for 4 whole months after release. Considering this is Appeal, I expect no further patches (but never know as that was a lot more work on patches than Second Contact).
I restricted to 30 fps though and that can act weird in some game over eg 60 fps. This was not tested here by me.
The consoles, when I tried the demo there, did a ton better. So, if it bothers you, that would probably be the better way to go if you can go that way.
I did not test it on Linux and the experience could be different (therefore better is a possibility) as they worked on Steam Deck support after release.
Used the default dx12. When I did test dx11 previously, whenever that last time was, it wasn't any better for me.
Higher quality settings can cause stuttering etc from modern day hardware throttling. Etc. So, its not always the game at fault. Throttling can be a manufactuer or user created situation.
If you want low CPU usage, have to use DLSS. That's about all it does here is highly lower CPU for whatever reason. High CPU use has more potentional to cause stutters from CPU throttling.
Post edited 2 days ago by echoVolume
