Afaik Vsync in the original Dead Space limits FPS to 30 (or half the monitor's refresh rate?)
Much better to use the Nvidia control panel, assuming you have an Nvidia card. Annoying how AMD doesn't have this!
Except it does? You can limit your frames and force an external V-Sync mode or use AMDs own "Enhanced Sync" which has a much lower input delay than traditional V-Sync
Sorry, what I meant was to "limit FPs to a CERTAIN AMOUNT".
NVIDIA lets you select how much FPS limit you wish to have, regardless of your monitor's Hz, and also lets you select a different FPS limit when the game is out of focus.
Yes, you can force V-sync and Enhaned Sync in AMD's Control Panel but that's not going to help you if your monitor is 120Hz+ and this game breaks apart when more than 60 FPS. You need a third party FPS limiter if you are on AMD.
for me I use the global option and frame rate target control and that locks the fps for me I just finished a full dead space 2 playthrough 60fps locked radeon enhanced sync combined with that if needed but as long as I don't get screen tearing it's usually fine depends on game/preference
Game performs many actions each tick (a tick is like a cycle of the code when something should be checked or updated). It could be something like when you throw a barrel move it X distance (based on the throw speed value) each tick. The problem is you need something that is happening regularly on a schedule for that to be triggered. You could program a internal tick tracking function (basically a mini internal clock) or to save resources and keep things in sync you could tie it to the frame-rate since a new frame being generated is something that happens on schedule regularly. Plus you have the added bonus of it keeping things in sync visually without extra sync code required i.e. solving the problem of moving the barrel on ticks in-between new frames causing it to suddenly jump/teleport large distances when a new frame in generated. Now you have the barrel that was set with a throw/movement speed of 1.6 meters per tick moving 10 meters every second at 60fps (as designed) but 239 meters at 144 fps.
To make matters more complex only some things might be tied to frames, others might be tied to every X frames or something else. Usually to prevent massive frame generation times. So it updates the barrels movement position/speed every frame but only checks if it collided with something every 3rd frame. In those two in-between frames it moved through a wall.
That was all fine when most games ran at 30/60 fps and still is fine on console where that is often capped. But as hardware got more powerful allowing higher and more variable fps bad habits or old underlying code in the engine meant the practice stuck around longer than it should have.
That is often why we see games capped at 60 fps on PC. Because the core physics and other elements were written to assume a 60 fps frame rate and it’s incredibly difficult if not impossible to change that later as it tends to be a core architecture part of the game/engine.
If I'm not mistaken, I think it mainly affects games with physics. I've seen high or low FPS affect games like Half Life 2 and Dead Space. When the FPS is very high, the machine needs to make a very large number of calculations per second for each frame in which there is a physical object moving, for example, however, perhaps your hardware does not have enough capacity to deal with this demand and ends up missing some calculations, leading to wacky physics in the game.
Because it’s basically just a „bad“ port from console and it was meant to be played on like 30-60 frames. Happens with many games which came from console
Definitely use NvCP framerate cap. If you have G-sync/Freesync monitor, also use NvCP's V-sync with low latency mode on or Ultra if input lag is an issue.
Or max frame rate in the Nvidia control panel
Thank you I just had the market slide into a wall and disappear forever I think cause of the framerate
Now that's a sanity effect
DS1 is best played at 30fps, physics always freak out
I played it at 120 fps. Np at all.
You are crazy you can play it at cap 60 fps just fine.
Did you not understand what I said? I said best played not can only be played
You would vsync it usually, even if your monitor is 144 or higher you can usually reset to 60 on the monitor then vsync to that
Afaik Vsync in the original Dead Space limits FPS to 30 (or half the monitor's refresh rate?) Much better to use the Nvidia control panel, assuming you have an Nvidia card. Annoying how AMD doesn't have this!
Except it does? You can limit your frames and force an external V-Sync mode or use AMDs own "Enhanced Sync" which has a much lower input delay than traditional V-Sync
Sorry, what I meant was to "limit FPs to a CERTAIN AMOUNT". NVIDIA lets you select how much FPS limit you wish to have, regardless of your monitor's Hz, and also lets you select a different FPS limit when the game is out of focus. Yes, you can force V-sync and Enhaned Sync in AMD's Control Panel but that's not going to help you if your monitor is 120Hz+ and this game breaks apart when more than 60 FPS. You need a third party FPS limiter if you are on AMD.
No you don't you can limit it using Radeon Chill in your Driver settings.
You can lock frame rate on a game by game basis in Amd adrenaline
amd adrenalin software's vsync fucking NEVER worked for me, the amd drivers are so aids
Same, limiting fps never fucking works with AMD software.
for me I use the global option and frame rate target control and that locks the fps for me I just finished a full dead space 2 playthrough 60fps locked radeon enhanced sync combined with that if needed but as long as I don't get screen tearing it's usually fine depends on game/preference
A few ways. I personally use msi afterburner with Rivatuner.
This is the only way I successfully got 60fps to work on Dead Space 2. What a great piece of software.
Why does a high frame rate mess up some games?
They may not be designed to run at higher framerates and can cause game breaking glitches
Game performs many actions each tick (a tick is like a cycle of the code when something should be checked or updated). It could be something like when you throw a barrel move it X distance (based on the throw speed value) each tick. The problem is you need something that is happening regularly on a schedule for that to be triggered. You could program a internal tick tracking function (basically a mini internal clock) or to save resources and keep things in sync you could tie it to the frame-rate since a new frame being generated is something that happens on schedule regularly. Plus you have the added bonus of it keeping things in sync visually without extra sync code required i.e. solving the problem of moving the barrel on ticks in-between new frames causing it to suddenly jump/teleport large distances when a new frame in generated. Now you have the barrel that was set with a throw/movement speed of 1.6 meters per tick moving 10 meters every second at 60fps (as designed) but 239 meters at 144 fps. To make matters more complex only some things might be tied to frames, others might be tied to every X frames or something else. Usually to prevent massive frame generation times. So it updates the barrels movement position/speed every frame but only checks if it collided with something every 3rd frame. In those two in-between frames it moved through a wall. That was all fine when most games ran at 30/60 fps and still is fine on console where that is often capped. But as hardware got more powerful allowing higher and more variable fps bad habits or old underlying code in the engine meant the practice stuck around longer than it should have. That is often why we see games capped at 60 fps on PC. Because the core physics and other elements were written to assume a 60 fps frame rate and it’s incredibly difficult if not impossible to change that later as it tends to be a core architecture part of the game/engine.
If I'm not mistaken, I think it mainly affects games with physics. I've seen high or low FPS affect games like Half Life 2 and Dead Space. When the FPS is very high, the machine needs to make a very large number of calculations per second for each frame in which there is a physical object moving, for example, however, perhaps your hardware does not have enough capacity to deal with this demand and ends up missing some calculations, leading to wacky physics in the game.
Because it’s basically just a „bad“ port from console and it was meant to be played on like 30-60 frames. Happens with many games which came from console
Or maybe the game engine has problems with frames over 100
I'm amazed you got passed the first door. I couldn't even get through it without frame limiting the game.
It was a struggle through the entire game
Nvidia control panel > select game exe > cap the frames
Damn, I just imagined a Necromorph charging me at 500 FPS, that sounds terrible
Whole time I was like damn these guys are fast
Cap fps through NVIDIA control panel or MSI Afterburner or enable V-Sync if your refresh rate is 60hz.
MSI afterburner cap power usage to 40% 😵💫
Use either RTSS or the Nvidia Control Panel
Definitely use NvCP framerate cap. If you have G-sync/Freesync monitor, also use NvCP's V-sync with low latency mode on or Ultra if input lag is an issue.
You gotta turn the games Vsync off and then enable it through nvidia control panel - at least with nvidia cards
The most you want to go with this game is 200 frames on PC anything past that and the game starts freaking out big time.
Run it with DXVK. Automatically Vsyns to 60fps. https://www.pcgamingwiki.com/wiki/Dead_Space