HP G2 Loss constant of tracking
-
Flight Simmer for some time. Had most of them since the 90s. Now struggling with a HP G2 and our beloved BMS. Gutted!
Have had the G2 for a while now and it has always been problematic and I think most of the issue has been Steam VR throughout. IL2 constantly crashed and Onward has never been playable. This is very different to my experience with both Oculus CV1 and Quest 2. Bulletproof headsets to say the least! But in the search for sufficient resolution for the DCS F/A18A I went the HP Reverb G2. Had the replacement cable under warranty like many and also use a powered USB hub for it as that was a reported issue. Nothing really helped and then came OpenXR
The advent of OpenXR was a huge help and I have since flown many hours in IL2 and DCS. In IL2 I would still occasionally losing tracking with a resultant blue-screen and game crash but it was not so bad it put me off simming.
Along with millions I and my old squaddies have eagerly awaited VR for the most awesome sim ever built (BMS). A mate with Quest 2 is having a great time but unfortunately I am unable to even get past the startup screen. After about 5 seconds it just rolls over or jerks around the screen (loss of tracking). I am pretty sure it is a Steam VR issue but not 100% sure. Is anyone else having similar issues? I did buy a powered USB hub for the G2 as it was reported the MB USB wasn’t able to supply enough grunt for the HMD. Any assistance gratefully received.
System is barely 18mths old, GTX3080, bags of RAM etc.
Cheers,
Zap -
I guess for a start: Is it possible to use OpenXR at this stage?
I also have a short video of the issue but do not have privileges sufficient to post it
-
I had not heard of this until you posted.
This sounds great…!
-
@Aragorn Yes I have been using OpenXR for IL2 and DCS and it really is so much better than SteamVR.
I have now solved the issue but had a fair old fight with teh PC to get there. I have an Aorus 570 Elite Wifi and 3080 and found other had had similar trouble.
Had a devil of a time getting into BIOS from W10 and still not sure what is wrong there but a reflash with later BIOS seems to have done the trick. A mate found a post suggesting changing PCIe from Gen 4 to Gen 3 also.Sure looks good to fly the Falcon in VR!
-
@Zapper said in HP G2 Loss constant of tracking:
Flight Simmer for some time. Had most of them since the 90s. Now struggling with a HP G2 and our beloved BMS. Gutted!
Have had the G2 for a while now and it has always been problematic and I think most of the issue has been Steam VR throughout. IL2 constantly crashed and Onward has never been playable. This is very different to my experience with both Oculus CV1 and Quest 2. Bulletproof headsets to say the least! But in the search for sufficient resolution for the DCS F/A18A I went the HP Reverb G2. Had the replacement cable under warranty like many and also use a powered USB hub for it as that was a reported issue. Nothing really helped and then came OpenXR
The advent of OpenXR was a huge help and I have since flown many hours in IL2 and DCS. In IL2 I would still occasionally losing tracking with a resultant blue-screen and game crash but it was not so bad it put me off simming.
Along with millions I and my old squaddies have eagerly awaited VR for the most awesome sim ever built (BMS). A mate with Quest 2 is having a great time but unfortunately I am unable to even get past the startup screen. After about 5 seconds it just rolls over or jerks around the screen (loss of tracking). I am pretty sure it is a Steam VR issue but not 100% sure. Is anyone else having similar issues? I did buy a powered USB hub for the G2 as it was reported the MB USB wasn’t able to supply enough grunt for the HMD. Any assistance gratefully received.
System is barely 18mths old, GTX3080, bags of RAM etc.
Cheers,
ZapOk guys, OpenXR/OpenComposite does work better but that is not the issue, and who knows if/when it will come to BMS… The OP seems to be ok now (and I have NO idea why a BIOS change would do anything), but Tracking with the G2 should work flawlessly and it almost always comes down to an external lighting issue that is causing a problem. It is very similar to TrackIR in that regard, a glare from sunlight or a bright light will cause it to go nuts. For others stumbling on this post try this; with all external lighting off/shades drawn (a small overhead light above/behind should be fine), go into your “Mixed Reality Portal” Settings and select Environment, then Clear (Environment Data). Now put on the headset looking forward and follow any prompts. Now start BMS and see if tracking works. Let us know.
-
Hi Icer, thanks for your reply mate.
My current PC MB is an Aorus 570 Elite Wifi with an nVidia 3080 GPU.
As an original CV1 Rift and Q2 owner I have come close to binning the Reverb G2 several times as it has had issues with a loss of tracking in IL2 and DCS also (but not so bad) from the earliest days of owning it. My headset also had black screen issues which was diagnosed as a faulty cable as did a lot of other G2 owners and the cable was replaced under warranty by HP - at least that solved the black screen problem.
The loss of tracking and subsequent bluescreen then gamecrash issues with IL2 and DCS were not widely reported. Onward was also unusable with the same problem. On the HP forum it was suggested that perhaps the MB could not provide sufficient power through the USB C connector so I also tried a powered USB adapter/hub This changed nothing.
As a result the G2 gathered dust and I didn’t fly sims for ages on it (good old Oculus CV1 still ran like a charm!) but the problem was mostly solved when OpenXR was released. It is a project by a MS developer and a couple of others. It works a treat!
Then along came VR for BMS/F4 (which I have flown since F4 was released in '98). On installation of BMS 4.37 I was back to the loss of tracking issues and it was unusable. Coming to this forum I saw another poster was having similar issues to me and he solved it by changing PCIe from Gen 4 to Gen 3. In my attempts to do the same I had considerable difficulty in getting at the BIOS from W10 and in the end just upgraded the BIOS as mine was original from a couple of years ago.
This solved the problem completely and I am now flying BMS without that issue.
As the next step I do now seem to have an anomaly with the HUD rendering, am working on it and will report later. I will try the tips for VR users in the docs for a start.
Cheers,
Zap