Bouncing character issues

[D.M.E]

I don't remember this problem before and I'm wondering if it's cause I was on a dvd copy then and now it is a Steam copy. I downloaded patch 1.03 but it says not for Steam, Is it available on steam? Is it the issue and if not how do I fix the problem?
Cheers.

[realist123]

I had bouncing characters. If you have a decent PC just max out all the graphics settings that is what fixed it for me. Might not be your solution.

It might just be that you have to max out the refresh rate, but to be safe I maxed out everything in the graphics options and it went away for me. I toned down some things like shadows later on but it was still fixed.

[D.M.E]

I'm averagng 150 to 200 fps on max settings so I tried putting v-sync on to limit the fps and that seems to have helped, I got the idea from a thread 2 or 3 pages back, Thanks for replying.

[PaulieZero]

I was getting bouncing NPCs on Windows 8 using DX10. When I switched to DX9 it stopped.

[D.M.E]

Originally posted by Team Merica':

I was getting bouncing NPCs on Windows 8 using DX10. When I switched to DX9 it stopped.

If I find it's still happening I'll have to try this, thanks.

[Muzle84]

Your PC is just too powerrful for FC2. Enable VSync and nobody will jump anymore.
EDIT: Doh! I should read posts more carefully, sorry.

[D.M.E]

:)

[Madwand]

Originally posted by Muzle84:

Your PC is just too powerrful for FC2. Enable VSync and nobody will jump anymore.
EDIT: Doh! I should read posts more carefully, sorry.

No, you were the first person to say it's from too powerful a PC which makes the vsynch comment make sense.

[D.M.E]

Originally posted by Madwand:

Originally posted by Muzle84:

Your PC is just too powerrful for FC2. Enable VSync and nobody will jump anymore.
EDIT: Doh! I should read posts more carefully, sorry.

No, you were the first person to say it's from too powerful a PC which makes the vsynch comment make sense.

His suggestion was correct but what he meant in the edit was that when he suggested it he hadn't got to my post saying that I'd found a different thread suggesting that was the case and that V-sync had solved it for me.

[Firefly in the dusk🌙]

Setting vsync on is not enough depending on your hardware, you also have to cap the framerate to 60. Vsync on + refresh rate set to 60 (as opposed to higher) worked for me.

[D.M.E]

Originally posted by Alex M.:

Setting vsync on is not enough depending on your hardware, you also have to cap the framerate to 60. Vsync on + refresh rate set to 60 (as opposed to higher) worked for me.

Good too know, Thanks.

[Jayne Cobb]

So my takeaway from this (just reinstalled after a couple of years) is that the issue can be fixed by messing with frame rate and V-Synch, and every machine may have their own sweet spot. Yes?

[D.M.E]

[Firefly in the dusk🌙]

Not really a sweet spot, basically if you go above 60 fps the physics engine seems to go nuts. When I mentioned "depending on your hardware" I really meant "depending on your monitor". If your monitor supports refresh rates above 60 you want to set the refresh rate to 60 before turning on vsync. If your monitor supports only 60 or lower, then just turning on vsync is fine.

[D.M.E]

Originally posted by nashathedog:

[Archangel]

Originally posted by Alex M.:

Setting vsync on is not enough depending on your hardware, you also have to cap the framerate to 60. Vsync on + refresh rate set to 60 (as opposed to higher) worked for me.

Confirmed on Win10 with a totally OP CPU and GPU. :P