I just want to inform you of the risk of image burn in risk. I have the 102 version. Most of the time I am not using it, but it is plugged in sitting on the edge of my desk. I don’t have Piplay running. Yesterday, after not having used the Pimax for a few days, I used it and noticed that the Pimax Logo is beginning to burn into the screen. I quickly went to turn off the logo, and the only way to do this is to use Task Manager to kill the Pimax related processes, PiServiceLauncher first, then PiService, and pi_server.
You may want to implement a screen dimming routine immediately in your software.
What I did to help combat this is replace the default image that appears in the headset.
In the \Program Files\Pimax\Runtime folder, you’ll find a file labeled pimax_default.jpg
This is the image which will appear on the Pimax when it’s on but not in use.
I replaced it with a custom image which isn’t as busy or bright and it’s helped a bit.
Thanks. Great idea. I’m just gonna make it dark, maybe just bright enough to tell it’s on. I wonder what it does without that jpg. When I first got it and plugged it in without the driver installed there was some image that made it look like it was physically broken. Not cool
Mine does not dim. Maybe my sensor borked? It doesn’t go dark when I take it off. I have a BE. shrug. Maybe it broke. My desk is not safe from traffic, and a couple of times the headset has been pulled off the desk onto the hard floor.
In case this has happened to anyone else, there are things you can do to fix it, as well as other failing pixels. First you could run a video like this:
And there are also other utilities that will do similar effects to pixels, even designating more specifically which pixels. I have used such programs in the past with about a 50% success rate on dead pixels. I’m not planning on sitting and running one of these anytime soon for such a small defect. I’m too busy playing with my Awesome Pimax and NOLO. But some time I probably will give it a try.
