So I’ve been experiencing the annoying “not tracked” issue with PiTool where everything but the headset is tracked after a reboot or change of user (my girlfriend and I use separate users to allow us to have separate Steam save games) and have found a workaround that, although really annoying, seems to work every single time I get the dreaded “not tracked” issue in PiTool where it’s only the headset that’s not tracked.
Here’s what I do:
- Delete the contents of C:\ProgramData\pimax\runtime\config\lighthouse (don’t worry - they’ll be recreated automatically when restarting the service in the next steps)
- Press Ctrl-Alt-Del and choose Task Manager
- Click on the Services tab
- Write “pi” or scroll down to find PiServiceLauncher
- Righ-click PiServiceLauncher and choose Restart
- Turn on the Vive wands and the headset will be tracked (not sure why that is though)
You can also do this in a .bat or .cmd file if You want to:
del /q /s “C:\ProgramData\pimax\runtime\config\lighthouse”
rmdir /q /s “C:\ProgramData\pimax\runtime\config\lighthouse”
sc stop PiServiceLauncher && timeout 1 && sc start PiServiceLauncher
You can run the .bat/.cmd file by right-clicking it and choosing “Run as administrator”.
Note: If You run into issues where the headset keeps being disconnected, try unplugging the power plug on the Pimax cable for a few seconds and let the headset reboot before (re)doing the steps above.
Note2: Sometimes it’s enough to just block sight between the headset and the lighthouse(s) momentarily to get tracking working.
EDIT: There’s now an option in PiTool .121 beta for restarting the PiServiceLauncher service: