Forum Discussion
Merging a dual camera feed with view portals for Rift Imaging;Any suggestions on how to approach it?
I am a mech engr well through the process of building a 5 DOF motion driver simulator prototype. The goal is to knock at least 20% off the road toll, for any country that is culturally compatible with the tools anyway. The prototype is constructed from the outset to be economically delivered at population scale and highly effective at teaching / changing attitudes. The full story is at www.vrdriversim.com.
In about three months I will be trying to integrate head mounted camera feed with the VR imagery so the user sees themselves driving the car with the imagery coming via view portals that match windows and mirrors. I am just putting out feelers now for any suggestions as to the best way to approach this task? The longer version with the nuances of this q can be seen here: https://www.vrdriversim.com.au/forums/topic/green-screening/
Whilst it is still a body of work to do, I am very confident of the intended techniques to get an exact match between the VR image motion and physical motion of the simulator. What I am trying to get a fix on is the best way to look at it! I originally purchased a DK2 to check VR was at a level the whole project was likely to be viable, and then a Rift after it. Because of the front mounted camera I then added a Vive to the arsenal (still haven't unboxed the thing!). And now I see the Acer Windows Mixed Reality Dev headsets are out and wonder if that is the best platform for this? But my heart is with Oculus, as pioneers, so would rather sort something out for the Rift if it can work.
I haven't thought too far past first commercial site roll-out (15 headsets), but to do Oz the way I expect is going to be near enough to 1,000 headsets, and the US would be 10,000+ if my assumptions are correct. It will be quite a job to sort out the bits they connect to, but that is where I see this thing is going... So these foundling level decisions are going to be important over time as you can be sure we will stick with what we know, and set up the economics to suit.
Thank you in advance for anything you can suggest.
In about three months I will be trying to integrate head mounted camera feed with the VR imagery so the user sees themselves driving the car with the imagery coming via view portals that match windows and mirrors. I am just putting out feelers now for any suggestions as to the best way to approach this task? The longer version with the nuances of this q can be seen here: https://www.vrdriversim.com.au/forums/topic/green-screening/
Whilst it is still a body of work to do, I am very confident of the intended techniques to get an exact match between the VR image motion and physical motion of the simulator. What I am trying to get a fix on is the best way to look at it! I originally purchased a DK2 to check VR was at a level the whole project was likely to be viable, and then a Rift after it. Because of the front mounted camera I then added a Vive to the arsenal (still haven't unboxed the thing!). And now I see the Acer Windows Mixed Reality Dev headsets are out and wonder if that is the best platform for this? But my heart is with Oculus, as pioneers, so would rather sort something out for the Rift if it can work.
I haven't thought too far past first commercial site roll-out (15 headsets), but to do Oz the way I expect is going to be near enough to 1,000 headsets, and the US would be 10,000+ if my assumptions are correct. It will be quite a job to sort out the bits they connect to, but that is where I see this thing is going... So these foundling level decisions are going to be important over time as you can be sure we will stick with what we know, and set up the economics to suit.
Thank you in advance for anything you can suggest.
No RepliesBe the first to reply