What to do first when it arrives?

first open the box... :P

second will play few demos.

Third, check scale, movements, best configuration for inmersion on my proyect.

Next investigate best way or doing thinks in my proyect without break inmersión or cause nausea/annoy

I am wondering how to do many things since never try DK1

I'm sure there will be new documentation to specifically support the integration of DK2 into Unity and UE4 but for general reading I'd say the document linked to below (assuming you haven't already seen it) is a must for getting some understanding of what needs to be implemented and more importantly avoided when developing for VR

I'm sure some comments will be less valid with the inclusion of positional tracking, lower latency and the higher resolution screens but it's a good general 'do's and don'ts' of VR development.

http://static.oculusvr.com/sdk-downloads/documents/OculusBestPractices.pdf

"nomax5" wrote:
Like many I am waiting impatiently for my oculus to arrive

wow, you bought the company? :D ;)

I myself am waiting for my oculus rift to arrive, I figured just one HMD was fine... :mrgreen:

to add some relevant content: I will be trying it out firstly in UE4 on my project(s) as I'm keen to see what's working, and how, or not - asap. The ability to then build any type of environment I can think of, fast, in the VR framework is enticing, possibly more-so than trying out other's demos (at first). I guess I'll be trying out loads of ideas/prototypes with it for the first few weeks to see if any of my other ideas are feasible further down the line or if they are just pie in the sky that isn't do-able with VR yet. :mrgreen:

Definitely read the best practices and make some notes on what it says about speed (meters per second) and focus area (0.5-2.0 meters ahead for example) to reduce sickness, and make sure you are getting accurate scaling in.