i have exactly the same problem now… i think its broken…
@PimaxQuorra @PimaxUSA
1 Like
Nevermind i got my fixed again.
i have been switching no alot usb ports and suddenly it came alive…
But i dont know why it happend
1 Like
On my motherboard I have to use the USB 3.1 port, red port. The 3.0 controllers usually give me issues with Pitool detecting the headset at all. I also use a USB power injector cable (two A connectors, one for data and one for power) connected to a USB power brick. Before the power injector I had issues with the headset dropping out mid play.
2 Likes
I’ve tried using a 3.1 port, doesn’t change anything.
Still no response on my ticket, do they even look at those?
They definitely look although replies are often slow. On a bright note, I’ve had 4 separate tickets ranging from issues with Pimax.com to headset issues including one that was a mistake I made and every ticket has been resolved to my satisfaction. Just be patient, they will get back to you eventually.
How long has your ticket been open?
1 Like
15 days, made it minutes after creating this forum thread.
If you don’t mind sharing, what kind/brand/spec of PC are you running the headset with?
Assuming it’s a desktop, do you specifically know the motherboard brand/model?
On another note, did you purge the following folders/files after your uninstalls of Pitool and Steam?
Pimax:
C:\Program Files\Pimax
C:\ProgramData\pimax
C:\Users\USERNAME\AppData\Local\Pimax
C:\Users\USERNAME\AppData\Local\PiTool
C:\Users\USERNAME\AppData\Roaming\PiTool
Steam:
C:\Users\USERNAME\AppData\Local\openvr
C:\Program Files (x86)\Steam\config\ (Only Files Pertaining to VR)It’s a custom built one, so I know all the specs:
- Intel i9 9900KS
- ASUS ROG Strix Z390-I Gaming
I just went through this, uninstalled piservices, pitool and deleted all the directories you listed (expect the Steam config, nothing there looked like it was VR-related). Still no change in behavior.
Have you tried the lighthouse_watchman_update? I had your problem and fixed it with this: (case sensitive)
launch lighthouse_watchman_update.exe in the folder C:Program Files\Pimax\Runtime
command line 1：lighthouse_watchman_update.exe –bw3
Then
command line 2: lighthouse_watchman_update.exe –Bw3 0x90030006
Shutdown your computer for a few seconds and restart
That is what ultimately fixed the same issue for me. Good luck!
1 Like
Do you know if these commands are universal between the 5k and 8k(x)?
1 Like
I’m not sure. It very well could be but I’m not sure I’d risk it.
I ve had some tracking issues in the past week 8kx. It’s when I’m seated and iracing. Headset loses tracking and steam vr just shuts down when I put headset on or take off…not everytime though. Thought it was my accuforce wheel software…it’s. Not … still troubleshooting 
1 Like
What does it do exactly?
2 Likes
Hi risa
Here you go 
D:\Steam\SteamApps\common\SteamVR\tools\lighthouse\bin\win32>lighthouse_watchman_update.exe -bw3
Version: lighthouse_watchman_update.exe (buildbot_vortex-windows_steamvr_rel_win32@vortex-windows) 06101229
HID opened: VID 28de PID 2300 serial LHR-F76DE4D5 seq 1 | if 0
Sending reset into bootloader command
D:\Steam\SteamApps\common\SteamVR\tools\lighthouse\bin\win32>lighthouse_watchman_update.exe -Bw3 0x90030006
Version: lighthouse_watchman_update.exe (buildbot_vortex-windows_steamvr_rel_win32@vortex-windows) 06101229
HID opened: VID 28de PID 2301 serial LHR-F76DE4D5 seq 1 | if 0
Sent the set board revision command. Resetting…
Did not make my 8Kx tracking stable though 
3 Likes
Oh wow, these two commands and a reboot fixed it for me! Thank you so much!
btw, I finally got a response from Pimax support yesterday about a Teamviewer session during the week, just as I don’t need it any more.
In any case, this is a great catch-all thread for debugging 8KX tracking issues in the future, thanks to everyone who added suggestions!
2 Likes
I just got the same problem starting yesterday. Actually I had my headset on my desk for some time not using it so the heat theory could have some credibility. I have a ticket open and got the same list of things to try and no good. Well actually the resetting tracking using the watchman does work to appease pitools but still the base stations don’t show up in pitools or steamvr unless you pair the controllers. The system does not work properly though and steamvr has issues with the headset now saying it is not found or saying it is invalid. One other very curious thing. If I unplug my HMD and plug it in again, I have gone back to pitools complaining it can’t track it. I ran through watchman 3 times and each time the same thing happens. I tried to run some commands for the lighthouse_console with the dis and period commands per my ticket help but they didn’t show how it worked and I don’t know the proper way to type it on the command line. Hope someone knows. He did say that if the pulse_queue_overflow was not zero that would indicate a hardware problem.
I have found my headset for detection seems to be for some reason very picky about Usb port and Display port used. The other day I had to keep switching usb ports til I found the one I guess that was used before. Once I had it, tye headset detected properly. Which to me is odd behavior.
Similarly while my 8k on my 1080ti prefers top DP my 5k+ prefers a different dp to detect.
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.