Looking at some of the vrwebhelper logs in my Steam folder it seems to be a bug in vrserver which prevents some assets from being loaded?
Fri Dec 30 2022 12:56:08.085955 - Console message (Error) from http://localhost:27062/dashboard/controllerbinding.html?desktop=true:0:
| Uncaught (in promise) AxiosError: Network Error
If I try to open that URL in the browser, I get a 401.
This is probably also why the keyboard doesn't work anymore as well
I don't know if this is at all related or not, but recently I have noticed this when trying to start my SteamVR. It seems to try to communicate with Qt, but fails and says Error 301. I know Qt is used to make GUI, and seeing as I am having a Qt SSL issue, perhaps Qt has something to do with SteamVR GUI not working properly? I am just throwing idea out cause I would like to figure out why my SteamVR GUI has been freezing up and not working properly lately.
##########
Using breakpad crash handler
Setting breakpad minidump AppID = 250820
Forcing breakpad minidump interfaces to load
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Game process updated : AppID 250820 "gamemoderun /home/user/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=250820 -- /home/user/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/user/.local/share/Steam/steamapps/common/SteamVR/bin/vrstartup.sh'", ProcID 75136, IP 0.0.0.0:0
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198137413553 [API loaded yes]
Steam_SetMinidumpSteamID: Setting Steam ID: 76561198137413553
ioctl (SFEATURE): Connection timed out
Game process updated : AppID 250820 "gamemoderun /home/user/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=250820 -- /home/user/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/user/.local/share/Steam/steamapps/common/SteamVR/bin/vrstartup.sh'", ProcID 74974, IP 0.0.0.0:0
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Steam_SetMinidumpSteamID: Caching Steam ID: 0 [API loaded yes]
Steam_SetMinidumpSteamID: Setting Steam ID: 0
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
##########
I also had this spammed constantly in my last successful launch of SteamVR:
ioctl (SFEATURE): Connection timed out.
EDIT:
I copied my updated version of the Qt files from my /lib folder into the steamvr qt folder at SteamVR/bin/linux64/qt/lib/ and that seems to have fixed the issue with qt.network.ssl. Still gettint 301 error with the ioctl timeout issue though.
Just a heads up for people trying to work around this right now: SteamVR seems to have changed where it stores what tracker does what. You now need something like this in steamvr.vrsettings:
"trackers" : {
"/devices/lighthouse/LHR-XXXXXXXX" : "TrackerRole_LeftFoot",
"/devices/lighthouse/LHR-XXXXXXXX" : "TrackerRole_Waist",
"/devices/lighthouse/LHR-XXXXXXXX" : "TrackerRole_RightFoot"
}
Nothing extracted yet.
Describe the bug
The menu to configure trackers such as Vive Trackers or Tundra Trackers doesn't accept any changes I make.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should change the role of the trackers
System Information (please complete the following information):
Screenshots
Additional context
I am using Tundra Trackers, but I assume this is a general bug.
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.
Workaround
You can configure this manually by editing the config.json of the device at
.steam/steam/config/lighthouse/lhr-<serial>/config.jsonIn my case I set
"tracked_controller_role" : "left_foot", ...right_footand ...waistrespectively.If that property does not exist (didn't for me), just add it to the end of the file. Make sure to add commas where necessary.