The RDN

Hi everyone, Seriously ED?... since months (before summer 2019), there's several threads about this bug (in Hornet, A10C, Harrier and Tomcat sections) without reaction from ED team… I wrote an MP to Ninieline about this and I never had a response… then I wrote to user support and I have this response: Know issue but no time to fix it. Few weeks ago a new thread was opened (in Hornet or A10C section not sure, and no time to search im in job now :music_whistling:), and in these thread we come to the conclusion that the only way to fix it actually, is to set the chimney smoke to 0). And yes with latest drivers installed (and since month there was a lot of latest drivers version :music_whistling:) So there's definitively a bug with IR image rendering with chimney smoke other than 0. and since time it will be good to be fixed… thanks.

Hi everyone, same issue for me and others friends…. since one ore 2 patch (I don't remember exactly) the Stennis don't turn on lights when we call it for landing (in low light conditions or bad weather). I don't have track but if you need I can probably do one this we. Have a nice day

Hi everyone, same issue for me… Have a nice day :pilotfly:

Hi everyone, Acutally the only solution to fix this issue ist to set the chemey smoke to 0. @NineLine: there is already 3 subject about this issue (in A10C / Hornet / F14 sub-forums) since months, and I write you an MP about this (when I saw there was no reaction on the 3 threads, but you never respond me). since time it will be good to fix it one day :music_whistling: thanks ! Have a nice day all :pilotfly:

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 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

Hi, I've tried your solution and it smell good … I'll see after several flights but I've tried 4 times and the 4 times I have a pretty good image rendering :thumbup: Initially I have 2 on smoke density, and now I've try with 5 (a friend has this setting and has no bug) and it seems ok. Well done!! you're my new Hero of the Day :megalol::smartass::pilotfly:

Hi everyone, from what I see in your second picture, it has nothing to do with object distance view… it's clearly the IR image rendering that is broken (since months, and in "stable" version too, and we have no feedback from ED). There's still 2 or 3 post with this subject (in A10C forum, Harrier forum, F14B forum) once again please ED do something or at least say us if it is tracked, or if there's a way to fix it. Thanks

Hi everyone, IR image rendering bug is still here (since months)… first picture TPOD in TV mode, second one in IR mode… very usefull :megalol: seriously don't tell me is not a gamebreaking bug… it's impossible to target Something near a "burning" area. Please ED do Something… thanks

Hi QuiGon, thanks for testing… I have myself try all know "solutions", but my conclusion is that this bug is totally random… I even bought a new graphic card and have done a totally full install (dcs and cg drivers) and sometimes I have the bug, and sometimes not… :music_whistling:

Hi, yes it's a bug a no only delete fxo and metashaders2 isn't a solution. see those threads: https://forums.eagle.ru/showthread.php?t=239818 https://forums.eagle.ru/showthread.php?t=239907 Please open a report bug for this gamebreaker bug (yes it's gamebreaker because sometimes it's totally impossible to target a zone where they're burning objects), perhaps it will motive ED to correct it… since months we have this issue, and I'm pretty sure that when the TGP for Hornet will come out, this issue will be not fixed… Have a nice day

Hi everyone, I can confirm to … same issue for me

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

Thanks for your help Hornblower (and all others :-))

Hi, thanks for your answer :-) I've a GTX9700 graphic card, with last drivers (I try also a totally new installation of drivers, but change nothing) I had one mod initially (deck crew mod), but when I try the repair / cleaning / fresh install, I've had it deleted, and… nothing change… I'll try to send a message to NineLine, but first I'll wait for today's update, perhaps with a loooooot of chance it will be fixed (Hope Mode hi hi) Another last question: where do you find SkateZilla's update gui? Thanks a lot one more time :-)

Hi, sorry this picture was for the Hornet section, I was in the two threads in same time and this is what happen :-) I'm quasi sure that is the same bug in the 2 case, because both for A10 and hornet I have juste the bug off ugly smoke before repaire, and then after repair and fxo / metashader cleaning, I have the green (for hornet) and white (for A10C) screen. A question: when I do the repair, I've seen that the openbeta is copying files from stable version… can the bug comme from this?... is there a way to repair without copying files from another instance? And I'll be glad to contact Nineline… how do I do this? (I'm a rooky in forum discussions sorry :smartass:) Thanks guys :thumbup:

Hi again :-P here's a Screenshot what I have now… :cry::lol:

Hi again, So I've done the whole procedure (and yes my drivers are the latest version ;-)), it changes nothing… the most disapointing is when I've updated my graphics drivers, it was fixed but juste for one try… second time I've running DCS after that, the bug was here again… and it was just the "ugly white smoke bug"... but now after all those manipulations (delete fxo, repair, etc...), it's worst… when the mav is targeting a zone with burning vehicles, the mav's screen come full green and I see nothing… And still no reaction from ED team…. that's the most disapointing… I'll wait tomorrow's patch, and if not fixed I think I'm done with DCS for a moment… In every case a big thanks for your help guys :-)

ok I'll try after work the "terrain metacaches fix", but if after a totally fresh reinstallation it wasn't fixed, I doubt that it will change something…. Hope Mode ON :-)

I try this solution and now it's worst.... now when the mav is targeting an area with burning vehicles, I have a full green screen, can't see nothing... So I try a fresh full reinstallation, and nothing better... full green screen :cry::music_whistling:

Hi again, for me, after full clear of shaders and repair, was worst... now when my may is targeting a zone with burning vehicles, I have a full green screen, can't see nothing anymore... Once again, habe we news if is that bug reported?... there is 2 subjects for this bug (one in A10C avionics section), and there is no official reaction... Please ED a little word? ;-)

Hi again, After repair, 2 bugs are fixed… MK20 without Efuz works fine, and I can drop again chaff and flares… still the ir tv bug, but this is another subject :-P Thanks guys for your help!

If you're talking about VR performance update, I've understand that it's integrated for Caucasus and Persian Gulf map since 2.5.5.

Hi, yes I've done all like that (release, MFuz VT with HT 1500)… I've no issue before this 2.5.5 patch… but I've a lot of others issues since this patch (mav ir image bug that it seems it's fixed for others, unable to launch chaff and flare…), so tonight I'll try a fresh reinstall… perhaps it could help … in all case thanks for your help :-)

Thanks for answer… so I think I'll try a fresh reinstall… perhaps it will fix it…