Performance issue, very bad FPS and FPS drops
Hi, I have a problem with Need For Speed Rivals : I get some serious FPS drops, it is unplayable, why is it unplayable when I could play BF3 on Max settings and BF4 on Medium/High ? Also, there's no...
Forum Discussion
As In The Previous Page @chaz0r Mentioned By Using Fraps Can Get some better Fps,But What Are System Specs to Get 60Fps.
Can Someone Post The Minimum And Recommended Specs.
Thank You!
Well I had more trouble using Dxtory than FRAPS but then again Dxtory uses the Lagarith Lossless codec which makes the files much bigger so the raw data output must be significantly higher.
I tried something a bit different today to improve responsiveness in controls (PC - I use an XBOX 360 controller). I used the command line for -GameTime.MaxSimFps 45, but WITHOUT the -GameTime.ForceSimRate 45+, I used 45 just for something different, because my computer isn't high end enough to maintain 60fps, especially in the areas already mentioned where it dips to 20 and slow motion!
Once I set -GameTime.MaxSimFps 45 in the game properties, I used riva tuner in the background and limited the fps to 30 so it wouldn't go into fast motion. Usually this doesn't work, since nothing running in the background affects the game when running in X64 mode, but if you choose X86 mode, at least for me, riva tuner works, with the onscreen display, while running in the background. What this did for me is that the controls felt much more responsive and the game did not go into fast motion.
This game is still very problamatic at the docks, lagoon road and all the other places already mentioned by Chaz0r, it typically still dips to 20fps and the game goes into slow motion, so technically the patch did absolutely NOTHING to fix that issue.
Anyway, just thought I'd throw this out there
It's safe to say that we've gotten the problem narrowed down enough for developers to step in and do their work. Bottom line is that NFSR slows down to a crawl at certain spots because the hardware isn't being fully/properly utilized due to flawed coding. That's it.
