![]() |
|
#6
|
|||
|
|||
|
Hi Jeff,
Thanks for getting back to me! First off, is it perhaps better if we handle this through a support ticket and then post the final results here? I have hacked together the following to get Vive specs: Code:
display_node = vizconnect.getRawDisplay('main_display').displayNode
if type(display_node.getSensor()).__name__=='SteamVRHMD':
resolution = (1080.*2,1200.)
refreshRate= 90.
# get FOVy and aspectr from the Vive's projection matrices
import vizmat
a=vizmat.Transform()
a.set(display_node.getSensor().getProjectionMatrix(viz.LEFT_EYE))
left = a.getPerspective()
a.set(display_node.getSensor().getProjectionMatrix(viz.RIGHT_EYE))
right = a.getPerspective()
FOVy = (left[0]+right[0])/2.
aspectr = (left[1]+right[1])/2.
This also leaves me with a new question. In this situation, should i open the overlay (setRenderWorldOverlay())with the resolution of the two screens combined (i.e., 2160x1200), or should i open it at a single eye size, 1080x1200? When i do the latter, things are positioned way off in the HMD, so i used the former which seems to work ok. Its however hard to know if things are positioned correctly, since we can't use a ruler to measure. Thank you and all the best, Dee |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Regarding Viconnect viewpoint | rajnishv | Precision Position Tracker (PPT) | 3 | 03-21-2017 12:03 AM |
| Regarding viewpoint with vizconfig,addFloatRangeItem&Storing viewpoint in PREFERENCES | rajnishv | Vizard | 0 | 06-27-2016 04:57 AM |
| Projection Matrix (onto oblique near plane) | andrewjworz | Vizard | 1 | 07-13-2012 10:10 AM |
| projection matrix control & child window | kwkim | Vizard | 0 | 08-31-2011 01:53 AM |