By using this site, you agree to our Privacy Policy and our Terms of Use. Close
shikamaru317 on 15 June 2023
Edit Thread
Ryuu96 said:
shikamaru317 said:

A breakdown of the analysis for those without the time to watch a 45 minute video:

  • Per object, per pixel motion blur has been added into a Bethesda game for the first time. Per object, per pixel motion blur is why the game looks quite smooth in the direct even though it is only 30 fps. idSoftware worked with Bethesda Game Studios to add their own motion blur solution from idTech into Creation Engine 2.

This should help with the gunplay right? Make it better even if 30fps?

The game will look smoother when whipping your gun around in first person to aim at people thanks to the high quality motion blur, but if you have input latency issues with 30 fps it won't help there of course. But I personally don't think input latency will be a big issue in a singleplayer shooter like this, it's not like you are more likely to lose a singleplayer fight due to a poorer input latency, like you might in a multiplayer game. 

I was quite impressed by the motion blur in the direct honestly, I thought most of the scenes in the Starfield direct were 60 fps when watching it live that day, with only a few that looked 30 fps to me, so I thought that Bethesda was going back and forth between showing off PC max settings at 60 fps and Series X at 30 fps. Now to find out it was 30 fps the entire direct has me a bit shook, because it looked 60 fps most of the time for me. I'm impressed by what Bethesda has achieved and don't think I will have any issues with the 30 fps now. Especially if you choose to play it in 3rd person, that 30 fps will be even less of an issue visually then.

Last edited by shikamaru317 - on 15 June 2023