ChuckJäger Posted April 28, 2019 Share Posted April 28, 2019 Seems red smoke and new smoke from explosions have a white out effect on the A-10C TGP and AGM-65D's. VFA-113 | Stinger 307 | "Hank" USN OEF OIF Veteran i7-8700K OC'd 4800ghz | Gigabyte GeForce RTX 2080Ti OC'd | 32gb RAM | 2.5TB SSD | Odyssey + | TM Warthog HOTAS | Link to comment Share on other sites More sharing options...
Puma Posted April 28, 2019 Share Posted April 28, 2019 Can confirm. Is this a bug or is the smoke actually hot enough to blind ir? Custom Pit 476 Recruiting i9-12900KF, 32 GB DDR5, Gigabyte Aorus Z690 Master, Gigabyte RTX 2080 Ti, 1TB Sabrent Roket 4+ 2x750GB RAID-0, TrackIR 5 /w clip, CRG9 49” Curved Ultrawide Flight Display+15" Touchscreen+17" Gauges display, Thrustmaster Warthog+7.5cm, Saitek Pro Combat Pedals, Streamdeck, Butt Kicker and pneumatic G-Seat Link to comment Share on other sites More sharing options...
some1 Posted April 28, 2019 Share Posted April 28, 2019 https://forums.eagle.ru/showthread.php?t=239818 Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil T-50CM, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro Link to comment Share on other sites More sharing options...
Harker Posted May 6, 2019 Share Posted May 6, 2019 https://forums.eagle.ru/showthread.php?t=239818Weird thing is that I had this until tonight. Now, my IR behavior seems to have returned to the "old" one. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro Link to comment Share on other sites More sharing options...
EasyEB Posted May 7, 2019 Share Posted May 7, 2019 So what's the status of this? Has it been shadow fixed or is it still an issue? Not keen on updating until it is fixed. Link to comment Share on other sites More sharing options...
EasyEB Posted May 9, 2019 Share Posted May 9, 2019 For me it got worse in the last OB update. Link to comment Share on other sites More sharing options...
IlludiumQ36 Posted May 18, 2019 Share Posted May 18, 2019 Sigh...this has been rolled into the stable update. Link to comment Share on other sites More sharing options...
Puma Posted May 18, 2019 Share Posted May 18, 2019 Ouch. Classic ED. Custom Pit 476 Recruiting i9-12900KF, 32 GB DDR5, Gigabyte Aorus Z690 Master, Gigabyte RTX 2080 Ti, 1TB Sabrent Roket 4+ 2x750GB RAID-0, TrackIR 5 /w clip, CRG9 49” Curved Ultrawide Flight Display+15" Touchscreen+17" Gauges display, Thrustmaster Warthog+7.5cm, Saitek Pro Combat Pedals, Streamdeck, Butt Kicker and pneumatic G-Seat Link to comment Share on other sites More sharing options...
Nealius Posted May 19, 2019 Share Posted May 19, 2019 I'm still not experiencing this issue with 30386 on the PG map. Does it only occur on Caucasus? Certain types of smoke? Graphics driver issue like the cluster bombs a few weeks ago? Link to comment Share on other sites More sharing options...
9echo Posted May 31, 2019 Share Posted May 31, 2019 I'm still not experiencing this issue with 30386 on the PG map. Does it only occur on Caucasus? Certain types of smoke? Graphics driver issue like the cluster bombs a few weeks ago? Hi Nealius, would you mind testing yours in the Caucasus map? I read in the DCS World General Questions MAV thread that you had deleted two folders and tweaked some graphic settings only to find the problem disappearing, so would be interesting to see if this fixes the issue. I experience this on the Caucasus map (does not have any other maps at the moment). SYSTEM: Mainboard MSI B360M Bazooka | CPU i7 8700k @ 3.2 GHz | RAM 2x8GB GDDR4 @ 2400 MHz | GPU Gainward GeForce RTX 2070 Dual Fan | 256GB SSD | Win 10 x64 DEVICES: MSI Optix 24" LED Curved | Thrustmaster Warthog | MFG Crosswind | TableMount MonsterTech MODULES: A-10C | F-14 | F/A-18C | Spitfire | P-51D Link to comment Share on other sites More sharing options...
9echo Posted June 2, 2019 Share Posted June 2, 2019 Has anyone actually fund a workaround to this issue? Or are you playing whilst putting up with it? SYSTEM: Mainboard MSI B360M Bazooka | CPU i7 8700k @ 3.2 GHz | RAM 2x8GB GDDR4 @ 2400 MHz | GPU Gainward GeForce RTX 2070 Dual Fan | 256GB SSD | Win 10 x64 DEVICES: MSI Optix 24" LED Curved | Thrustmaster Warthog | MFG Crosswind | TableMount MonsterTech MODULES: A-10C | F-14 | F/A-18C | Spitfire | P-51D Link to comment Share on other sites More sharing options...
EasyEB Posted June 2, 2019 Share Posted June 2, 2019 I reverted back to the last version without it. Link to comment Share on other sites More sharing options...
9echo Posted June 2, 2019 Share Posted June 2, 2019 How do you revert back to the last version without it? Can you choose the version in the Updater-tool? SYSTEM: Mainboard MSI B360M Bazooka | CPU i7 8700k @ 3.2 GHz | RAM 2x8GB GDDR4 @ 2400 MHz | GPU Gainward GeForce RTX 2070 Dual Fan | 256GB SSD | Win 10 x64 DEVICES: MSI Optix 24" LED Curved | Thrustmaster Warthog | MFG Crosswind | TableMount MonsterTech MODULES: A-10C | F-14 | F/A-18C | Spitfire | P-51D Link to comment Share on other sites More sharing options...
KamiraHusky Posted June 6, 2019 Share Posted June 6, 2019 any idea if this has been fixed in today's release, despite not being on the change list? Brrrrt Link to comment Share on other sites More sharing options...
prof_laser Posted June 6, 2019 Share Posted June 6, 2019 Yes, it's fixed. Link to comment Share on other sites More sharing options...
The RDN Posted June 7, 2019 Share Posted June 7, 2019 Hi everyone, for me it's not fixed in OB 2.5.5 update… and I have deleted all my FXO / Metashaders before try… Stable version in 2.5.4.29167 no bug…. other later versions I have this issue… any idea? Thanks to all.. Link to comment Share on other sites More sharing options...
KamiraHusky Posted June 7, 2019 Share Posted June 7, 2019 Can confirm it was fixed for me last night. https://imgur.com/6c0qg8x Brrrrt Link to comment Share on other sites More sharing options...
The RDN Posted June 7, 2019 Share Posted June 7, 2019 Thanks for answer… so I think I'll try a fresh reinstall… perhaps it will fix it… Link to comment Share on other sites More sharing options...
tobyeez Posted June 7, 2019 Share Posted June 7, 2019 Has the VR update been integrated ? Link to comment Share on other sites More sharing options...
The RDN Posted June 7, 2019 Share Posted June 7, 2019 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. Link to comment Share on other sites More sharing options...
lahsoldier Posted June 8, 2019 Share Posted June 8, 2019 Hi everyone, for me it's not fixed in OB 2.5.5 update… and I have deleted all my FXO / Metashaders before try… Stable version in 2.5.4.29167 no bug…. other later versions I have this issue… any idea? Thanks to all.. Me either and did the same deletions. Asus Prime 390A, Intel I7-8700k@4.8ghz, 32g ram, Nvidia EVGA GeForce RTX 2070, Track IR5, SSD(DCS dedicated), HDD for Win 10. TM Warthog 78051 Track IR5 Thrustmaster pedels Link to comment Share on other sites More sharing options...
Sandman1330 Posted June 9, 2019 Share Posted June 9, 2019 I find it much worse now. It’s good until there’s a hotter source, then it washes out to the point of unuseability (ie as soon as one target is hit and burns, the whole screen just washes out white) I know this is partially realistic, but the effect is extremely overdone. Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2 Link to comment Share on other sites More sharing options...
FoxOne007 Posted June 9, 2019 Share Posted June 9, 2019 I am having a similar issue, where the ground is white in both BHOT, WHOT and CCD making it near impossible to spot targets unless zoomed in to the max level and actually looking out of the cockpit to spot them and place the TGP over it. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
lahsoldier Posted June 9, 2019 Share Posted June 9, 2019 (edited) White and black hot after hits and resulting "hot" smoke. Looks like blobs (same target) Seems like "normal (not white hot or black hot) looks bad over trees. Almost like looking at a page of static on my old TV. BTW these are well past the initial explosion and all. Edited June 9, 2019 by lahsoldier Asus Prime 390A, Intel I7-8700k@4.8ghz, 32g ram, Nvidia EVGA GeForce RTX 2070, Track IR5, SSD(DCS dedicated), HDD for Win 10. TM Warthog 78051 Track IR5 Thrustmaster pedels Link to comment Share on other sites More sharing options...
Harker Posted June 9, 2019 Share Posted June 9, 2019 White and black hot after hits and resulting "hot" smoke. Looks like blobs (same target) Seems like "normal (not white hot or black hot) looks bad over trees. Almost like looking at a page of static on my old TV. BTW these are well past the initial explosion and all.I actually think it's looking much more realistic like that IF that was the explosion. As it stands, they should reduce the delta between the hot smoke and the environment, but increase the "temperature index" of the explosion, so we still have a more localized whiteout for a few seconds after the explosion. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro Link to comment Share on other sites More sharing options...
Recommended Posts