Since today, after upgrade to PiTool .275, my 8K+ is not detected anymore. The led has a strange color, like it was both red and green at the same time (not flashing from one to the other). The led is red when I turn it off or if PiTool is closed. Diagnose says DP is not connected, but it is. Tried to switch between the DP of my monitor and the 8K+, but no change.
I tried to roll back to older PiTool versions, still the same. Updated the NVidia driver, no change.
Hello fabrice, same for me, I upgraded my 5k+ last night (pitool 275), he flashed my firmware, everything worked normally, and just now restarting my system, exactly the same symptom as you!!! !
I tested a lot of things, nvidia driver reinstallation, pitool in 271, firmware reflash, nothing works
I thought I had screwed my cable before reading your message.
Not working for me. Can you confirm this is the one:
Tried also another version (264) and still the same. The funny thing is that despite saying that flash is successful, DFU.EXE still says that firmware version is 273…
to work for me Fabrice,
complete uninstallation of Pitool 275 with cleaning of the windows 11 registry
Install pitool 270, update to 275 because I did not find the DFU on 270!!
Flashing the helmet in firmware 270 with method a gilles33366 (thank)
OK
then uninstall pitool 275 and switch to 270
THERE IS SURELY SIMPLE BUT IT WORKED FOR ME
attention: after flash on pitool in 275, go back to 270 immediatement
Yes this is the right one (I case of : i have the same headset than you) :
(Also plug/unplug the cable on the headset and check every cable)
So i will write again what i done :
1 ) With Pitool 275 and last firmware : Quit pitool and downgrade with DFU (with admin rights) to firmware 270. (Check if lights blink red/green while downgrading)
1.a) If possible : create rules to block updates on firewall
2 ) After that : uninstall pitool (Clean APPDATA, Program Files), reboot, and install pitool 268. PiToolSetup_1.0.1.268.exe - Google Drive
3 ) ???
4) Relaunch pitool. It works.
We really need a Drive with all firmware/pitool …
I’ve forwarded your issue to our Pitool engineer team. They will recreate the 8K+ scenario, and try to come out with a solution.
Hopefully it could be resolve in upcoming version.
You may request to provide the log file to our specialist via the ticket system, please kindly take note.
Thanks a lot PimaxQuorra.
Please note that Bramerit17 in this topic also have the issue with his 5k+. So it does not seem to be impacting the 8k+ only.
I can confirm that my 8K-X shows a different behaviour since PiTool .275 and firmware 299:
Detection of HMD takes longer: Before (PiTool .270 and firmware 295), the 8K-X was recognized almost instantly; now, it starts with error code #10600 and takes 2-3 seconds until resolved
LED color when simply “on” (HMD on, USB-PC-data only, USB-power-plug off, PiTool closed) no longer is dim red, but somewhat white - light-greenish. (Switches to bright red, when turning HMD off, as before.)
My Pimax 5k+ showed the same behaviour on saturday. I installed the new pitool version and firmware and the pimax didn’t respond at all. I tried restart computer/5k+, replug cables and reinstall pitool, nothing helped. Today I wanted to export a log for pimax support, and today the pimax headset responded again without any action from my side…
I had that snow once when I wanted to revert to an older PiTool (.270) : It seems it had gone back automatically to 90 Hz although I had left .275 with 75 Hz (and deleted all folders, of course)… So I changed the 90 Hz to 75 Hz, and it worked without snow.
Nevertheless, one day later I had even worse detection problems that with .275 (270: no detection at all any more), so I got back to .275 again. And since I always stay at 75 Hz (which my sim’s can’t even reach), at least that snow issue didn’t reappear any more.
So perhaps try it once or twice with 75 Hz - at least to locate the issue’s cause?
this is why I never rush to install (any!) updates.
My 8KX is running very, very good with *272 and (fw)299.
==> never change a running system
Hope those affected will solve the issues soon. Good luck to all
Yes, I totally agree with you.
I stayed with .270 for a long time since 90 Hz isn’t interesting for me.
But when I read about potential little performance increase with .275, I grew weak…
this is why I never rush to install (any!) updates.