SteamVR

SteamVR

HP Reverb G2 (WMR) + SteamVR = can't play some games
Hello, world.

The problem

I can't play some VR games on Steam with my HP Reverb G2 stock controllers because buttons don't do anything.

I'm running an up-to-date Windows 10 box with Windows Mixed Reality. I have my stock HP Reverb G2 connected and WMR (not involving Steam) works just fine - can do everything in Cliff house, controllers work perfectly. With my particular headset (HP Reverb G2), I am forced to use WMR or the headset won't work (can't ditch WMR), so for SteamVR to be able to interface with the headset and controllers I have to have "Windows Mixed Reality for SteamVR" installed through Steam (per instructions from both HP and Microsoft), which I do. And everything works just fine in some Steam games, but... not in some of the other ones.

My research so far points to problem somewhere near "Windows Mixed Reality for SteamVR" plugin/ware that bridges SteamVR/OpenVR-based games with WMR. I suspect something is wrong with controller buttons on this level.

Disclaimer: I did crawl the web looking for solution, but nothing works for me. Neither erasing streamvr.vrsettings, nor reinstalling everything from scratch (including Windows), nor enrolling or opting out of betas, nor using separate bluetooth dongle for pairing controllers (as opposed to pairing them to integrated bluetooth on the headset itself), nor selecting/changing bindings in SteamVR controller bindings/settings and whatnot.

Observation #1 - OpenXR based apps NOT affected, SteamVR/OpenVR ARE affected

In particular, controller buttons do NOT work/register in games that are OpenVR/SteamVR based (let's take Google Earth VR for example; see "VR Support: SteamVR or Oculus PC"; https://store.steampowered.com/app/348250/Google_Earth_VR/), the controllers do track but pressing any button except the Windows button does nothing. It does appear that games that ARE OpenXR-based (like Ornament Express; see "VR Support: OpenXR, requires motion controllers"; https://store.steampowered.com/app/2163140/Ornament_Express/) do NOT have this problem - buttons work as expected, I can play these games just fine.

That is:
  1. WMR Cliff house (not involving Steam at all) = controllers track, all buttons work
  2. Ornament Express (OpenXR based game; WMR set as OpenXR runtime) = controllers track, all buttons work
  3. Google Earth VR (SteamVR/OpenVR based app; talks to WMR through OpenVR/"Windows Mixed Reality for SteamVR") = controllers track, but ALL button's don't work (pressing any button except Windows button does nothing)

From this I conclude that (1) works because Cliff house app is interfacing directly with WMR, (2) works because the game is interfacing with WMR through WMR-provided OpenXR interface (SteamVR shows current OpenXR runtime as Windows Mixed Reality), and (3) doesn't work because something's apparently not right with controller input passthrough at "Windows Mixed Reality for SteamVR" software level.

Observation #2 - Windows button always works and brings up WMR menu + buttons always work inside WMR menu

Once I press the Windows button in Google Earth VR to bring up WMR menu, which as it appears is handled by WMR long before SteamVR even gets an opportunity to think about it, WMR takes over the controllers and they work fine as long as I'm staying/navigating through WMR's menu. Once I close the menu by pressing Windows button again, I return to Google Earth VR and buttons don't work again. Pressing Windows button again - I get the buttons working again while I stay in WMR menu. If I exit to Cliff house from the WMR menu (i.e. exit Google Earth), the controllers will work in Cliff house just fine.

Observation #3 - SteamVR itself apparently is affected too

I mean SteamVR Home, VR Dashboard don't work either. Same problem, controllers track but ALL buttons don't work - I can not neither move, nor select anything in SteamVR Home or in VR Dashboard. Once I press Windows button, I can access WMR menu and controller buttons work in the menu just fine. Once I close WMR menu through Windows button and go back to SteamVR home - buttons are gone.

Observation #4 - Running SteamVR from WMR menu makes no difference

When I press Windows button to bring up WMR menu, on the left hand side there's Steam icon (which I believe appears once you install "Windows Mixed Reality for SteamVR" through Steam) which I can click to bring up SteamVR Dashboard/settings. Once I click it, the same thing happens - controllers track but buttons don't work. I.e. I can't select or do anything in that dashboard. If I bring up WMR menu, controllers work fine in the menu again.

Observation #5 - SteamVR's "Test Controllers" doesn't show ANY activity

Opening Settings > Controllers > Test Controllers in SteamVR shows no activity when I click any buttons on either of the controllers. Regardless of whether I'm in WMR menu or not.
The "Test Controllers" window allows me to select between "LEFT HAND" and "RIGHT HAND" controllers (i.e. which controller to test), but neither of these options produce any output on the screen after I press any of the buttons. No buttons being registered at all, trackpad doesn't register as well. When I select "LEFT HAND" controller, window title at the top says "Testing Controller MRSOURCE1", and for "RIGHT HAND" it says "Testing Controller MRSOURCE0".

Steps to reproduce

Case 1 - SteamVR Home
  1. Run Steam (through Windows start menu)
  2. Go to Library, find SteamVR, click Launch.
  3. SteamVR Home opens. You find yourself looking at "ROOMS", "RECENT APPS" and "STEAM FRIENDS". Observe controllers are tracking, you can point at things, but you can't select anything and neither of the buttons on neither of controllers does anything.
  4. Press Windows button on either of controllers, WMR menu pops up. Observe you can freely navigate through the menu with the very same buttons.
  5. In WMR menu, select "Home" icon to get to Cliff house. Cliff house loads. Observe controllers continue to fully work.

Case 2 - Ornament Express
  1. Run Steam (through Windows start menu)
  2. Go to Library, find Ornament Express, click Launch.
  3. Ornament Express game starts. Observe controllers continue to fully work.

Case 3 - Google Earth VR
  1. Run Steam (through Windows start menu)
  2. Go to Library, find Google Earth VR, click Launch.
  3. Google Earth VR starts. Observe controllers track but none of the buttons work, just like in SteamVR Home.

Environment

I should note though that on this machine I did get the controllers to work in Google Earth and other SteamVR/OpenVR games (SteamVR Home, etc) ONCE (somehow, I have no idea how), but after enjoying it for a few hours I shat the PC down for the night only to learn next morning that the controllers' buttons don't work once again. I have no idea how I got them done as I assumed I finally solved the issue, and no idea how why they stopped working. At that time I did not assume it will be such a pain to get controller buttons to work, so I didn't make any notes. Since then I have reinstalled Windows and reinstalled Steam/SteamVR multiple times, all to no avail.

SteamVR's system report

SteamVR Version 2.3.4 (1706131326) Steam: Public (beta) Tracking: holographic OS: Windows 10 (10.0.0.19045) Direct Mode Graphics: AMD (31.0.22030.2) System Admin: No Async Reprojection: Enabled Performance drops: 561/1 365/2 21/3 13/4 2427/4907 User IPD (m): 0.0679916 Displays - Direct Mode Display 0: \\.\DISPLAY1 3840x2160 @ (0, 0) AMD Radeon RX 7800 XT Primary Monitor 0: \\.\DISPLAY1\Monitor0 Generic PnP Monitor Display 1: \\.\DISPLAY11 1920x1080 @ (0, -1080) Virtual Display Adapter Monitor 0: \\.\DISPLAY11\Monitor0 Generic Non-PnP Monitor Display 2: \\.\DISPLAY12 1920x1080 @ (0, -2160) Virtual Display Adapter Monitor 0: \\.\DISPLAY12\Monitor0 Generic Non-PnP Monitor Display 3: \\.\DISPLAY13 1920x1080 @ (0, -3240) Virtual Display Adapter Monitor 0: \\.\DISPLAY13\Monitor0 Generic Non-PnP Monitor Device 1 - Headset HP Reverb Virtual Reality Headset G20 WindowsMR WindowsHolographic Camera Firmware: Version not available. VSync to Photons: 0.02 Display Frequency: 90 User IPD (m): 0.0679916 Current Universe ID: 26936415931633 Previous Universe ID: 0 Device Path: /devices/holographic/WindowsHolographic Best Alias: /user/head Device 2 - Controller WindowsMR: 0x045E/0x066A/0/2 WindowsMR: 0x045E MRSOURCE0 Supported Buttons: 0 Connected Dongle: Version: Unknown Version Device Path: /devices/holographic/MRSOURCE0 Best Alias: /user/hand/right Device 3 - Controller WindowsMR: 0x045E/0x066A/0/1 WindowsMR: 0x045E MRSOURCE1 Supported Buttons: 0 Connected Dongle: Version: Unknown Version Device Path: /devices/holographic/MRSOURCE1 Best Alias: /user/hand/left USB xHCI Compliant Host Controller Manufacturer: Generic USB xHCI Host Controller, Provider: Microsoft, 1/18/2024, 10.0.19041.3996 Root Hub [Port1]: Generic USB Hub (VID:05E3 PID:0610) [Port1] [Port2]: Generic USB Hub (VID:0BDA PID:5411) [Port1] [Port2] [Port3] [Port4]: Generic Bluetooth Radio (VID:0A12 PID:0001) [Port3] [Port4] [Port2] [Port3]: Generic SuperSpeed USB Hub (VID:05E3 PID:0620) [Port1] [Port2]: Generic SuperSpeed USB Hub (VID:0BDA PID:0411) [Port1] [Port2] [Port3] [Port4] [Port3] [Port4] [Port4] USB xHCI Compliant Host Controller Manufacturer: Generic USB xHCI Host Controller, Provider: Microsoft, 1/18/2024, 10.0.19041.3996 Root Hub [Port1]: Generic SuperSpeed USB Hub (VID:2109 PID:0822) [Port1] [Port2]: Generic SuperSpeed USB Hub (VID:04B4 PID:6504) [Port1]: USB Composite Device (VID:045E PID:0659), Microsoft, HoloLens Sensors, 78e1c46d-0767-48d7-af16-4edf509acc17 [Port2] [Port2]: Generic USB Hub (VID:2109 PID:2822) [Port1] [Port2]: Generic USB Hub (VID:04B4 PID:6506) [Port1] [Port2]: USB Composite Device (VID:0BDA PID:4C15), Generic, USB Audio [Port3]: USB Input Device (VID:03F0 PID:0580), Quanta Inc., QHMD A85V, 8CC111Z1KT [Port4] USB xHCI Compliant Host Controller Manufacturer: Generic USB xHCI Host Controller, Provider: Microsoft, 1/18/2024, 10.0.19041.3996 Root Hub [Port1] [Port2] [Port3] [Port4] [Port5] [Port6] [Port7] [Port8] [Port9] [Port10] [Port11] [Port12] [Port13] [Port14] [Port15] [Port16] [Port17] [Port18]: USB Composite Device (VID:1532 PID:007B), Razer, Razer Viper Ultimate Dongle [Port19]: USB Composite Device (VID:1532 PID:007E), RAZER, Razer Mouse Dock [Port20]: USB Input Device (VID:046D PID:C312), LITEON Technology, USB Multimedia Keyboard [Port21] [Port22] [Port23] [Port24] [Port25] [Port26] [Port27] [Port28] [Port29] [Port30] System Runtime: C:\Program Files (x86)\Steam\steamapps\common\SteamVR Log: C:\Program Files (x86)\Steam\logs Config: C:\Program Files (x86)\Steam\config Drivers: C:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver { "DesktopUI" : { "pairing" : "1531,825,800,600,0", "settings_desktop" : "1564,960,800,600,0" }, "GpuSpeed" : { "gpuSpeed0" : 1604, "gpuSpeed1" : 1614, "gpuSpeed2" : 1507, "gpuSpeed3" : 1596, "gpuSpeedCount" : 4, "gpuSpeedDriver" : "31.0.22030.2", "gpuSpeedHorsepower" : 1580, "gpuSpeedRenderTargetScale" : 1.0799999237060547, "gpuSpeedVendor" : "AMD Radeon RX 7800 XT", "gpuSpeedVersion" : 2 }, "LastKnown" : { "ActualHMDDriver" : "holographic", "HMDManufacturer" : "WindowsMR", "HMDModel" : "HP Reverb Virtual Reality Headset G20" }, "steamvr" : { "debugInputBinding" : true, "globalActionSetPriority" : true, "installID" : "6112937664076269650", "lastVersionNotice" : "2.3.4", "lastVersionNoticeDate" : "1706138891", "showAdvancedSettings" : true } }
Any help getting down the root of this would be greatly appreciated. Any logs I can provide - please let me know, I will. Have a good day everyone!
< >
Showing 1-8 of 8 comments
Bob Loblaw Jan 26, 2024 @ 12:32pm 
That's a solid bug report. Here's a couple cases of people fixing similar:
Prior causes of G2 controller not working in the forums:
1) Google Earth: if you ever had AMD AI Suite and Armoury crate, re-install windows. ( https://steamcommunity.com/app/348250/discussions/0/2997674076197110240/?ctp=3 ) ( https://www.youtube.com/watch?v=bEjH775UeNg&t=782s ) (see timestamp 13:02)
2) Pinball FX2 VR: uninstall & reinstall the game ( https://steamcommunity.com/app/547590/discussions/0/3154186375127542815/?tscn=1620402789 )
Last edited by Bob Loblaw; Jan 26, 2024 @ 12:35pm
76561199559593705 Jan 26, 2024 @ 3:27pm 
Thank you for reply. Unfortunately, this doesn't help.

RE 1 (Google Earth) - I do have AMD system, but I have installed "Driver Only" from their AMD Adrenalin software. I checked AMD install log at "C:\Program Files\AMD\CIM\Log\Install.log_2024-1-26_22_41_24.log" and that's indeed what I checked:
... 2023-11-12::12:40:26::057 CUIManager::selectedInstallType :3741 selected install type is: Driver Only 2023-11-12::12:40:26::057 InstallMan::isRSXCurrentlyInstalledOnMachine :6372 RSX package not installed 2023-11-12::12:40:29::889 InstallMan::isChipsetInstallerEligible :6659 isChipsetInstallerEligible:- =0 2023-11-12::12:40:29::893 CaptureAnalyticsData::InitializeInstallAthena :1300 Install Athena : Command line - 0 - Checkbox - 1 - Enabled - 1 2023-11-12::12:40:29::893 CaptureAnalyticsData::InitializeInstallAthena :1303 User opted in for Install Analytics 2023-11-12::12:40:29::928 InstallMan::performMyState :5018 performMyState: IM_INSTALL 2023-11-12::12:40:29::932 ProgressEvent::StartEvent::<lambda_1>::operator ():121 Starting event: PreInstall 2023-11-12::12:40:29::932 isWindowsServiceStopped :4420 Queried Windows Update Status: 4 2023-11-12::12:40:29::947 InstallMan::performPreInstall :2596 --- InstallMan -> preinstall ---- Packages to install after install type selection:------ 2023-11-12::12:40:29::947 InstallMan::performPreInstall :2636 --- performPreInstall -> [Microsoft Visual C++ 2019 Redistributable 64 bit W-00-0000-000-006-029-001-00-25] file: VC_redist.x64.exe path: C:\Users\John\AppData\Local\Temp\\AMDRSInstaller\CN\..\VC19RTx64 type: 9 2023-11-12::12:40:29::947 InstallMan::performPreInstall :2636 --- performPreInstall -> [AMD Display Driver W-06-0001-000-001-001-001-00-00] file: U0397406.INF path: C:\AMD\AMD-Software-Installer\Packages\Drivers\Display\WT6A_INF type: 2 2023-11-12::12:40:29::947 InstallMan::performPreInstall :2636 --- performPreInstall -> [AMD HDMI Audio Driver W-06-0001-000-001-039-001-00-25] file: AtihdWT6.INF path: C:\AMD\AMD-Software-Installer\Packages\Drivers\Audio\HDMI\WT64A type: 2 2023-11-12::12:40:29::947 InstallMan::performPreInstall :2636 --- performPreInstall -> [AMD Streaming Audio Filter Driver W-10-0U01-000-001-111-001-00-25] file: amdsafd.INF path: C:\AMD\AMD-Software-Installer\Packages\Drivers\Audio\SAFD\WT64A type: 2 2023-11-12::12:40:29::947 InstallMan::performPreInstall :2636 --- performPreInstall -> [AMD SoundWire Controller Driver W-10-0U01-000-001-117-001-00-25] file: amdsdwc.INF path: C:\AMD\AMD-Software-Installer\Packages\Drivers\Audio\SDWC\WT64A type: 2 2023-11-12::12:40:29::947 InstallMan::performPreInstall :2636 --- performPreInstall -> [AMD SoundWire Streaming Driver W-10-0U01-000-001-118-001-00-25] file: amdsdws.INF path: C:\AMD\AMD-Software-Installer\Packages\Drivers\Audio\SDWS\WT64A type: 2 2023-11-12::12:40:29::947 InstallMan::performPreInstall :2636 --- performPreInstall -> [USBC PD Firmware Updater W-10-0U01-000-007-014-001-00-25] file: usbcpdfw.exe path: C:\AMD\AMD-Software-Installer\Packages\Apps\USBCPDFW type: 10 2023-11-12::12:40:30::108 ProgressEvent::EndEvent::<lambda_1>::operator () :131 Finished event: PreInstall 2023-11-12::12:40:30::108 ProgressEvent::StartEvent::<lambda_1>::operator ():121 Starting event: Uninstall Previous Versions 2023-11-12::12:40:30::109 GetDeviceDescriptionMapFromINF :4981 Failed to open C:\AMD\AMD-Software-Installer\Packages\Drivers\Display\WT6A_INF\UWPPair\UWPPair.inf file. 3 The system cannot find the path specified. 2023-11-12::12:40:30::109 PackageMan::RemoveDevice_BasedOnHardwareID :1425 No devices specified to disable 2023-11-12::12:40:30::269 sendGoogleAnalytics :1425 Successfully sent HttpQueryInfo to: /r/collect?v=1&_v=j33&aip=0&a=153463489&t=event&ni=1&_s=1&dl=http%3A%2F%2Finstaller%2F&ul=en-US&de=UTF-8&dt=driver-installer&ec=application&ea=launch&el=driver-installer&tid=UA-55985825-1&cd1=http%3A%2F%2Finstaller%2F&cd3=driverinstaller&cd17=(not%20set)&cd24=adult&cd35=(not%20set)&cd37=747E-C8%7C%7C%7C%7C&cd38=1002%7C%7C%7C%7C&cd41=1DA2%7C%7C%7C%7C&cd42=AMD%20Ryzen%20Threadripper%203960X%2024-Core%20Processor&cd43=WindowsRS&cd44=64&cd45=en-US&cd46=(not%20set)&cd47=(not%20set)&cd48=en-US&cd49=(not%20set)&cm1=(not%20set)&ds=INSTALLER&cid=8be01ad0-87e6-43a6-92c8-dee882d2f164&an=INSTALLER&av=%7C23.20.23.01-231025a-397406C-AMD-Software-Adrenalin-Edition&z=3613468455 2023-11-12::12:40:35::116 ProgressEvent::EndEvent::<lambda_1>::operator () :131 Finished event: Uninstall Previous Versions 2023-11-12::12:40:35::118 PackageMan::installPackages :704 ---PackageMan -> Starting the install of AMD Display Driver...... 2023-11-12::12:40:35::119 InstallMan::performInstall::<lambda_11>::operator :2930 --- InstallMan -> Performing multi threaded install 2023-11-12::12:40:39::919 PackageMan::installPackages :704 ---PackageMan -> Starting the install of Microsoft Visual C++ 2019 Redistributable 64 bit...... 2023-11-12::12:40:51::505 PackageMan::installPackages :954 ---PackageMan -> Install of Microsoft Visual C++ 2019 Redistributable 64 bit is successful. - iResult - 0 2023-11-12::12:41:18::742 PackageMan::installPackages :954 ---PackageMan -> Install of AMD Display Driver is successful. - iResult - 0 2023-11-12::12:41:18::744 PackageMan::installPackages :704 ---PackageMan -> Starting the install of AMD HDMI Audio Driver...... 2023-11-12::12:41:20::576 PackageMan::installPackages :954 ---PackageMan -> Install of AMD HDMI Audio Driver is successful. - iResult - 0 2023-11-12::12:41:20::576 PackageMan::installPackages :704 ---PackageMan -> Starting the install of AMD Streaming Audio Filter Driver...... 2023-11-12::12:41:21::738 PackageMan::installPackages :770 AMD Streaming Audio Filter Driver Node ready for installation. 2023-11-12::12:41:36::316 PackageMan::installPackages :954 ---PackageMan -> Install of AMD Streaming Audio Filter Driver is successful. - iResult - 0 2023-11-12::12:41:36::317 PackageMan::installPackages :704 ---PackageMan -> Starting the install of AMD SoundWire Controller Driver...... 2023-11-12::12:41:36::673 PackageMan::installPackages :954 ---PackageMan -> Install of AMD SoundWire Controller Driver is successful. - iResult - 0 2023-11-12::12:41:36::673 PackageMan::installPackages :704 ---PackageMan -> Starting the install of AMD SoundWire Streaming Driver...... 2023-11-12::12:41:37::124 PackageMan::installPackages :954 ---PackageMan -> Install of AMD SoundWire Streaming Driver is successful. - iResult - 0 2023-11-12::12:41:37::124 InstallMan::performInstall :3120 feature Level: 2110 2023-11-12::12:41:37::306 InstallMan::performInstall :3120 feature Level: 2110 2023-11-12::12:41:37::367 InstallMan::performInstall :3120 feature Level: 2110 2023-11-12::12:41:37::660 InstallMan::performInstall :3120 feature Level: 2110 2023-11-12::12:41:39::634 populateInstalledPackagesRegistry :1869 ERROR Failed to get Driverstore Path for C:\AMD\AMD-Software-Installer\Packages\Drivers\Audio\SDWC\WT64A\amdsdwc.INF 2023-11-12::12:41:39::635 InstallMan::performInstall :3120 feature Level: 2110 2023-11-12::12:41:39::855 populateInstalledPackagesRegistry :1869 ERROR Failed to get Driverstore Path for C:\AMD\AMD-Software-Installer\Packages\Drivers\Audio\SDWS\WT64A\amdsdws.INF 2023-11-12::12:41:39::857 InstallMan::performInstall :3120 feature Level: 2110 2023-11-12::12:41:39::857 InstallMan::performInstall :3140 perfrom special package installation 2023-11-12::12:41:39::857 PackageMan::performSpecialPackagesInstall :243 USBCPDFW package install start - USBC PD Firmware Updater 2023-11-12::12:41:39::857 PackageMan::performEligibilityForUSBCPDFW :3000 USBCPDFW eligibiity start - USBC PD Firmware Updater 2023-11-12::12:41:39::857 PackageMan::performEligibilityForUSBCPDFW :3010 USBCPDFW exe path located in - C:\AMD\AMD-Software-Installer\Packages\Apps\USBCPDFW\usbcpdfw.exe 2023-11-12::12:41:40::039 PackageMan::performEligibilityForUSBCPDFW :3017 prformed USBCPDFW exe extraction to C:\Users\John\AppData\Local\Temp\USBCPDFW 2023-11-12::12:41:40::040 PackageMan::performEligibilityForUSBCPDFW :3098 Device Id: 747E,vendor id : 1002 , sub Device Id: D475 , sub vendor id : 1DA2, revision id: C8 , BDF :020000 2023-11-12::12:41:40::196 PackageMan::performEligibilityForUSBCPDFW :3109 firmware updation is required : false and Return code is 10: command is: C:\Users\John\AppData\Local\Temp\USBCPDFW\usbcpdfw.exe -? -b020000 -s Error Result: Failed to lauch >C:\Users\John\AppData\Local\Temp\USBCPDFW\usbcpdfw.exe -? -b020000 -s< Last error return: 0 2023-11-12::12:41:40::196 PackageMan::performEligibilityForUSBCPDFW :3122 USBCPDFW ---> Error Result: 10 ,Error Details: Failed to lauch >C:\Users\John\AppData\Local\Temp\USBCPDFW\usbcpdfw.exe -? -b020000 -s< Last error return: 0 2023-11-12::12:41:40::197 PackageMan::performEligibilityForUSBCPDFW :3127 Removing adapeter from eligibility list : DeviceID : 747E ,Return code is 10: , ErrorString USBCPDFW NO DEVICE: 2023-11-12::12:41:40::214 InstallMan::createBugReportToolShortcut :6595 BugReportTool not found in path : C:\Windows\SysWOW64\AMDBugReportTool.exe 2023-11-12::12:41:40::217 PackageMan::confirmSuccessfulDisplayDriverInstall :533 ---PackageMan -> The current active display driver is AMD Radeon RX 7800 XT by Advanced Micro Devices, Inc. version 31.0.22023.1014. 2023-11-12::12:41:40::217 PackageMan::confirmSuccessfulDisplayDriverInstall :534 ---PackageMan -> The current active display driver is AMD Radeon RX 7800 XT by Advanced Micro Devices, Inc. inf oem4.inf. 2023-11-12::12:41:40::337 CheckIfSystemDeviceIsRebootRequiredFlagSet :428 ---PackageMan -> Reboot is requested by Pci Bus 2023-11-12::12:41:40::343 InstallMan::performInstall::<lambda_17>::operator :3202 Install has completed. Reboot is required. ...

RE 2 (Reinstall Google Earth VR, Steam/SteamVR) - that doesn't help either.

What catches my attention is that SteamVR's System Report says "Supported Buttons: 0" for both of the controllers:
Device 2 - Controller WindowsMR: 0x045E/0x066A/0/2 WindowsMR: 0x045E MRSOURCE0 Supported Buttons: 0 Connected Dongle: Version: Unknown Version Device Path: /devices/holographic/MRSOURCE0 Best Alias: /user/hand/right Device 3 - Controller WindowsMR: 0x045E/0x066A/0/1 WindowsMR: 0x045E MRSOURCE1 Supported Buttons: 0 Connected Dongle: Version: Unknown Version Device Path: /devices/holographic/MRSOURCE1 Best Alias: /user/hand/left
Not sure what to make of this.

Triple-checked USB drivers in Device Manager - all devices are recognized and drivers all have been installed automatically through Windows Update.
bendotcom  [developer] Jan 26, 2024 @ 3:30pm 
Google Earth is not a good test case: It's very old, and it has not been updated, meaning it is using legacy input. It has specific cases for specific headsets (based on looking at model names) and it hasn't been updated since the G2 was released, meaning it definitely doesn't know about the G2.

That's not to say we can't try to work around a Google Earth specific issue, but that's different than a more general input problem like you are describing. If you pick a more modern app for the OpenVR testing you might learn something from those results you didn't learn from Earth.
76561199559593705 Jan 26, 2024 @ 4:09pm 
Thanks a lot for looking into this.

In terms of behaviors observed, SteamVR Home vs Google Earth VR behave exactly the same in terms of buttons not working, and SteamVR Home, I would presume, is as recent as it can get (in terms of VR compatibility) because it's apparently part of SteamVR itself.

RE trying out a more recent OpenVR/SteamVR app - I just tried out Grapple Tournament {LINK REMOVED} advertises SteamVR support) and the problem is the same - buttons don't work. I can invoke WMR menu, buttons work inside the menu, but once I exit - no button gives any effect. I do see character's hands, I can move them around, I can point, but I can't do anything else because buttons apparently don't register. I have not ran Grapple Tournament before - this is first time downloading/trying this game out.
76561199559593705 Jan 26, 2024 @ 4:57pm 
Update: I have also tired out another OpenXR game which I never downloaded before (Dark Ride Simulator; https://store.steampowered.com/app/2467510/Dark_Ride_Simulator/) and controller buttons work as expected. This seems to confirm only OpenVR/SteamVR games are affected.
76561199559593705 Feb 22, 2024 @ 7:26am 
Spent a lot of time investigating this further, coming back with a few more leads.

Observation #6 - SteamVR misreports "low battery" condition for HP Motion Controllers while playing any OpenVR game/app, but DOES NOT misreport when in WMR

When SteamVR is running, desktop (monitor) will show little SteamVR window with the green icons showing what hardware is active. In my case I see green headset plus two controllers. When I am using WMR (that is - I am in Cliff house, or I am inside SteamVR Home, VR Dashboard or any other OpenVR-based app/game and have WMR menu activated), SteamVR window shows no problems with controllers - they appear as if fully charged (there's actually no battery charge pictogram next to controllers at all, and no messages about controllers' batteries being low - i.e. shows controllers as good).

HOWEVER, when I exit WMR (by launching SteamVR from Cliff house, which lands me into VR Dashboard or SteamVR Home), then SteamVR desktop window immediately goes to show both controllers as discharged (empty red battery pictograms appear next to each controller, plus text "Low battery"). Pressing "Identify controller" next to each of the controller icons properly triggers haptics (vibration). If I press the Windows button on either of the controllers to bring up WMR menu, SteamVR window STOPS REPORTING low battery condition for both controllers - i.e. starts reporting controllers as "normal". Once I close WMR menu by pressing the Windows button again, SteamVR is back to reporting discharged state for both controllers. This correlates to the fact that when I am in WMR menu, controllers work as expected - I can point and can use buttons to navigate then WMR menu, but when I close WMR menu and apparently controllers are handed over by WMR back to OpenVR (SteamVR), SteamVR starts misreporting battery level and buttons don't work.

I am using brand new, fully-charged Lithium-Ion 1.5V AA accus for my controllers, so low voltage certainly is NOT an issue. I have checked all 4 AA accus with voltmeter - they all post 1.5 volts.

Observation #7 - SteamVR reporting controllers as discharged is directly connected to buttons not working

Sometimes (VERY rarely), predominantly after clean boot (but this is a gremlin - most of the times exactly the same steps don't reproduce), if I launch SteamVR from Desktop (shortcut), I WOULD get the controllers working in VR Dashboard / SteamVR Home (depending on whether I have SteamVR Home disabled or enabled) and subsequently ANY game that I launch from there on starts working (i.e. if buttons start working - they work everywhere). The controllers start working VERY rarely and I have not found a set of steps which would get the controllers working every time. If I close SteamVR and WMR and later relaunch them, problem comes back (so the good state in which everything works is sensitive to restarting or existing SteamVR).

HOWEVER, I did notice that when controllers do WORK, SteamVR suddenly does NOT report controllers as discharged, which makes me think this must be the key lead to solving the button issue. Perhaps there's some problem in the WMR for SteamVR layer RE battery levels, and for some reason SteamVR stops accepting button input if it "thinks" controller is discharged (wild guess).

If at any point, with the controllers miraculously working (in VR Dashboard / SteamVR home or any other OpenVR app like HLVR), I exit to WMR's Cliff house through WMR menu and then come back, the problem returns - buttons no longer work, and SteamVR starts reporting low battery condition on both controllers.
76561199559593705 Feb 22, 2024 @ 7:41am 
Oh and one more thing:

Observation #8 - VR Dashboard shows battery level "NaN%" instead of actual percentage

When I am in VR Dashboard while not having controller buttons working (but I still can point at things because tracking works) - If I point at controller battery levels inside the VR Dashboard on the bottom right corner, then battery levels for both controllers are reported as "NaN%".

Unfortunately, I have not checked how does battery reporting look like in VR Dashboard when controllers actually do work and SteamVR desktop window doesn't report them as discharged.
76561199559593705 Feb 22, 2024 @ 3:11pm 
Confirmed both VR Dashboard and SteamVR window show correct battery charge (59% and 64% respectively; see {LINK REMOVED}) when controller buttons work, and incorrectly show charge (VR Dashboard shows "NaN%" for battery percentage; see {LINK REMOVED}) for both controllers, while SteamVR window draws empty battery next to each controller and warning message "battery is low".

I seem to be able to intermittently get controllers working, but only after reboot.
< >
Showing 1-8 of 8 comments
Per page: 1530 50

Date Posted: Jan 26, 2024 @ 12:01pm
Posts: 8