i fast reaction wrote:it's not a cpu bottleneck, it's a gpu bottleneck that occurs due to how certain parts of the map were made. the engine is fine above 240fps, its source.
you can play with no fps cap and vsync disabled by adding the launch option "+fps_max 0". you can only remove the cap entirely or set a cap lower than 144. nothing in between will work.
you will likely find playing at 144fps locked to be more responsive in many areas than unlimited when your framerate falls under around ?288? as the gpu being fully saturated will cause you to start filling the pre-rendered frame buffer.
at this time only a 2080ti with high clocks playing at 720p on minimum settings will consistently hold 240fps but you may find in some places you dip slightly under.
I excluded any GPU bottleneck by creating custom resolution and using Lod Bias, so my GPU usage was around 40% at the worst! And the CPU couldn´t still handle the 240fps, no matter what. In some areas it will go to 300fps easily, in other areas It always drops to 140-150 no matter what. All that inconsistent framerate only hurts aiming, big time. Having dips from 240 to 140 is atrocious for muscle memory, I would rather cap it. The engine isn´t clearly optimized for 240hz, because devs didn´t bother to tweak the stability above 144, it floats for no reason at all, even by just looking at the sky.
Exactly what happens on Battlefield V too, wich was designed and tweaked up to 200fps only (the maximum framerate cap by default), and Black Ops 4 aswell, wich suffers from the same problem as Apex, floaty framerate.
If you lock framerate to 138fps on 144hz monitor + Gsync/Freesync on these modern games, you have a better experience than with uncapped + 240hz
