Awesome was Sean able to ascertain why the Review units & your 8k unaffected?
No idea, I just informed him about that this last procedure worked (we tried a few), and sent him the log files. (We communicate through email atm) Lets see what he responds. I also informed him about this thread, and the fact that others have the same problem.
I linked your post in @Davebobman’s compilation of issues with potential solutions.
In the Banner topic it’s in tge 5k+ 8k Directory link.
Great! Lets see what Sean says
I have the same issue.
Currently waiting on a Teamviewer session, should be happening real soon.
If the Teamviewer session doesn’t happen I will try this fix.
Thanks for posting this.
Will update if/when fixed.
Happy to report that @PM_Sean has worked some wizardry on my Teamviewer
session and my headset is now tracking.
Untested on any games yet as have to do tea.
Will test a little later.
Thanks @PM_Sean you are a legend.
I’d say that’s the same as just deleting that lighthouse config file and then reboot pc. I think he did the other steps just to see if deleting that config file fixed the problem (restarting the service is the same thing as restarting the PC, at least, for the HMD).
Deleting those config files and rebooting PC did not help for some weird reason. We tried that right before trying this. Seems that restarting the services in the same session does something more…
Hmm that’s odd … The services are started when windows finishes booting, exactly like when you restart them manually. Not sure why the result would be different but I guess that in theory they could do dump config to disk when closing windows, in which case just deleting the file alone wouldn’t help. But that would be weird.
Anyway glad it works now.
Here is what works for me: When HMD loses tracking and will not be found by lighthouses, delete lighthouse directory and restart service as described above. THEN, move HMD out of view of lighthouses completely. THEN bring HMD back into view of lighthouses. Tried it several times and was able to get to work every time.
Thanks. But does it happen often? I have never seen this problem with the review units, nor the m1…
Not really. I never lose tracking once acquired. If PiServer can’t find the HMD at start-up it is usually enough to just move it out of sight of the lighthouses for 10 seconds and then back in view.
You know, this is the good thing about being backer 6XXX : fortunatly all these ‘early backer’ problems will be solved by the time (march 2019 ?) we will get our Headset
That almost sounds like M1 had better tracking signal due to thinner plastic. Not sure, but this might explain it.
I have created a batch file that will go through this process (except restarting your PC).
It is untested (I don’t have PiTool or my headset) so I would appreciate if @sjefdeklerk and/or some other code monkeys would take a look at it.
EDIT: It is extremely ugly but heavily commented. Who knew that commenting in a batch file would look that bad.
Thanks! Very confusing though in my case: moving HMD out of view and then back into view worked for me, but so far only once. Tried to repeat the action after restarting the PC (head tracking was lost again after that of course) several times and couldn’t repeat the initial outcome.
Thank you for your advices,
For two weeks I was travelling and did not have acces to my pimax.
I have purchased and installed an additional USB card (Inateck) installed PiToolSetup_220.127.116.11, but my pimax is still stuck in black (black screen, black led), I was not able to turn it back on.
I have tried to set the pimax headset in dfu mode as described by @SweViver on his 1st november video:
The led color did not change (still black) but I still tried the dos command only to get the message “0 Device(s) found. Plug your DFU Device !”
I tried connecting the pimax to a second computer but it is not detected.
I have once again measured the voltage out of the power brick. It is about 12V.
I have reached out to pimax support and will wait for their answer.