#1
|
|||
|
|||
Position of Oculus DK2 sensor
System: Vizard 5, Oculus DK2, runtime 0.8
Does anyone know what the default position is for the Oculus motion tracker? I am using practically the same code as the oculusExample.py except I am loading my own scene instead of the piazza. What I can't figure out is how Vizard is deciding where to place the origin of the sensor? Can I change it? Thanks in advance for anyone who can help with this. |
#2
|
|||
|
|||
If the position is good in the piazza but not your own scene, it's likely an issue with the model. Your model may not be exported at the origin in the modeling software or the units may be different than Vizard and the scaling is off. You can look in Inspector to see if the model is offset from the origin and check the model size in meters.
|
#3
|
|||
|
|||
Thank you Jeff, I will look at the inspector to see if there is an issue with my models.
But is there a way to move the DK2 camera around within the vizard space? Is there a command analogous to: Code:
hmdSensor.setPosition(x,y,z) hmdSensor.setEuler(a,b,c) http://stackoverflow.com/questions/3...sor-in-vizard5 |
#4
|
|||
|
|||
You could get a handle to the link associated with the oculus tracker and apply an offset to that:
Code:
link = vizconnect.getTracker('dk2').getLink() # clear link offsets link.reset(viz.RESET_OPERATORS) # apply offset link.postTrans([0, 0, 4]) |
Tags |
camera, oculus, rift, sensor |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Using Oculus and Vicon for updating in pit | Qiliang He | Vizard | 1 | 09-06-2015 03:46 PM |
sensor radius bug? | lalechuza | Vizard | 7 | 08-25-2015 06:57 AM |
Oculus runtime disrupts clustering to mirror DK2 display | performlabrit | Vizard | 1 | 01-23-2015 08:00 AM |
Changing parent without changing absolute global position? | The SundanceKid | Vizard | 2 | 05-23-2014 03:43 PM |
Translate view from sensor position to lens position? | Kaminski | Vizard | 4 | 03-09-2011 11:36 AM |