Blur Busters Forums

I read that the Oculus Rift is going to use Low Persistence to strobe the frames on and off which should work well to eliminate motion blur for the majority of games. I'm just a little concerned about how well it will work with a racing game. My understanding is that G-SYNC is better for variable frame rates (eliminate stutters/tearing, more blur) where as strobe is better for constant max frame rates (e.g. 120fps @ 120Hz, eliminates blur). I found a thread on Twitter by John Carmack from last year where he spoke for 6 hours at the nVidia G-SYNC announcement https://twitter.com/ID_AA_Carmack/statu ... 7605625856. I asked him why Oculus opted for Low Persistence instead of G-SYNC. His response:



So, I guess I won't hold out hope for a G-SYNC Rift. Will probably get on board with Commercial Version One and hope for the best with my racing games

Its a good point. What is more important? Refresh rate or image blur?

I guess both would be amazing. But I think a crisper image is really important for a screen that close to your face.

PoWn3d_0704 wrote:I guess both would be amazing. But I think a crisper image is really important for a screen that close to your face.

Especially since the FOV on that thing isn't that great. You feel like you're scuba diving. Blurriness is bound to make you sick at some point.

http://en.wikipedia.org/wiki/Vestibulo- ... lex_system

we're incredibly good at that.
with VR, basically there is persistence-related motion blur whenever one's head moves but eyes remain focused on an object. so it is crucial to keep persistence as low as possible. otherwise everything will be a blurry mess whenever you move your head.

gsync/variable refresh rate is most helpful in medium framerate situations. and I'm not sure how pleasant medium framerate would be in VR. I think for VR, I'd only use applications which can consistently keep framerate above the max refresh rate (which is where gsync is no help).

flood wrote:http://en.wikipedia.org/wiki/Vestibulo- ... lex_system

we're incredibly good at that.
with VR, basically there is persistence-related motion blur whenever one's head moves but eyes remain focused on an object. so it is crucial to keep persistence as low as possible. otherwise everything will be a blurry mess whenever you move your head.

gsync/variable refresh rate is most helpful in medium framerate situations. and I'm not sure how pleasant medium framerate would be in VR. I think for VR, I'd only use applications which can consistently keep framerate above the max refresh rate (which is where gsync is no help).

I plan on adding a second 780 Ti at some point in the near future. Probably when Project Cars hits the streets. I tried an "open box" deal on Newegg last week and it was a major fail. Will wait until the prices come down on a new one, I guess. Anyways, that should be more than enough to keep my frame rate maxed at whatever refresh rate the Rift ends up having in CV1.

Cool!

FYI, Blur Busters started originally because of a tweet reply from John Carmack:
http://www.blurbusters.com/arduino-scan ... is-viable/