Closed rtlnut closed 1 month ago
The-personified-devil
commented
3 months ago In v20.9.1 your controllers should only be simple stars made out of wires. But not being able to open system view really sounds like a quest issue, since alvr doesn't really have the ability to influence that
rtlnut
commented
3 months ago In v20.9.1 your controllers should only be simple stars made out of wires. But not being able to open system view really sounds like a quest issue, since alvr doesn't really have the ability to influence that
The report screen can be opened by clicking the menu button five times, which is the only way to open the menu after a bug has appeared, after which the controller can return to normal. But I couldn't shut down the device properly, because the controller was still disabled on the screen where I chose to shut down or restart the device.
zmerp
commented
3 months ago This is very odd, it wasn't uncommon to have ALVR lock up the whole OS, but this was years ago on the Quest 1.
github-actions[bot]
commented
1 month ago This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Description
When I open the alvr client on Quest2, it doesn't recognize my controller, and it seems that all the controller buttons are disabled. I can't open the system menu, and I can only reset the view by long pressing the Menu button. This bug does not affect me connecting to the computer and entering Steam Home, but my controller is still not recognized after entering. I don't have a specific way to reproduce this bug. It seems to disappear after a few retries, but it will also appear again.
General Troubleshooting
Environment
idk
Hardware
CPU: i5 7300HQ
GPU: GTX 1060
GPU Driver Version: 32.0.15.5612
Audio:
Installation
ALVR Version: 20.9.1
ALVR Settings File: session.json
SteamVR Version: 2.7.4
Install Type:
exe,deb,rpm, etc)zip)OS Name and Version : Windows 10 64-bit (10.0, Build 19045)