Having no issues here, can you follow these steps to give me a trace file?
Capturing debug traces · mbucchia/Pimax-OpenXR Wiki (github.com)
Thanks.
Having no issues here, can you follow these steps to give me a trace file?
Capturing debug traces · mbucchia/Pimax-OpenXR Wiki (github.com)
Thanks.
Also, when you switch from one OpenXR runtime/headset to another, you should reset your OpenXR Toolkit settings since certain settings might not port over well. You can use the OpenXR Toolkit Safe mode for that (see our website).
Öhm, LH is the best VR Tracking System for consumers oon the market. Nearly so good as ART. Dont understand the Problem. No space to place the Stations?
Honestly, I’ve been having a bad experience too.
Before Pitool 279, I could not get the headset tracked at all.
Since Pitool 279 things are better, but there are still times I need to wave the headset around and turn in 360 degrees for the tracking to come up.
For most of my development now, I go to 9-axis to avoid this headache.
Do you only have one base?
Then try to keep at least 1.5 - 2m distance. Position about 30-45 degrees, side and top.
Ahh, LH 1.0 is better than 2.0. for single Base use.
Valve was obsessed with saving at a higher price. 2.0 is better in large rooms since 4 bases can be used. But in a 1.0 Base 2 scanners run, so better localization.
No i have 3 55 inch leds tv in front of me i would have to drill a hole in the middle .it sucks…see my dilemma.
yes i have tried it with just no lighthouse just 9 Axis but i get motion sickness without .
Even with a hole through the screens, Lighthouse wouldn’t have worked. The distance would be too short. It runs over a laser grid in space, which requires space. Here is a short video showing how it works.
In this respect, it’s not a bad design from LH , just unusable for your specific case from the outset.
That’s a good video . Yes i know my situation is not ideal for the lighthouse thing, I just hope Pimax gets the new 12 k working well then i wont have any issues.
But the oculus 2 with open XR is pretty good just the narrow FOV , but i will wait and still praying that sim update 10 will have multi monitor support .
i got the Lighthouse to work I made a Plastic Hanger for it so it sits in the upper right corner of the monitor so far so good.
Hey folks, can I ask that we stay on topic? OpenXR + Pimax. Thanks.
iRacing officially added OpenXR support today! Has anyone run it with this, yet?
I don’t have the game and I would love for someone to just try. Do you not have the game yourself?
EDIT: somebody confirmed that it works.
I have installed Pimax OpenXR to test with SU 10 (beta). I get the following error: “The initialization of VR failed.” “Please check that OpenXR is installed”.
I can’t capture a trace using the apps because “there are no trace profiles running”.
My log output:
[OXRTK] 2022-07-12 12:25:29 +0200: OpenXR Toolkit - GA-1 (v1.1.4)
[OXRTK] 2022-07-12 12:25:29 +0200: dllHome is "C:\Program Files\OpenXR-Toolkit"
[OXRTK] 2022-07-12 12:25:29 +0200: OpenXR-Toolkit layer is active
[OXRTK] 2022-07-12 12:25:29 +0200: Runtime supports extension: XR_KHR_D3D11_enable
[OXRTK] 2022-07-12 12:25:29 +0200: Runtime supports extension: XR_KHR_D3D12_enable
[OXRTK] 2022-07-12 12:25:29 +0200: Runtime supports extension: XR_KHR_vulkan_enable
[OXRTK] 2022-07-12 12:25:29 +0200: Runtime supports extension: XR_KHR_vulkan_enable2
[OXRTK] 2022-07-12 12:25:29 +0200: Runtime supports extension: XR_KHR_composition_layer_depth
[OXRTK] 2022-07-12 12:25:29 +0200: Runtime supports extension: XR_KHR_win32_convert_performance_counter_time
[OXRTK] 2022-07-12 12:25:29 +0200: XR_EXT_hand_tracking is not available from the OpenXR runtime or any upsteam API layer.
[OXRTK] 2022-07-12 12:25:29 +0200: XR_EXT_eye_gaze_interaction is not available from the OpenXR runtime or any upsteam API layer.
[OXRTK] 2022-07-12 12:25:29 +0200: Application name: 'FS2020', Engine name: 'Zouna'
[OXRTK] 2022-07-12 12:25:29 +0200: Using OpenXR runtime PimaxXR (Unofficial) 0.2.2
[OXRTK] 2022-07-12 12:25:29 +0200: --> aSeeVR_connect_server
[OXRTK] 2022-07-12 12:25:32 +0200: <-- aSeeVR_connect_server
There is a bug in flight simulator su10 that makes it you cannot not use the hidden area mesh. You will have to enable it in Pitool for now.
There are 2 ways in OpenXR to disable the hidden area mesh:
Both ways are 100% valid. PimaxXR implements 1), other runtimes implement 2).
SU9 works with 1) and 2).
SU10 does not work with 1).
PimaxXR 0.2.3 will have a workaround to that issue, which is basically to use 2) instead.
Enabled the option Hidden Area Mask, and indeed VR initializes. I feel stupid not making the connection. Thanks for pointing that out.
Lol you shouldn’t! This is a new bug in the game. Worked fine before, very weird that it broke out of nowhere.
I just purchased a PImax8kx myself and have a problem with the base stations so waiting for a new one. Could someone kindly let me know the right sequence to run it in FS2020 ?
(with sim update 9, i chose to not use beta 10 ).
I just turn on Pitools, and for now have OpenXR Toolkit disabled. (i was using that previously with my Reverb G2)
Yesterday when i tried to run VR in MFS, i got the message, ’ headset not detected’. It is detected in Pitools and SteamVR ( which i have turned on too)
thank you for any help!
OpenXR is probably still set to wmr. openXR must be activated in Steam, or better, you use this alternative instead of SteamVR: GitHub - mbucchia/Pimax-OpenXR: PimaxXR: an unofficial OpenXR runtime for Pimax headsets.
I cant get it to work either so where is this Hidden Mask area Option?
I have to use Steam to connect.