The part of pimax software it has quarantined is the Oculus compatibility. Look at the filename.
The Pitool window display is still bugged if FXAA is enabled in the Nvidia control panel⦠But at least it is still visible/usable, just all clear blue.
Better to use fxaa per ap no need to have it on globally. Strange Amd while has other issues doesnāt have this issue.
I usually just turn on things like that on Game ap settings.
Mixed reality has its own bugs. My lenovo explorers right controller always complains about low battery since a software update >.>
When using 120hz or 90hz and decrease all brightness and contrast, I found little blinking dots.
Last time I test hp reverb, has same issue. May be about cable.
Who know how to set brightness for 120hz? I have to increase the contrast, but still not good enough.
I think the brightness at 120 Hz is something only Pimax can fix. There may be limitations that they cannot overcome, without a headset redesign. (I hope that is not the case.)
Why? The headset panels are LCD and the pixels take a period of time to change from one color to another. To hide that smear, the LED backlight flashes on at the moment when the pixels are at the desired level for a frame. Then the LED lighting is turned off, while the pixels transition to the next frame. Apparently, when running in 120 Hz, the amount of time the LED is on has been reduced (since the pixels are in transition more often).
The solution is to leave the LED on for a longer period of time (smearing the transition from one frame to the next) or using brighter backlight LEDs. Brighter LEDs use more power, which might lead to other problems. If the LEDs are as bright as they can get, the hardware itself may need to be upgraded. This is a great new feature, but it was never promised and this is a beta version of PiTool after all.
Wait for the next PiTool and/or firmware upgrade, to see if Pimaxās engineers can find a fix. Until then, set your PiTool settings for brightness and contrast as best you can or run at 90 Hz.
@Matthew.Xu (Or who should we @ for bug reports?)
I experienced an issue with the beta today. Today was the first time that I took the headset out of 120hz mode since updating. It took me around 8 tries to get it back into 120hz mode afterward.
Are there any logs that are automatically captured that I can provide?
When I started Pitool it had 90hz selected in the drop-down despite the headset being 120hz when I last turned it odd. I attempted to select 90hz then 120hz to make sure that it was in 120hz mode. When I first changed the headset to 90hz mode it reconnected three times (black screen then windows device connect sound). Afterward I selected 120hz and the headset reconnected 3 times, however it was still in 90hz. I retried this 5 times but got the same results. After the headset restarted 3 times it was in 90hz mode despite selecting 120hz. Steam even reported 90hz. I tried setting the backlight to low and fov to āsmallā before changing to 120hz but it still didnāt help.
I tried changing to one of the other hz settings but it still restarted three times and ended up in 90hz mode.
Eventually I switched settings back to ānormalā fov and high backlight, started steam vr and then changed to 120hz while steam was open. The headset restarted and steam vr closed but yhis seemed to work but I donāt know if it was a coincidence. So the headset ened up back in 120hz mode again after all those tries.
@Sean.Huang Please note the bug report above. As I mentioned in a previous post (far above), I had similar issues switching between 80 and 72 Hz. I had to reboot the headset repeatedly and finally, restart the service also.
Hi Neal
What you are describing is correct for a display with modular pwm control of the backlight, this as you describe will switch the backligt on/off to improve percieved refreshrate, alot of monitors have had this feature. From what I am seeing looking through my HMD these are just low persistance displays eg. low Grey to Grey response. I could be wrong but I dont think so.
Yes, they are low-persistence, but my understanding is that the LED backlight flashes, so that it is only on when the pixels are showing the correct RGB values (not during the transition phase). That would certain explain why there might be a problem with 120 Hz mode. If the LED backlight was constantly on, why would there be a problem with dimness?
We can do a whole lot of thinking of this subject, but in the end only Pimax engenieers can do anything about it
Hope they get it fixed, as latency is much lower in 120hz
I think we all have these issues , stopping and restarting piservices normally helps
Replying to myself here because I found out (from Manzilla I think) that only if SteamVR is running first, it worked to change refresh rate. I tried this with setting my 5K XR to 64hz and it worked. Maybe all fps switches need to have SteamVR running first to have the correct effect (speculation).
Im assuming this version is bad? Guess ill avoid it
I wouldnāt say itās bad. Peopleās experience is uneven.
Iām using 197 and the only issue Iāve seen is difficulty changing the refresh rate. I have an 8K, so 120 Hz will never be available for me. I havenāt seen the stuttering issue that others have complained about.
What I like is that my framerate is ~15% higher. Iām mostly hitting 80 Hz now, in Elite D with my preferred settings. (PiTool quality at 1 and SteamVR at 50% with FFR on Conservative.)
Okay, so where is the backlight brightness update for 120hz. Itās so annoying to play in a dark lighting environment using 120hz mode when we should be able to use backlight settings for the headset.
The firmware update took a couple tries for me and it can take a few tries to change the refresh rate. But other than that 120hz mode works fine for me and I have not had any other problems. No studdering but I also didnāt have studdering on .180
Avoid it if you want. But it doesnāt seem all bad.
The last couple of weeks my headset (5K+) has been crashing within minutes. The screen goes black and PiTool reports it as disconnected. I think it might be related to the latest firmware update.
Has anyone else had this experience?
To make sure, I should revert to an earlier firmware version. There should be a guide somewhere on how to do that and where to find old firmwares, but I canāt seem to find it ⦠Could anyone post a link please?
Is this what you are looking for?
I have not had this issue yet. Hopefully rolling back will fix it.
Edit: Sorry did the reply wrong. @wilcovertegaal so you get a notification.
Thanks mate, much appreciated! Will check if it solves the issue and report back.