Forum Discussion
@trickeh2k wrote:
-Render.ResolutionScale 1.5
I tried this last night. It does look prettier, but it also forces the framerate up to 60fps when i had it on 2.0, tried using the other command to force it back to 30, no change, the above command line seemed to overrule it. so... it looks good, but runs terrible. back to 30fps hardcore... *sigh*
I do allways play with that command. For me it doesn't force 60 FPS, even at 2.0. My max FPS is still 30 with that.
@Chaz0r wrote:
@trickeh2k wrote:-Render.ResolutionScale 1.5I tried this last night. It does look prettier, but it also forces the framerate up to 60fps when i had it on 2.0, tried using the other command to force it back to 30, no change, the above command line seemed to overrule it. so... it looks good, but runs terrible. back to 30fps hardcore... *sigh*
I do allways play with that command. For me it doesn't force 60 FPS, even at 2.0. My max FPS is still 30 with that.
odd, i wonder why mine keeps running at 60? :L
- 12 years ago
Just played today, with the new Beta NVidia drivers, and the resolution scale set to 1.5, and it certainly seemed like the drops were less severe, but still there. Here's hoping for further improvements
- Anonymous12 years ago
Gotta love how people are discussing performance problems and FPS drops about a game that is 30 FPS locked by default from a developer in 2013 AND runs on the same engine as BF4...
Ghost Games, this is a message to you. Hire some people who know WTF they are doing. Amateurs wouldn't have made the decision to framerate lock the sim or the FPS even on the next gen consoles. It's absurd to even consider doing that these days.
Looks like this game is just going to be skipped completely just like Undercover and The Run. Both of which were woeful attempts at racing for console let alone PC.