A-10C TGP Ridiculously Bright At Night After 2.5.6 Update

[The Burrito]

Observe the very long post showing screenshots.

 

In 2.5.6, the display of the TGP (though not the Maverick, but then again it might only have been minimally affected) has gotten so bright at night it requires tuning of the contrast and brightness when it was never needed prior to the update.

 

This is how they looked in the last 2.5.5 Open Beta build:

 

CCD

 

BHOT

 

WHOT

 

Nothing has been changed, this is all default settings.

 

This is the same settings, looking at generally the same area, but farther away in 2.5.6 and its patch(es). It's the brightness overall that's strikingly different:

 

CCD

 

BHOT (Only usable without MFD brightness/contrast tuning if gain is set to 8 and level is set to 0)

 

WHOT (no appreciable change when setting gain and level)

 

Now, if I were to lower the brightness to 9, set the contrast to 30:

 

CCD

 

BHOT

 

WHOT

 

It becomes a little more manageable, though the CCD mode turns completely black if I set contrast to 32.

 

At stock gain and level settings but with adjusted brightness and contrast, this is what smoke of any kind does to the TGP:

 

BHOT

 

WHOT

 

My gain and levels are up, but if it's at 4L/4G or balanced in any way then smoke completely washes out the TGP video.

 

This is what smoke looked like in 2.5.5 OB:

 

BHOT

 

WHOT

 

[EDIT] I'm told that night mode is actually brighter than day mode. I'll have to check that when I'm able.

Edited March 9, 2020 by The Burrito

[Emmy]

The displays certainly have a glow about them. Like someone patterned them after an overexposed photo.

[Vanguard]

I haven't noticed anything new, even in 2.5.5, first thing I did after startup was brightness 10 on the left and brightness 15-20 on the right, contrast 31, and those figures still work well in 2.5.6 for me. Are you sure both default screenshots are in the same day/night setting for the MFD?

[Harker]

It's not specific to the A-10C, same thing happens in the Hornet as well. Some times of the day more than others. FLIR often becomes unusable.

 

Also keep in mind that time of day is not the best way to test close to sunrise/sundown, since I noticed that the same TOD will correspond to slightly different sky brightness etc in 2.5.6 (more correct than 2.5.5). Of course, that does not apply for things like 00:00 and 12:00.

[The Burrito]

I haven't noticed anything new, even in 2.5.5, first thing I did after startup was brightness 10 on the left and brightness 15-20 on the right, contrast 31, and those figures still work well in 2.5.6 for me. Are you sure both default screenshots are in the same day/night setting for the MFD?

 

 

I actually just realized that the first three screenshots are in day mode. The rest are definitely in night mode, but I can still clearly see everything pre-2.5.6, even without adjustments. In 2.5.6, switching to day mode just makes it worse. Night mode is what you see in the rest of them.

[Vanguard]

I'm not sure what to say mate, I'm on vacation and can't test anything but I'm fairly certain with the playtime I had before leaving, brightness 15, contrast 31 is what I used and I needed to tweak it in both 2.5.5 a d 2.5.6 every flight.

 

Day and night btw, because it's not obvious, just store two different configs with night being aboit 50% IIRC, day is 32/31/64 and night is 15/31/32 brightness/contrast/symbology. I don't mean it dims 50%, they are separate configs, so adjust day to whatever, switch to night, it will be 15/31/32, not 50% of your day setting.

 

Many of the comments floating around in other threads relate to most folks needing to adjust their gamma setting because of the lighting update. I too tweaked by gamma after the update, which is perhaps why I don't notice a difference because I used that to normalize the overall lighting. Perhaps your gamma needs tweaking or inadvertantly got reset after update.

[The Burrito]

Many of the comments floating around in other threads relate to most folks needing to adjust their gamma setting because of the lighting update. I too tweaked by gamma after the update, which is perhaps why I don't notice a difference because I used that to normalize the overall lighting. Perhaps your gamma needs tweaking or inadvertantly got reset after update.

 

 

My gamma is default. I've never changed it.

[Emmy]

It's not specific to the A-10C, same thing happens in the Hornet as well. Some times of the day more than others. FLIR often becomes unusable.

 

Also keep in mind that time of day is not the best way to test close to sunrise/sundown, since I noticed that the same TOD will correspond to slightly different sky brightness etc in 2.5.6 (more correct than 2.5.5). Of course, that does not apply for things like 00:00 and 12:00.

 

Happens in the F-16 as well but there’s a BRT / DIM switch which helps.

[Harker]

Happens in the F-16 as well but there’s a BRT / DIM switch which helps.

The brightness switch on the MFD? I just checked, this only affects the symbology right now, not the TGP image. It's the same for the Hornet.

[Vanguard]

My gamma is default. I've never changed it.

 

Like I said, that may in itself might be the issue, many peeps including myself felt a need to adjust it with the lighting changes in the latest patch.

 

https://forums.eagle.ru/showthread.php?t=264248

 

The good news is, it's possible to adjust gamma while in flight. I angled my view so the TGP and cockpit controls below it were still visible when I brought up the options menu, and adjusted it that way until it felt right. I think I ended up dropping down to 1.8, but the number will be dependent on your monitor, etc, which is why its tweakable in the first place.

 

Long story short, gamma will have a big impact on that white TGP screen.

[Vanguard]

On a similar note, anyone know if there is a way to change the default brt/con of the MFDs? It is a bit bothersome tweaking it before every flight.

[kunterbunt]

I do not even know how to change brightness. It keeps resetting back to default whenever I move to a different screen. Do you need to save the setting? Chucks guide never mentioned something like that.