reported earlier IR saturation

[maxTRX]

Old issue, just a reminder. I'm on newest nvidia drivers, shaders deleted (windows and DCS)

 

30sec. clip:

 

 

[BIGNEWY]

Hi 

 

do you have a track replay so we can test the same circumstance by any chance? 

 

thanks

[maxTRX]

24 minutes ago, BIGNEWY said:

Hi 

 

do you have a track replay so we can test the same circumstance by any chance? 

 

thanks

 

Sorry, didn't save it since this issue pops up every time FLIR or IrMav is used. It is less severe if further away from explosions and zoomed out.

My vid recorder is running nonstop on every mission so it was easy for me just to grab a clip. I'll try to save a track later on.

[Sn8ke]

I've reported this before as well. Old problem never been fixed. 

[dorianR666]

if i recall correctly, this bug is in DCS since 2.5.0

which would make the bug exactly 3 years old in 2 days.

[imacken]

It seems amazing to me that this is still going on.  I know there are other priorities, but this is kind of fundamental.

 

I think BN said in one of the other threads on this topic that it is unlikely to be fixed as the team are working on a new FLIR model.

 

Clearing the shader folders resolves the issue for a while, but the issue returns at some point. CCD the only reliable way to avoid this.

 

It's the same with the MAV FLIR.