How this works with multiplayer racing, I have no idea. thats also why the game with only teh FPS command runs faster. 50/60 than means, that the game plays SLOWER. If you have a lot of cars and particles on screen and your frame rate dips to 25 fps, your car in game will take longer to get from 0 to 60. Now when u are ingame but have only, say, 50 fps mostly cause of perf issues, low OC, or simply the PC you are using isnt strong enough, then the gamespeed will change. If you uncap the frame rate and run the game locked at 60 fps, the world will run at 2x speed.

If your computer is slow and runs the game at 20 fps, the world - your car, everything - dips to 2/3 speed. It appears that the speed at which the game simulates the world depends entirely on the frame rate. If your PC can’t handle it and the game dips down below 60fps, you’re not just going to see dropped frames, you’re going to run into actual slowdown of the entire simulation process, the same way that the physics and simulation were speed up when running the game at 60fps on the 30fps simulation cycle. I forced some anti-aliasing on in the NVIDIA control panel to play around (which works - FXAA and a bit of MSAA added in don't appear to break anything) and, after turning it up, found out that it appears *THE GAME ACTUALLY RUNS IN SLOW MOTION IF YOUR FRAME RATE DROPS BELOW 30 FPS.* That's right, folks. Ignoring the absurd hard-coded 30fps limit, Frostbite 3 seems way overhyped IMHO if all it can do is run a series of poorly optimized 'next gen' games at 30fps with little to show for it and half its features missing (like FXAA) out of 'design choice' (consolization). 2.8/10 Metacritic scores (28% averaged over 200 user reviews) are low for a reason.

Nfs rivals pc 60fps patch