Issues with new PiTool and Firmware

Chumet · September 25, 2021, 6:13pm

After updating to Pitool 272 and manually reflashing the latest firmware “P2_RELEASE_8KX_M299_t20210922093742_r6066b70.dfu”, I had no screen flickers already known to all. I thought that the advice to reflash the firmware had really solved it. But the next day when I turned on the PC, which does not supply power through the USB when it is off and the PIMAX 8KX is completely off, it started with a “white” led and stayed there until I started Pitool and it started working normally, but to my surprise the blinks had returned and were unbearable, very constant. I flashed the firmware again but the situation is the same. I can only get to have the 90Hz mode active with sporadic flickers every 5 or 10 seconds as @ Rygar1976 explains very well, when I restart the Pitool services and there are times that it is corrected and other times it is not. I think the problem is directly related to the Pitool services, it is the only variable that makes this screen flickering fault better or worse.
On the other hand I have tried all the USB ports of the PC and the DP of the graph and there are no improvements. I have also “literally” analyzed the proprietary connector of the Pimax and the cable with a magnifying glass, to rule out bad contacts that are on the verge of failure when the maximum stability of signal transmission is being requested. But the impression is that they are impeccable. I can only think that my original “copper” cable is degrading in some section, since lately I play a lot of shoters like ContractorsVR and there is much more movement, tension and turns on itself during the games. Before, I was a nearly 100% Simracing player.

For all this I ask you two questions:

Are there really many people here who do not have or have had screen flickering with arfitacts in 90hz mode?
Do you think that these sporadic flashes of greater or lesser frequency may be due to the degradation of the Pimax cable?
When the Pimax is completely disconnected and you connect them to the USB and DP, when it starts it shows the LED in “white” color and does not change its color until Pitool is started?

Rygar1976 · September 25, 2021, 7:17pm

Thank you. Yes I loaded the new PiTool and it auto updated the firmware. I did not notice a link for Firmware.

I appreciate the heads up!!!

neal_white_iii · September 25, 2021, 7:36pm

I have had zero problems with 90Hz on my 8KX (with firmware v2.2.255.298), although I did have trouble with the last PiTool not detecting my headset reliably, so I’ve been using PiTool v 270. Notably, I’m using an MSI RTX 2080.
I do think it could be a cable issue, but it might also be a problem with the DisplayPort.
I’ve never seen that.

Chumet · September 25, 2021, 11:30pm

I leave you 2 videos where the behavior of the white led when plugging in the Pimax 8KX is shown on the one hand and that Pitool gives an error but it ends up starting the HMD, I have tested it in all 60/75 / 90hz modes. If this is not what is established in this new firmware, maybe the firmware is not flashing correctly, but I have tried it several times and it always does the same. Also from CMD with the traditional method of manually setting the DFU mode by pressing the 3 buttons etc … So I was wondering if it is something normal in this new 299 firmware or is it my Pimax that is not working correctly now.
On the other hand, I leave you another video where the screen blackouts are shown with an interval of about 30 seconds, but it becomes more noticeable when they have been on for a while.
I have also seen fog in one of my HMD reboots, if you put a black background and I was already wondering if the cable was really damaged, but now when turning it off and leaving it quiet for a few hours, there is no fog. Something is wrong here and it does not support this 90hz frequency correctly. I regret the firmware of March 298 (P2_RELEASE_8KX_90HZ_Beta.dfu) and Pitool 270 where I have no problems with white LEDs, blackouts, fog and also turns off my controllers when turning off pitools.
They are solving the compatibility with the new Nvidia drivers and they are breaking what initially worked very well and that was a beta version to show that it was possible to reach 90hz.

Chumet · September 26, 2021, 12:04am

Now if I have been surprised, keeping the firmware 299 I have downgraded to version 270 of Pitool that had had such good results, I hoped that the HMD would not work well with this crazy combination. But surprisingly it has worked “half” I say it because the HMD was already started it has been working until I restarted it, which it has not done, it stays with the “white” led even if you have Pitool 270 active, not even restarting the services of the Pitool. I see that this latest version of Pitool 272 is part of the Pimax boot now and makes it incompatible with previous versions.
It’s a shame because for a few moments I have had what we are looking for:

There are no blackouts in 90hz
Works fine with the latest Nvidia 472.12 drives

The problem is clearly in the Pitools, they have to find what worked well in the 270 and keep it in the 272.

How crazy all this …

Chumet · September 26, 2021, 12:37am

As I had stayed with Pitool 270 I went down to the initial firmware of March 298 “P2_RELEASE_8KX_90HZ_Beta.dfu” to see that the Pimax starts as before without “white” LEDs or blackouts or anything, but of course having the Nvidia 472.12 drives installed. 90hz mode did not work. So I have put the following firmware 298 published in July “P2_8KX_M298_EngineerTest.dfu” and keeping Pitool 270 as you have it. And perfect, I have 90hz without blackouts or white LEDs, nor the need for Pitools to be on so that the HMD starts up and stays in standby mode. And my Index controllers also turn off when I pay for Pitool, which was something I really liked and was lost in version 271.

Pimax: We are not going well this way, you spoil things that we had good and stable to implement others that do not work well, (Compulsory smooth option). I tried the 1/2 mode and it was set to 45fps but the performance did not increase, that is, if I had 8.8 ms (90hz) = 90FPS without smooth option, I still had 8.8ms (90hz) = 45fps with smooth option at 1/2. The GPU load should drop to 8ms or less and I am not saying half, but see a noticeable improvement.

The winning combination for me, stable without blackouts and with the latest Nvidia drivers:

neal_white_iii · September 26, 2021, 2:13am

I’m glad it’s working for you. I think I will not upgrade to the newest PiTool, since my 8KX is working fine. I like the idea of the new 1/2 framerate option, but it’s not worth the hassle to update (at least until PiTool is more stable).

TonytotheB · September 26, 2021, 2:48am

Agreed Neal. I was contemplating the update but mine is fine. I also just extended with the Lindy and it’s perfect for me. Few hours of No Man’s Sky this morning

Kimchi_guy · September 26, 2021, 7:20am

Sigh… you’re right. Even after various combination of old 90Hz firmware and different pitools over the weekend, I realized pitool v270 and P2_8KX_M298_EngineerTest firmware were only way to run Steam VR home in stable visual. The latest firmware and pitool, I got screen blink. USB disconnection every 5 seconds… Other older firmware also had various issues like add-on crash by Steam VR.

With v270 and M298 firmware which is best for me at this point also have screen ghosting problem in many games such as Project car series, Myst VR etc while PE home and SteamVR home screen have absolutely no issue at all.

But I used to resolve this ghosting issue by re-installing Windows 10, so I guess it’s not directly related to Pimax hardware nor firmware/pitools.

Sidekick1 · September 27, 2021, 1:45pm

I just wish that during the process that Pitool would ask for permission to update the Firmware. I had downloaded both files (Pitool 272 & P2…8KXM299…). After the new PiTool forced the firmware update blinking on and off as well has huge artifacts. After installing the M299.DFU 8KX firmware and a reboot, everything works nicely. I do like the 1/2 option for DCS as it is smoother with less ghosting. It is still running fine but I only use it with my Simpit for DCS and IL2.

Genesis · September 27, 2021, 7:38pm

I haven’t tried the new smoothing option.

I did have another long VR play session on Sunday in VRChat and experienced regular screen flickering and blackouts on 90Hz which was distracting enough to need to switch back to 75Hz for the rest of the session, so seems like 90Hz is still an inconsistent experience between play sessions.

Sidekick1 · September 27, 2021, 9:21pm

Yes I did, I have a pretty optimized system running DCS and I have done many framerate tests with difference settings and overclocking settings for my GPU and my RTX3090 card. I am running i9900KS at 5.3 and my OC3090 with SteamVR running at 2900x2768. Using 8KX with two LH v1.

I use a dogfight with an AI as the test area as it is always the same. This is what I see ;

Without any Compulsory or Smart Smoothing I am getting a raw 80-90 FPS. At the merge the AI enemy has a little stutter as it passes the center FOV at high speed.

With Compulsory on at 1/2 this seems smoother but there is a small but short ghosting right at the merge pass through the center of the FOV.

With Compulsory on at 1/2 and Smart smoothing turned on, it feels just a tiny bit smoother but the ghosting is a bit more pronounced (larger).

I can handle the little bit of ghosting as it is so much smoother than native to me and I would rather have the smoothness with no micro stuttering.
Hope that helps…

BoxingPanda · September 27, 2021, 9:27pm

For me, this new pitool update and the optional firmware in the original post is the ONLY firmware to have BOTH 90hz and 110hz working PERFECTLY. Before I could get 90hz native working perfectly, but the 110hz upscaled would black out in one eye after a few minutes. Played for hours yesterday at 110hz with no issues. Love it!

Maremba · September 28, 2021, 1:16pm

I usually don’t post anything but the new behavior of this new functionality set in “1/2” is what allowed me finally to experience completely smooth flying sessions that I never ever had before, all the stutters were entirely GONE. Last night I went to fly again and the stutters were back, when checked the 1/2 value in Pitool had indeed not been saved, when selected that immediately I had that perfect experience again, it’s so good that it feels like something considerable is changed for good. Thank you pimax, now everything looks and feels amazing at 90hz!

neal_white_iii · October 2, 2021, 5:57am

@PimaxQuorra and @hammerhead_gal , I decided to update to the latest PiTool. BIG mistake. I was running PiTool 270 and all was good.

When I upgraded PiTool, it automatically flashed the headset too. Everything looked fine at first, but when I actually tried to use the headset, the screens were flashing black and multicolored static junk. Sometimes I could see some of the correct image flash by.

I tried to flash using the new 8KX firmware mentioned in the PiTool post. I’ve flashed the headset before, but the headset would not stay in program mode (red-green-blue flashing LED). It would enter that mode, but in a few seconds it would go back to standard mode, so I couldn’t flash it. After many, many attempts, I got it in program mode and flashed it, but now PiTool says the headset is disconnected.

I’ve rechecked the cable several times, but the headset is not detected. I then tried to reflash to a previous (known working) firmware, but now DfuSeCommand.exe now cannot find the headset. (It tells me to plug it in!)

The headset is plugged in and none of my hardware has changed. I’ve tried swapping the ports around and I’ve also swapped from my original cable to my Pimax optical cable. It still says the headset is disconnected. This must be a Pimax software/firmware issue.

I have wasted well over 2 hours now. I am quite unhappy.

Here’s some info that might help your team to diagnose the issue…

I’ve seen this notification a few times now (and I’ve never seen it before I tried to update PiTool)…

And here’s a warning in Device Manager…

Here’s my pitool.log, in case that helps…

Log

10/02-00:58:34 Critical: PiTool start
10/02-00:58:34 Critical: start load translate
10/02-00:58:34 Critical: load json cuccess: “C:/Users/Neal/AppData/Local/Pimax\PiTool\config.json”
10/02-00:58:34 Critical: load translator file name >>>>>>>>>>>>>> “pitool_cn”
10/02-00:58:34 Critical: load translator file name >>>>>>>>>>>>>> “pitool_en”
10/02-00:58:34 Critical: load translator file name >>>>>>>>>>>>>> “???”
10/02-00:58:34 Critical: load translator file name >>>>>>>>>>>>>> “???”
10/02-00:58:34 Critical: load translator file name >>>>>>>>>>>>>> “???”
10/02-00:58:34 Critical: load translator file name >>>>>>>>>>>>>> “???”
10/02-00:58:34 Debug: config_object size: 8
10/02-00:58:34 Debug: language_str: “pitool_en”
10/02-00:58:34 Debug: load translator success “C:\Program Files\Pimax\Runtime\language\pitool_en.qm”
10/02-00:58:34 Critical: start load qml
10/02-00:58:35 Critical: Setting init
10/02-00:58:36 Critical: setAutoRun: false false
10/02-00:58:36 Critical: config.json is contains noviceguide
10/02-00:58:36 Critical: set mNoviceGuide : false
10/02-00:58:36 Critical: PiService
10/02-00:58:36 Critical: setHmdCap 0
10/02-00:58:36 Info: PiService::start,success
10/02-00:58:36 Critical: EnumDisplaySettings success 3840 2160
10/02-00:58:36 Info: all exist
10/02-00:58:36 Critical: enable false
10/02-00:58:36 Critical: svc_setIntConfig abg_as_enable failed false
10/02-00:58:36 Info: setForceFramerateDivider divider: 2
10/02-00:58:36 Critical: svc_setIntConfig dbg_force_framerate_divide_by failed 2
10/02-00:58:36 Critical: svc_setIntConfig enable_foveated_rendering failed
10/02-00:58:36 Critical: svc_setIntConfig foveated_rendering_level failed
10/02-00:58:36 Critical: set support_vive_only_games failed false
10/02-00:58:36 Critical: set over_drive_levels failed 1
10/02-00:58:36 Critical: set color_contrast left error
10/02-00:58:36 Critical: set color_contrast right error
10/02-00:58:36 Critical: set color_birghtness left error
10/02-00:58:36 Critical: set color_brightness right error
10/02-00:58:36 Debug: gameSetting sucessful
10/02-00:58:36 Critical: path: “C:\Program Files\Pimax\Runtime”
10/02-00:58:36 Critical: result: 3
10/02-00:58:36 Critical: result: “”
10/02-00:58:36 Critical: result: “No connected lighthouse device found.”
10/02-00:58:36 Critical: result: “”
10/02-00:58:36 Info: SteamModel
10/02-00:58:36 Info: getInstallFolder, (“C:\Steam”)
10/02-00:58:36 Info: ResourceModel
10/02-00:58:36 Info: initResource tool size 0
10/02-00:58:36 Info: initResource piplay size: 0
10/02-00:58:36 Info: steamvr app: “C:\Steam\config\steamapps.vrmanifest” size: 10
10/02-00:58:37 Debug: initResource game: 10
10/02-00:58:37 Critical: Unable to open Libraries key.
10/02-00:58:37 Debug: initResource game: 10
10/02-00:58:37 Info: loadPiplay1Data “C:/ProgramData/” “C:\ProgramData\pimax\pidb”
10/02-00:58:37 Info: “C:\ProgramData\pimax\pidb” is not exist
10/02-00:58:37 Debug: RpcServer listen at port 17926
10/02-00:58:37 Critical: OnlineModel init
10/02-00:58:37 Debug: config : “C:/Users/Neal/AppData/Local/Pimax”
10/02-00:58:37 Critical: pimaxLogDir : “C:/Users/Neal/AppData/Local/PiTool/PiToolLog.zip”
10/02-00:58:38 Debug: tool,Component.onCompleted
10/02-00:58:38 Info: “:/performance_en.txt”
10/02-00:58:38 Info: “GTX1050/AMD R9 280 or above is recommended for the best experience” 103 79
10/02-00:58:38 Info: “GTX1050/AMD R9 280 or above is recommended for the best experience” 79 46
10/02-00:58:38 Info: “Good enough” 46 23
10/02-00:58:38 Info: “Good enough” 23 0
10/02-00:58:38 Info: “Intel I5 or above is recommended for the best experience” 10 6
10/02-00:58:38 Info: “Intel I5 or above is recommended for the best experience” 6 3
10/02-00:58:38 Info: “Good enough” 3 2
10/02-00:58:38 Info: “Good enough” 2 0
10/02-00:58:38 Info: setOs “Windows 10 Home(10.0.19043)”
10/02-00:58:38 Info: checkCpuLevel,index= 2 “Intel(R) Core™ i7-8700K CPU @ 3.70GHz”
10/02-00:58:38 Info: ("{0A48E248-0A0E-11EC-A2D4-40B076475045}", “{29875EE7-B1F2-11EA-A257-40B076475045}”, “{2A752D1E-CEB8-11EA-A261-40B076475045}”, “{3E039C7D-C949-11EB-A2B7-40B076475045}”, “{AF481410-FA4B-11EB-A2D2-40B076475045}”, “{B1A26421-90B8-11EB-A298-40B076475045}”, “{B2C11C2B-C3BC-11EB-A2B1-40B076475045}”, “{B4FEBED0-C40D-11EB-A2B2-40B076475045}”, “{C0C2889B-EBBE-11EB-A2C9-40B076475045}”, “{C443DB22-F4CE-11EB-A2CE-40B076475045}”, “{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}”, “{E39D0F36-9FE0-11EB-A2A4-40B076475045}”, “{E4CDCF5A-888E-11EB-A295-40B076475045}”)
10/02-00:58:38 Info: getgpu tmp 472
10/02-00:58:38 Info: getgpu 1 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: getgpu 2 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: gpu driver “NVIDIA GeForce RTX 2080” “30.0.14.7212”
10/02-00:58:38 Critical: versionCheck: “1.0.1.272”
10/02-00:58:38 Critical: mBuildVersion: 272
10/02-00:58:38 Info: VersionItem::load>>>>>>>>>>>>>>>>>>>>>>> 272
10/02-00:58:38 Info: getHttpRequest url:
10/02-00:58:38 Info: vsesion get
10/02-00:58:38 Info: ("{0A48E248-0A0E-11EC-A2D4-40B076475045}", “{29875EE7-B1F2-11EA-A257-40B076475045}”, “{2A752D1E-CEB8-11EA-A261-40B076475045}”, “{3E039C7D-C949-11EB-A2B7-40B076475045}”, “{AF481410-FA4B-11EB-A2D2-40B076475045}”, “{B1A26421-90B8-11EB-A298-40B076475045}”, “{B2C11C2B-C3BC-11EB-A2B1-40B076475045}”, “{B4FEBED0-C40D-11EB-A2B2-40B076475045}”, “{C0C2889B-EBBE-11EB-A2C9-40B076475045}”, “{C443DB22-F4CE-11EB-A2CE-40B076475045}”, “{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}”, “{E39D0F36-9FE0-11EB-A2A4-40B076475045}”, “{E4CDCF5A-888E-11EB-A295-40B076475045}”)
10/02-00:58:38 Info: getgpu 1 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: getgpu 2 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: ("{0A48E248-0A0E-11EC-A2D4-40B076475045}", “{29875EE7-B1F2-11EA-A257-40B076475045}”, “{2A752D1E-CEB8-11EA-A261-40B076475045}”, “{3E039C7D-C949-11EB-A2B7-40B076475045}”, “{AF481410-FA4B-11EB-A2D2-40B076475045}”, “{B1A26421-90B8-11EB-A298-40B076475045}”, “{B2C11C2B-C3BC-11EB-A2B1-40B076475045}”, “{B4FEBED0-C40D-11EB-A2B2-40B076475045}”, “{C0C2889B-EBBE-11EB-A2C9-40B076475045}”, “{C443DB22-F4CE-11EB-A2CE-40B076475045}”, “{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}”, “{E39D0F36-9FE0-11EB-A2A4-40B076475045}”, “{E4CDCF5A-888E-11EB-A295-40B076475045}”)
10/02-00:58:38 Info: getgpu 1 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: getgpu 2 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: isNotebook battery 255
10/02-00:58:38 Info: isNotebook battery 255
10/02-00:58:38 Info: ("{0A48E248-0A0E-11EC-A2D4-40B076475045}", “{29875EE7-B1F2-11EA-A257-40B076475045}”, “{2A752D1E-CEB8-11EA-A261-40B076475045}”, “{3E039C7D-C949-11EB-A2B7-40B076475045}”, “{AF481410-FA4B-11EB-A2D2-40B076475045}”, “{B1A26421-90B8-11EB-A298-40B076475045}”, “{B2C11C2B-C3BC-11EB-A2B1-40B076475045}”, “{B4FEBED0-C40D-11EB-A2B2-40B076475045}”, “{C0C2889B-EBBE-11EB-A2C9-40B076475045}”, “{C443DB22-F4CE-11EB-A2CE-40B076475045}”, “{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}”, “{E39D0F36-9FE0-11EB-A2A4-40B076475045}”, “{E4CDCF5A-888E-11EB-A295-40B076475045}”)
10/02-00:58:38 Info: getgpu 1 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: getgpu 2 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: ("{0A48E248-0A0E-11EC-A2D4-40B076475045}", “{29875EE7-B1F2-11EA-A257-40B076475045}”, “{2A752D1E-CEB8-11EA-A261-40B076475045}”, “{3E039C7D-C949-11EB-A2B7-40B076475045}”, “{AF481410-FA4B-11EB-A2D2-40B076475045}”, “{B1A26421-90B8-11EB-A298-40B076475045}”, “{B2C11C2B-C3BC-11EB-A2B1-40B076475045}”, “{B4FEBED0-C40D-11EB-A2B2-40B076475045}”, “{C0C2889B-EBBE-11EB-A2C9-40B076475045}”, “{C443DB22-F4CE-11EB-A2CE-40B076475045}”, “{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}”, “{E39D0F36-9FE0-11EB-A2A4-40B076475045}”, “{E4CDCF5A-888E-11EB-A295-40B076475045}”)
10/02-00:58:38 Info: getgpu 1 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Info: getgpu 2 “NVIDIA GeForce RTX 2080”
10/02-00:58:38 Critical: PiService::getRefreshCounts get refreshCounts failed: 0
10/02-00:58:38 Critical: file exists “C:\Users\Neal\AppData\Roaming\PiTool\manifest\PiTool\” “”
10/02-00:58:38 Info: exist “C:\Users\Neal\AppData\Roaming\PiTool\manifest\PiTool\.json”
10/02-00:58:38 Debug: get m_contrastLeft_B: 0 PiService::loadFromFileByTitle
10/02-00:58:38 Info: setForceFramerateDivider divider: 2
10/02-00:58:38 Critical: svc_setIntConfig dbg_force_framerate_divide_by failed 2
10/02-00:58:38 Critical: setTempFoveatedEnable : false enable : false
10/02-00:58:38 Critical: setTempFoveatedLevel : -1 level : -1
10/02-00:58:38 Critical: file exists “C:\Users\Neal\AppData\Roaming\PiTool\manifest\PiTool\” “Common Setting”
10/02-00:58:38 Info: exist “C:\Users\Neal\AppData\Roaming\PiTool\manifest\PiTool\Common Setting.json”
10/02-00:58:38 Debug: get m_contrastLeft_B: 0.1 PiService::loadFromFileByTitle
10/02-00:58:38 Debug: TempBrightnessLeft “is -0.02”
10/02-00:58:38 Critical: PiService::getRefreshCounts get refreshCounts failed: 0
10/02-00:58:38 Critical: PiService::getRefreshCounts get refreshCounts failed: 0
10/02-00:58:38 Critical: PiService::getRefreshCounts get refreshCounts failed: 0
10/02-00:58:38 Critical: PiService::getRefreshCounts get refreshCounts failed: 0
10/02-00:58:38 Critical: PiService::getRefreshCounts get refreshCounts failed: 0
10/02-00:58:38 Critical: PiService::getRefreshCounts get refreshCounts failed: 0
10/02-00:58:38 Critical: PiService::getRefreshCounts get refreshCounts failed: 0
10/02-00:58:38 Critical: svc_getPanelMode failed: -1
10/02-00:58:38 Critical: getPanelModeIndex failed: 0
10/02-00:58:38 Critical: svc_getPanelMode failed: -1
10/02-00:58:38 Critical: getPanelModeIndex failed: 0
10/02-00:58:38 Critical: getScreenSave failed false
10/02-00:58:38 Critical: getLanguageList 6
10/02-00:58:38 Debug: onResCountChanged,count=10
10/02-00:58:38 Info: searchResource sortType02: 0
10/02-00:58:38 Info: searchResource sortType02: 0
10/02-00:58:38 Debug: privacy_path : “C:\Program Files\Pimax\Runtime\language\privacy\pitool_en_privacy.txt”
10/02-00:58:38 Info: “:/privacy_en.txt”
10/02-00:58:38 Debug: ConnectUI,Component.onCompleted
10/02-00:58:38 Critical: load qml end
10/02-00:58:38 Critical: init end
10/02-00:58:38 Info: post event data
10/02-00:58:38 Info: postEventData command= “/piplay_v3/stat/event?device_id=47b07640-4550-b040-47b0-76404550b040&time=1633150718”
10/02-00:58:38 Info: httpReadyRead : 182
10/02-00:58:38 Critical: httpError : QNetworkReply::NetworkError(UnknownServerError)
10/02-00:58:38 Info: parsePiPlayData -1 “” “get data error”
10/02-00:58:38 Debug: parseUpgradeData code!=8888 “get data error-1”
10/02-00:58:39 Info: httpReadyRead : 182
10/02-00:58:39 Critical: httpError : QNetworkReply::NetworkError(UnknownServerError)
10/02-00:58:39 Info: parseResponseData “\r\n502 Bad Gateway\r\n<body bgcolor=“white”>\r\n

502 Bad Gateway

\r\n

nginx/1.14.0 (Ubuntu)\r\n\r\n\r\n”
10/02-00:58:53 Debug: config : “C:/Users/Neal/AppData/Local/Pimax”
10/02-00:58:53 Critical: DiagnoseHandler::softwareDiagnose
10/02-00:58:57 Debug: doing resource

10/02-00:59:03 Debug: doing resource

10/02-01:03:48 Debug: showWindow
10/02-01:03:51 Debug: config : “C:/Users/Neal/AppData/Local/Pimax”
10/02-01:03:51 Critical: DiagnoseHandler::softwareDiagnose
10/02-01:04:13 Critical: ~PiService
10/02-01:04:13 Info: ~ResourceModel

Lebois · October 2, 2021, 10:01am

I tested the automatic firmware with pitool 272 : 90hz didn’t work (I don’t exactly remember what was wrong). I tested the manual firmware “P2_RELEASE_8KX_M299_t20210922093742_r6066b70” : I was having black screens everything 2 or 5 seconds.
Today, I reflashed the firmware, I restarted the headset (using the pitool button), I restarted the service using pitool’s button. And now it seems stable…

grzvs · October 2, 2021, 2:38pm

Hi, it happened exactly the same to me, what I did:

Install latest Nvidia drivers.

Uninstall latest Pitool and install previous version.

Stop Pitool service.

Reflash HMD with previous firmware with the DFU workaround with commands MS-DOS(see sweviver video for dummies).

Restart windows and unplug your HMD.

It should work fine again.

Hopes it helps.

neal_white_iii · October 2, 2021, 4:21pm

Thanks for the suggestion. I did all of that already (three times with different versions), except the nVidia drivers (which are already the latest). The one thing I didn’t do is uninstall PiTool, so I’ll give that a try.

mol · October 2, 2021, 6:26pm

I had the same problem. Spent a whole night trying to force headset into DFU mode with the annoying 3-button move. The only thing that worked for me was to only install pitool 270, and clean up the crap drivers that Pitool leaves after each failed usb insertion. Unplug the headset, open Device Manager, then enable “Show Hidden Devices” and delete every one of the “Unknown USB Device” under USB Controllers heading.

After that I had by trial and horror find an usb 3 port with enough power and force DFU mode, then use dfu exe. The damned thing wouldnt properly flash any new versions of firmware but 298 worked.

I guess I have to stay on this versions until Pimax releases a non-beta versions and at least 10 other people verify that it actually works… 90Hz mode isn’t working for me on this fw with latest nvidia driver.

neal_white_iii · October 2, 2021, 8:02pm

Yeah, I really hate that too. I have large hands and it’s quite hard to fit three fingers on the tiny switches (which need to be wider apart for me). I usually use a finger and cover both volume buttons with my thumb. It’s awkward but it’s easier for me. The hardest part is unplugging the USB port from the back of my computer, which means I have to crawl under my desk and use a flashlight. This was really a pain in the butt, since the headset frequently reverted to standard mode after a few seconds.

@hammerhead_gal, for future headset models, can Pimax change this to an easier method, that doesn’t require unplugging the headset? I know this is possible, since PiTool does it automatically, during installation. How about an “Enter firmware update mode” button in PiTool? It already has that functionality, all that needs to be done is to add a button to the UI. Even better, allow the user to specify a firmware file to download. Then we wouldn’t need to mess around with DFU and the Command Prompt. Please submit a request to the development team. Thanks!