reported earlier FLIR Screen totally black-white after bomb explode

[Ramsay]

Thanks Ramsay. Sounds like a very basic and solvable bug. Hope ED can raise to the occasion.

Nope, not so easy.

 

After playing a MP session tonight, I tried to recreate the render bug and couldn't.

 

Tried deleting temp files, clearing the fxo and metashaders2, etc. and there's no way I can reproduce what I saw/screen shot earlier ?

 

The IR Mav render in the replay stubbornly remains correct i.e. as seen in post #71.

 

... and then 5 minutes later, it renders incorrectly but subsequent replays are good again ?

Edited June 14, 2020 by Ramsay
Still trying to reproduce the FLIR fault in a reliable way.

[hein22]

Nope, not so easy.

 

After playing a MP session tonight, I tried to recreate the render bug and couldn't.

 

Tried deleting temp files, clearing the fxo and metashaders2, etc. and there's no way I can reproduce what I saw/screen shot earlier ?

 

The IR Mav render in the replay stubbornly remains correct i.e. as seen in post #71.

 

But it's not a matter of reproducing the issue, that's easy, just install the game and play and everyone will see the FLIR is wrong.

[Stubbies2003]

Can you show me some screenshots of what you are seeing in this instance? A track as well so I can make sure I am replicating just as you see it. Right now I don't see this type of issue.

 

 

Refer to Ramsay picture/first video below your post I am responding to as it demonstrates the white out via smoke quite well.

[toilet2000]

Why should it, according to the TGP FLIR image, the smoke is COLD (Black is HOT, White is COLD), yet the warm light background is now dazzled/overexposed by the cold white obscurant.

 

There are issues with what's cold and what's hot in DCS because it simply isn't simulated at all currently. But as you can see from the videos I linked previously (see:

), it should absolutely washout during explosions, and for a fairly long bit of time.

[Zarma]

No problem if the screen turns blank at impact but when the bug is present, you cant use the FLIR to search a target because as soon as you look "close" to a burning target, the screen turns blank even is "close" is many hundred feets.

[some1]

This is still an issue in various planes, today the display in A-10C went full white after Maverick got in the view (maybe smoke effect is a culprit?). When I restarted the game the image was better, but there are still weird white blobs instead of smoke from burning objects in both A-10 and F-18.

 

IR:

 

CCD:

[some1]

And the FLIR went completely south on me today. What a waste of time.

I have a suspicion the smoke from Maverick launch can trigger the issue, just like the smoke from chimneys (which I have disabled).. but it's just a suspicion.

 

 

[NineLine]

A short track of the issue would be great, although it is reported, it would be nice to be able to submit new items for the team.

[some1]

I played the attached track several times, restarting DCS with each attempt. Just start DCS, replay track, exit to desktop, start DCS, repeat... Not changing anything in the system, no shaders reset or anything. And I randomly get one of the three results:

 

1. everything looks fine.

 

 

2. medium garbage, but usable.

 

 

3. completely useless as soon as smoke gets in the view.

 

 

Sorry if I sound annoyed, but this game breaking issue is still here despite being reported almost a year ago.

flirWhiteout.trk

[BIGNEWY]

Hi

 

Thanks for the post, I am not able to reproduce on my machine.

 

Can I ask you if you are using any shader mods like the VR one or reshade?

 

Also can you take a screenshot of your settings for us,

 

we will continue to try.

 

Thank you

[some1]

Here are my settings, no reshade or any shader mods (or any mods I can remember). The issue seems to happen in both VR and 2D:

 

[NineLine]

I tried with those exact settings, and no issue here, will see what BN sees as well.

[Harker]

I also see the behaviors some1 describes. Different starts of DCS can lead to any of the above scenarios, without nothing changing in the meantime. I have also tried with and without cleaning the fxo and metashaders2 folders in Saved Games between DCS restarts. The issue is not consistent.

 

My settings are attached.

[some1]

I also checked on a different PC (a laptop with GTX1050) with a vanilla DCS install, having only Hornet, PG and the Harrier installed.

 

2 out of 5 DCS runs, I got the issue. Not the total whiteout, but the intermediate issue where the smoke doesn't blend correctly with the background. (https://i.imgur.com/pfPqbSQ.jpg)

[Andrei]

@BIGNEWY, @NineLine

I have been personally hunting this bug for couple months (2769). I can confirm every single word that the gents here are reporting. There is this issue, and it happens *sometimes*.

 

You will most likely will never be able to reproduce it by watching a track. It can happen on any machine, I think, but under a specific set of circumstances, which are not replicable in track replay.

 

I know that it doesn't help a lot with getting to the root of the problem, just sharing own observations after looking at it for a while.

 

It goes as far that I have an issue when writing the track. Two minutes later after replaying the track I no longer have it :)

Edited July 30, 2020 by Andrei

[some1]

It is replicable in track replay for me, but simply not every time I start DCS.

 

I also get this "intermediate" corruption more often than total whiteout. Which may be harder to notice and some people may have the issue not realising something is wrong. But once you know what to expect, it's easy to spot:

 

Good: https://i.imgur.com/7KKGNAK.jpg

Bad: https://i.imgur.com/pfPqbSQ.jpg

[Shadow KT]

This is the same issue with the A-10 TGP where hot stuff like exhaust from missiles and explosions white out your FLIR view. I've send track as well...

 

Super inconsistent, normally I have to delete shaders couple of times to fix the issues

[Harker]

This is the same issue with the A-10 TGP where hot stuff like exhaust from missiles and explosions white out your FLIR view. I've send track as well...

 

Super inconsistent, normally I have to delete shaders couple of times to fix the issues

I think it's a DCS-wide issue. When it occurs, it seems to occur for all FLIR sensors, since I they probably all share a common FLIR renderer.

[hein22]

Hi

 

Thanks for the post, I am not able to reproduce on my machine.

 

Can I ask you if you are using any shader mods like the VR one or reshade?

 

Also can you take a screenshot of your settings for us,

 

we will continue to try.

 

Thank you

 

You couldn't? I don't understand, the issue is there, doesn't seem to be dependent on the PC but DCS.

[Invisibull]

Latest on this? Just got the A10C II and the TGP/Mav screen are mostly unusable if there's smoke around. Same with the Viper. None of the workarounds seem to consistently work.

[Sn8ke]

I have reported this, however have not been able to produce a track because it doesn’t occur everytime. May be dependent on the map, and other specific factors, however this is an issue making night strike missions almost impossible.

[Tholozor]

From my own experience, something may be related to shader compiling. Sometimes when I notice the issue occur, I close DCS, delete fxo and metashaders in Saved Games, restart DCS and recompile, and it goes away. Not every time, but if I do it enough, it eventually does.

[BIGNEWY]

This is probably related to the chimney smoke setting, set it to zero it should help.

[Tholozor]

Chimney smoke is already set to 0.

[Harker]

This is probably related to the chimney smoke setting, set it to zero it should help.

Already set to zero for months now and I also tried setting heat blur to off, as another poster suggested. Doesn't seem to help or at least it does not eliminate the problem.

 

The weirdest thing is that I'll delete fxo+metashaders2 in Saved Games and that might help or not help at all. And one time I'll launch DCS and it'll work correctly for the entire session, no matter the aircraft. Seems like it's something that changes upon launching DCS (or restarting your PC or waking it up from Sleep?), I don't know.