07-29-2020, 08:28 AM -
The 60 FPS patch shouldn't be causing this, I've never seen this issue before in fact, regardless of using patch or not, that's very weird. Maybe this is a recent bug/regression? You may want to try with some random version from 1 or 2 months ago to see if that's the case.
The settings I mentioned have to be that way, if some tutorial told you otherwise it's wrong. If anything, you can test Thread Scheduler On vs Off to see what gets you the best performance but you should get it with it Off as I mentioned. Frame Limiter makes no sense because the game limits itself, you're just adding extra latency for absolutely nothing, Changing VBlank Rate only messes up logic since the unlocking is done by the patch and doesn't require it. Approximate XFloat isn't on UI because it's supposed to never be disabled, things like that can happen when you do, even though it may not be the cause for that specific bug.
The settings I mentioned have to be that way, if some tutorial told you otherwise it's wrong. If anything, you can test Thread Scheduler On vs Off to see what gets you the best performance but you should get it with it Off as I mentioned. Frame Limiter makes no sense because the game limits itself, you're just adding extra latency for absolutely nothing, Changing VBlank Rate only messes up logic since the unlocking is done by the patch and doesn't require it. Approximate XFloat isn't on UI because it's supposed to never be disabled, things like that can happen when you do, even though it may not be the cause for that specific bug.
Desktop: Ryzen 7 5800X, Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
Laptop: Ryzen 9 5900HX, Radeon RX 6700M, 2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350, Radeon R9 280X, 2x4G DDR3 1600MHz, Manjaro Linux
Laptop: Ryzen 9 5900HX, Radeon RX 6700M, 2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350, Radeon R9 280X, 2x4G DDR3 1600MHz, Manjaro Linux