IR issue since last open beta (2.5.4.30038)

Don't have both installed only OB so not sure if this works but can you do a repair on the stable version then do one on the OB?

Maybe your stable may have the old files from previous flights and for some reason the repair is using those instead of the ones that should go in the OB? Maybe do the procedure to both stable and OB?

Hi,

I have the same theory than you… maybe the OB is copying "corrupted or old" files from stable…

I've sending an MP to NineLine, waiting for the answers…

and perhaps my probs will be fixed soon, I've found a good sale occasion for a GTX1080TI, so next week I'll replace my old GTX970 and this time I hope the problem will be fixed :-P

Thanks for your help

I love the irony - having not had this problem and helped others to fix it, I now have it after the latest OB and have not been able to solve it yet:lol:

I experienced the issue again after having solved it. I followed recipe for fixing it again, and it solved the problem, so I can confirm what the guys advised us to do should work. Must be something with the shaders that is causing this issue.

Noticed some shimmering going on after the past patch but definitely not what we were seeing before. Did the full fix and it appears to be gone. Got to be a shaders issue.

Still getting the smoke blobs and whiteout problem. I tried the suggested fix - all the steps - and it did nothing. It was working well after the last OB update (Hornet TGP) for one day and then broken again, out of nowhere.

Any suggestions? It's really ruining the experience for me :(.

Yeah this is really disheartening. I also tried the method for fixing it and it worked once, after a restart of DCS it's back again and cannot be fixed using the same method.

So, removing the fxo and metashaders folders from the Bazar folder and then running a repair works after you do it enough times, but after a DCS restart it’s back to broken again. Yesterday night I sat for an hour straight doing this over and over again trying to get it working.

So, removing the fxo and metashaders folders from the Bazar folder and then running a repair works after you do it enough times, but after a DCS restart it’s back to broken again. Yesterday night I sat for an hour straight doing this over and over again trying to get it working.

In case it could help, for me with A10c and Hornet this IR issue is graphic driver related : https://forums.eagle.ru/showpost.php?p=4033229&postcount=8

In case it could help, for me with A10c and Hornet this IR issue is graphic driver related : https://forums.eagle.ru/showpost.php?p=4033229&postcount=8

Didn’t work for me unfortunately.

Didn’t work for me unfortunately.

i'm sorry.

Did you try several times, or even with a DDU procedure ? (I've never done DDU because each time I had issue with driver I sorted out without need to use it)

Because 1 or 2 times, with "cleanup" custom driver install, it can fail to solve (it failed for me… took 3 install with "cleanup" procedures !!). I don't know why.

No. I don't feel comfortable running those kinds of software. This problem is up to ED to solve since no other games have this kind of ridiculous workaround solution for this kind of problem. It's like we have to "pump" the game up into working, I might aswell start shoveling coal into my PC and do a rain dance and hope it works.

LOL ! I too find that sometimes DCS is very chaotic with software environment.

Thanks.

No. I don't feel comfortable running those kinds of software. This problem is up to ED to solve since no other games have this kind of ridiculous workaround solution for this kind of problem. It's like we have to "pump" the game up into working, I might aswell start shoveling coal into my PC and do a rain dance and hope it works.

Hi EasyEB,

Try this solutions:

- in DCS option set the smoke density on "0"

- quit DCS and delete fxo and metashaders2 in your saved game/dcs folder

- restart DCS and test ..

in my case it seems that the problem was solved… (not 100% sure because I have to do another flight test but not enough times)

Bye

I also still have this issue. I deleted the fxo/metashader folders several times over without success. I'd rather keep the smoke densitity to 4 as I want to see chimney smoke.

I also still have this issue. I deleted the fxo/metashader folders several times over without success. I'd rather keep the smoke densitity to 4 as I want to see chimney smoke.

Hi,

just deleting fxo/metashaders does nothing… I've tried with different smoke density, but it seems that just the "0" value fix the problem. So I've sacrified the chimney smoke because I prefere to have a non bugged tgp :music_whistling:

and knowing how it goes, it will take years (at best) for the problem to be solved :music_whistling::music_whistling:

Hi,

just deleting fxo/metashaders does nothing… I've tried with different smoke density, but it seems that just the "0" value fix the problem. So I've sacrified the chimney smoke because I prefere to have a non bugged tgp :music_whistling:

and knowing how it goes, it will take years (at best) for the problem to be solved :music_whistling::music_whistling:

I've messed a bit more with this issue - I found something more I think.

1) Initial point my Flir was OK with smoke density to "1" and actual 436.30 driver.

2) I changed smoke setting to "10" (quit and launch DCS) - Flir was bugged.

3) I changed smoke to "0" ONLY (NO delete fxo/meta2) (quit and launch DCS) - Flir was OK.

4) I changed smoke to "1" (quit and launch DCS) - of course Flir bugged. BUT THEN :

5) I reinstall 436.30 driver ONLY - Flir still bugged - I reboot my PC - Flir was OK (with "1" smoke setting)

At this point I changed smoke density to "10" - "1" - "10", FLIR REMAINED OK (see picture with "10" setting). I have no explaination of course but it worked. The thing also is that I did not deleted fxo/metashadders2 so I keep thinking this delete process is placebo concerning Flir bug.

Does this issue persist with the latest open beta?

Yes.

Oh for gods sake.

Yes.

Can confirm, same here. I have this issue with all aircraft I use TGPs with (A-10C, Hornet, Tomcat). :(

This may be... better? I downloaded the last update and when I tested the (F-18C) TGP smoke looked okay. I went back to options and saw that chimney smoke was at 0. Before increasing that value would bring back the blobs and there was no way to get rid of them. This time I bumped chimney smoke to 5 and had no blobs. The flames are inverted (showing black when in WHOT mode), but no crazy auto gain causing a whiteout and no horrible looking smoke/explosions. Maybe progress??

This may be... better? I downloaded the last update and when I tested the (F-18C) TGP smoke looked okay. I went back to options and saw that chimney smoke was at 0. Before increasing that value would bring back the blobs and there was no way to get rid of them. This time I bumped chimney smoke to 5 and had no blobs. The flames are inverted (showing black when in WHOT mode), but no crazy auto gain causing a whiteout and no horrible looking smoke/explosions. Maybe progress??

No I think you just had luck. I've just tried to change chimney/smoke and blob is back. It can be inconsistent but it's still an issue.

Now I'm going to mess again with driver until it works with smoke to 1...

EDIT : cool, my last "procedure" worked again on 1st try, and untill now it lasts as long as I don't touch settings. (set chimney/smoke to setting I want - 1 - reinstall latest gpu driver - 436.51 - launch DCS to test : blob bug still here - reboot PC and launch DCS to test : bug is gone)