Frame Rate Dropped To 30!
#1
Posted 17 December 2013 - 11:41 AM
#2
Posted 17 December 2013 - 11:46 AM
Judging from GPU temps, I think this was done purposefully to reduce GPU usage.
Edited by August55, 17 December 2013 - 11:54 AM.
#3
Posted 17 December 2013 - 12:00 PM
#4
Posted 17 December 2013 - 12:06 PM
#5
Posted 17 December 2013 - 12:43 PM
#6
Posted 17 December 2013 - 12:46 PM
Edited by DavidHurricane, 17 December 2013 - 12:47 PM.
#7
Posted 17 December 2013 - 01:05 PM
DavidHurricane, on 17 December 2013 - 12:46 PM, said:
Add a wee bit of motion blur. 30-60 frames is pretty much the normal rate that the eye can handle properly anyway. Anything higher than that is just hardware bragging rights. Also Higher rates does not equal smoother picture either. Micro stutters from the progressive frame rate are noticable by the eye. Motion blur helps this out.
just a side note too, this is why the Film industry adopted 24 fps as a standard. The only times this has been increased is recently on the Hobbit filmed at 48fps and apparently the Avatar sequels will be as well.
That is also why 120Mhz TV settings sometimes look "too real" because it is refreshing faster than the eye normally sees so it seems like real life.
#8
Posted 17 December 2013 - 01:08 PM
#9
Posted 17 December 2013 - 01:15 PM
Radeon 7870 OC, Newest Driver, before the patch everything was fine.
It occurs only in Mechlab though.
#10
Posted 17 December 2013 - 01:29 PM
Edited by CapperDeluxe, 17 December 2013 - 01:30 PM.
#11
Posted 17 December 2013 - 01:39 PM
DavidHurricane, on 17 December 2013 - 12:46 PM, said:
Yes, I don't think they did it on purpose though.
DavidHurricane, on 17 December 2013 - 01:08 PM, said:
Yes, something is not right here...
Another post mentioned flickering as well. I only noticed that before when the Mechlab/the game wasn't the active window in the OS. Once you reentered the Mechlab, the flickering of components stopped...
Edited by GoldenFleece, 17 December 2013 - 01:40 PM.
#12
Posted 17 December 2013 - 02:13 PM
#13
Posted 17 December 2013 - 02:26 PM
S.
#14
Posted 17 December 2013 - 03:03 PM
AMD 290X and 30fps in Mech lab. Running a 120Hz monitor so can see the difference.
#15
Posted 17 December 2013 - 06:58 PM
In the past, if you opened up the mech lab and went to the camo spec and rotated your mech around, there would be an incredibly ugly ghostly image caused the the motion blur that cannot be disabled in this game. If you open up the camo spec and do the same thing now, the effect is gone, even though the whole thing is choppy.
Essentially it's working to synchronize the game's framerate to what it can handle for displaying without the motion blur, it seems. Unfortunately, this means that the entire front end is now a choppy, laggy piece of junk for the sake of fixing one small bug.
Phromethius, on 17 December 2013 - 01:05 PM, said:
just a side note too, this is why the Film industry adopted 24 fps as a standard. The only times this has been increased is recently on the Hobbit filmed at 48fps and apparently the Avatar sequels will be as well.
That is also why 120Mhz TV settings sometimes look "too real" because it is refreshing faster than the eye normally sees so it seems like real life.
Human vision can definitely process scenes at over 60fps. There is a reason that 60hz CRT monitors and low-frequency ballast in fluorescent tubes causes headaches and eye strain in most people, and that is because even if you do not consciously perceive the low frame/refresh rate, your brain does. Ask any competitive FPS player, there is a HUGE difference between 30 and 60, and a big difference between 60 and 100.
Motion blur is also only useful in regards to film, and then only because we're used to it. It implies motion that would otherwise be visible. In a game rendering engine like this though, the effect is very visible and very ugly. For screenshots of what it looks like, check out this thread. The stuttering/ghosting effect you can see is the motion blur that cannot be disabled, and while it doesn't look terrible if your framerate is both high and steady, any time you drop frames you should start to notice the weird ghostly silhouette around mechs if you look carefully. Oh, and the listed solution of turning off postprocess and motion blur no longer works. It is always on now, no matter what.
Edited by aniviron, 17 December 2013 - 06:59 PM.
#16
Posted 17 December 2013 - 07:20 PM
After seeing more recent posts on this I think 30fps is just fine. I have not seen any problems at this rate I just thought there was some sort of a problem because I did not see it mentioned in the path notes.
Edited by amenophis, 25 December 2013 - 03:05 PM.
#17
Posted 17 December 2013 - 07:24 PM
Off topic: music, what?
#18
Posted 17 December 2013 - 08:17 PM
Capping the FPS in the front end will not affect the FPS in game.
#19
Posted 17 December 2013 - 09:05 PM
Brian Windover, on 17 December 2013 - 08:17 PM, said:
Capping the FPS in the front end will not affect the FPS in game.
#20
Posted 17 December 2013 - 09:24 PM
At 60 fps my GPU runs hot and i am very happy with 30 fps!
Pretty Pls
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users