Using AH-64D IHADSS causes burn-in in Varjo Aero headset displays

[Simonster83]

Just noticed that after flying a bit longer session with the Apache, some IHADSS display elements have made a burn-in image in my Varjo Aero displays (the parts that are always stationary, eg. crosshair and altitude change scale). I guess I might just have a bad pair of displays, but to mitigate the issue, could the IHADSS elements be forced to move a couple of pixels once in a while? Somekind of automatic offset that wouldn't be even noticeable, but would prevent these kinds of burn-ins?

I think my Varjo Aero headset is quite AH-64 specific from now on...  

Edited February 12, 2024 by Simonster83

[BIGNEWY]

Hi, 

Ive not noticed any issue here with the G2 and I fly the AH-64D more than anything else currently. 

I tend to reduce the brightness on my IHADSS so maybe why, are you adjusting the brightness or leaving it default? 

thanks

[Simonster83]

I also used to have G2 and had no problems with it. So maybe it's just a Varjo Aero specific issue (or bad panel quality). I also usually reduce brightness on the symbols, so I don't think that's the problem. I'm getting a replacement headset, but I guess I'll need to be more careful with that one if the Aero is so sensitive to burn-in.

Just a heads up for Aero users and if someone is willing to make a mod to offset the sights, that might be helpful. Propably wouldn't be very high priority to ED when it might affect only a handful of users.

[St4rgun]

It's an OLED display after all, so I'm not surprised it's prone to burn-in. The G2 is an LCD panel display, so no burn-in is possible there.

But shifting the image by 1-2 pixels idea is good, unfortunately there could be areas which are getting permanent exposure even then.

[edmuss]

It's not an oled panel.....

Mini LED displays in varjo headsets.

I believe that there is an "anti-burn in" routine that varjo can carry out, I would ping their support.  If I recall correctly it was something along the lines of forcing the displays to a bright white for a time to reset the panel, not sure if it was a public thing or just a dev option.

[maxTRX]

My G2 is safe.  My head shakes like crazy as evident in my raw vids ,  oled or lcd, not a  chance for burn-in.    Somehow my brain tunes the shakes out when using VR.

[Simonster83]

8 hours ago, oldcrusty said:

My G2 is safe.  My head shakes like crazy as evident in my raw vids ,  oled or lcd, not a  chance for burn-in.    Somehow my brain tunes the shakes out when using VR.

Crosshair and some other elements stay fixed in relation to the displays (move with your head), so it doesn't really help shaking your head. But don't worry, with G2 you are safe.

I've contacted the support and sending the headset to them today. I guess they will either replace the headset or try to fix it. If I'll get the same issue again, I might try to do that "anti burn-in" myself.

[maxTRX]

Out of curiosity...  was your monocle set to max brightness or close to it in most of your flights and was it on nonstop?  Just trying to get an idea in case I ever decide to get Varjo or other headset with similar display.

[Simonster83]

2 hours ago, oldcrusty said:

Out of curiosity...  was your monocle set to max brightness or close to it in most of your flights and was it on nonstop?  Just trying to get an idea in case I ever decide to get Varjo or other headset with similar display.

It might have been at max during daylight (not sure what it defaults to). During night I turn the brightness down. It was on nonstop for couple of mission, so maybe two hours?

Propably it is a good idea to turn the monocle off always when you don't need it and turn the brightness as low as possible.

[St4rgun]

3 hours ago, Simonster83 said:

... It was on nonstop for couple of mission, so maybe two hours?

Propably it is a good idea to turn the monocle off always when you don't need it and turn the brightness as low as possible.

Ouch! That sounds really bad. I had no idea that such a "short" time is enough to cause a burn in with those displays...

In DCS flying 2 hours is nothing. Plus flying the Apache without IHADSS is not the intended use IMHO...

Edited February 14, 2024 by St4rgun

[Str][ker]

I've heard of this issue as well on the Varjo discord. I haven't heard of it for a while though so I had assumed it was resolved. I guess it wasn't.

[YoYo]

On 2/12/2024 at 1:22 PM, Simonster83 said:

Just noticed that after flying a bit longer session with the Apache, some IHADSS display elements have made a burn-in image in my Varjo Aero displays (the parts that are always stationary, eg. crosshair and altitude change scale). I guess I might just have a bad pair of displays, but to mitigate the issue, could the IHADSS elements be forced to move a couple of pixels once in a while? Somekind of automatic offset that wouldn't be even noticeable, but would prevent these kinds of burn-ins?

I think my Varjo Aero headset is quite AH-64 specific from now on...  

 

Interesting, no this problem on the Quest Pro. Looks more like question for producer - Varjo. Personally I always turn down the brigness of IHADSS in Apache. Default are too bright for me and cover ground details.

[Simonster83]

Adjusting the IHADSS location is a workaround solution for a problem I had with screen burn-in (or lcd retention) with Varjo Aero headset, it might be a good idea to move the IHADSS location once in a while a few pixels so it won't always stay in the same spot!

But unfortunately it is at least slightly bugged, not all elements of the IHADSS follow the adjustment. Eg. cueing dots dont move when adjusting.

 

Edited April 11, 2024 by Simonster83

[Xtorris]

I also noticed shrinking, or enlarging the IHADSS causes horrible amounts of parallax. Bad enough that is becomes really difficult, to tell how far away a waypoint actually is, by looking at it through the IHADSS.