Just unboxed my rift and I'm very excited! Naturally, the very first thing I, and probably many people who get it, want to do is see a 3D virtual world.
So I was thinking, what's the fastest, easiest way to do that? Maybe a youtube video, custom tailored to the displays of the rift (left eye on the left half, right eye on the right half, with the correct sort of skewed perspectives). So, you can plug in your rift, mirror the displays, and then go watch the video in full screen mode to get a quick taste.
Basically, I don't have access to a Windows machine just yet, so I feel like this thing is a big ol', neat looking paperweight!
It mirrors my Mac display just fine, but I don't know what to watch or do to see it in action. Any ideas?
A little known feature of Media Player Classic is that you can apply a custom post-process shader to the output, which given a SBS(Side-By-Side) input video would probably allow you to convolve the source picture as needed by the optics. Actually grabbing the rift data from the player would probably require a fair bit of work, but with some magic hardcoded numbers (maybe from a quick app that just prints them out), you could probably throw it together pretty quickly. Of course, the big problem remains that those videos won't use headtracking, so I feel like it might lose some of the magic.
Anyways, this is one of the first things I was thinking of trying out once I get my Occulus Rift Devkit...
Should a simple screen recording with FRAPS not be ok? If you play that back in fullscreen everything should be ok. YouTube should not be used for this because of its idiotic 30 fps lock.
A Simple screen recording with FRAPS is probably okay, if it effectively captures it side-by-side. Actually I feel like a bigger problem with YouTube might be the video quality, since the fps is more important with headtracking (to reduce latency) which a static video won't support anyways, so, as long as its perceived as smooth motion, i actually doubt the 30fps will cause a problem, but I don't have my devkit yet, so i could be totally wrong. It would be a problem for 3d movies though, if 30 fps per eye is insufficient, which makes me further doubt that would be the case
Man, I don't understand why everyone is going on about Youtube's 30FPS problem. I watched these with the dev kit and they are definitely watchable, not as smooth but they definitely illustrate the point well enough as per their intention. Truth is, the lower FPS I find really helps in reducing motion sickness since you can't control what your watching anyways. Without being able to control the screen with head tracking at higher frame rates can make you feel ill much faster. I verified this with cube mark at 30FPS and 60FPS. At 30 frames per second, I didn't feel as dizzy but as soon as I turned on 60 frames per second, instant motion sickness started to kick in. There is a reason for this but I will save that for another thread.