HP Reverb G2 drivers fubar?

[Panzerlang]

The speakers are fubar but moving on from that...

Tried to fire up IL2, got a box at the bottom of the screen saying a special driver needs to be downloaded and installed to have SteamVR run with Mixed Reality. Unfortunately my mouse cursor doesn't appear on my monitor. I used Win + Y to switch to "desktop input", nada. Rebooted, tried everything I can think of, no joy. I can use the HP controller in the headset to point at desktop items but clicking on them gets nothing. Task Manager comes up in a weird small box but no mouse cursor anyway. Unplug the headset power, still have to reboot the PC to get back to a working desktop.

Any ideas guys?

More info...

Headset disconnected. Fired up IL2 in VR mode (to see what would happen), little window opens at the bottom of my screen to say the headset is disconnected. No mouse cursor. Hit Ctrl-Alt-Del, get the blue screen with working mouse cursor, select Task Manager, back to desktop with the weird small Task Manager panel but no mouse cursor.

WTF etc.

[dburne]

Sounds like you may want to  completely uninstall what you have - and start over from scratch.

From Steam , you will want to download and install WMR for Steam VR, and of course Steam VR.

 

 

What I do is, once I put power to the headset WMR opens. I close that.

I then launch WMR for Steam VR, and both programs open.

I then put headset on - launch IL-2 from my Desktop IL-2.exe shortcut, and lower headset to proper position.

Then I am off to the races.

[Panzerlang]

I got it working finally but it was a proper dance through the hoops.

I'm amazed how well IL2 runs, actually stutters less than with the Q2 (I say stutters, but it's so slight and 100% playable).

[Panzerlang]

I've had two blue-screen crashes, both caused by SteamVR (second one was when I ran SteamVR on its own to monkey with its settings). "WHEA-uncorrectable-error" both times.

Pretty messed up from the get-go that this bloody thing requires two APIs to run, the MRP and SteamVR.

[SCG_Fenris_Wolf]

I don't want to sound like an alarmist, but j must ring the alarm for you:

 

Whea is a critical error tied to faulty memory (edit: or faulty memory controller). It corrupts your operating system over time and anything you run on it.

 

Once you have fixed the memory, you mustmust reinstall your OS. Redownload the game and everything as well. Don't use a system that produces such issues, any of your data that you open and process may become corrupted. Separate and safe all your important data now.

 

You must run stability tests over night (like memtest86) and check your OS event log for WHEA events after each memory modification! It's important.

 

It's also important to understand you cannot "undo" the damage to OS and software now, by simply not producing WHEA events anymore. Also, be aware of people just saying "Nah, it's not that bad". That's the same guys that run summer tires in winter.

 

Sorry man. But good you took a look at what the bsod told you and posted it here, and that you found out now and not in 2 weeks or with family pictures or data from work corrupted.

Edited December 4, 2020 by SCG_Fenris_Wolf

[Panzerlang]

2 hours ago, SCG_Fenris_Wolf said:

I don't want to sound like an alarmist, but j must ring the alarm for you:

 

Whea is a critical error tied to faulty memory (edit: or faulty memory controller). It corrupts your operating system over time and anything you run on it.

 

Once you have fixed the memory, you mustmust reinstall your OS. Redownload the game and everything as well. Don't use a system that produces such issues, any of your data that you open and process may become corrupted. Separate and safe all your important data now.

 

You must run stability tests over night (like memtest86) and check your OS event log for WHEA events after each memory modification! It's important.

 

It's also important to understand you cannot "undo" the damage to OS and software now, by simply not producing WHEA events anymore. Also, be aware of people just saying "Nah, it's not that bad". That's the same guys that run summer tires in winter.

 

Sorry man. But good you took a look at what the bsod told you and posted it here, and that you found out now and not in 2 weeks or with family pictures or data from work corrupted.

I appreciate the alarm but I have to apply logic here. If the memory was faulty it would trip up on everything, not just one particular app. In particular, it would trip up when under heavy stress, like when it's being flooded by a high-end game, not by a tiny app that tickles it. And it would do so consistently.

That's my take on it.

[SCG_Fenris_Wolf]

Well it's a wrong take, as it is tied to throughput (stress, as you said yourself), but good luck, especially with Windows updates or your libraries and any dependencies affected whatsoever while gaming! 

 

..Logic.... 

Edited December 4, 2020 by SCG_Fenris_Wolf

[Guest deleted@134347]

4 hours ago, J3Hetzer said:

I appreciate the alarm but I have to apply logic here. If the memory was faulty it would trip up on everything, not just one particular app. In particular, it would trip up when under heavy stress, like when it's being flooded by a high-end game, not by a tiny app that tickles it. And it would do so consistently.

That's my take on it.

 

the issue with the faulty memory hw is that it can potentially corrupt the core files and the chipset drivers. If you're up to it you can run the Windows Debugging tool and poke in the crash dump files.  https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools, 

 

If you replaced the faulty memory and don't get any more bsod's then it'll a bit difficult to find the culprit as there are likely no more dumps, it'll be a needle in a haystack. To be on a safe side you can either a) manually reinstall all of the drivers, i.e. chipset, video, sound, network, raid controller, etc drivers  b) reinstall the semi-annual windows update (it reinstalls the core os)  c) reinstall the whole OS (just run Windows installation and select reinstall+keep files/apps).

 

Fenris is a perfectionist ?  so I get where he's coming from.  

 

Personally, I like playing with the machines that have ghosts in them, I learn about a lot of stuff that way...

 

[Panzerlang]

I'm in the "If it ain't broke leave it the ** alone" camp. It's behaved perfectly today (two runs of IL2).