Nealius Posted May 6, 2020 Share Posted May 6, 2020 I was flying a mission up into central Iran and found the TGP FLIR to be useless. Whenever there was an impact, the FLIR (regardless of WHOT/BHOT) would completely blank out. At certain zoom levels it would also blank out. Typically after an impact, NARO or zoomed-in would blank out, with WIDE or zoomed-out working fine. After a period of time and before the next attack run, WIDE or zoomed-out would blank out, with NARO or zoomed-in working fine. TV mode was unaffected by any of this. Long Track File Link to comment Share on other sites More sharing options...
Harlikwin Posted May 6, 2020 Share Posted May 6, 2020 That sounds right ish for a flir sensor being overloaded. New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1) Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really). Link to comment Share on other sites More sharing options...
Nealius Posted May 6, 2020 Author Share Posted May 6, 2020 Read the body of my text and not just the title, please. See video: 3-RmnkCQHXE Link to comment Share on other sites More sharing options...
Harlikwin Posted May 7, 2020 Share Posted May 7, 2020 Yup that looks abnormal. I haven't flown AG in the viper lately but it didn't used to do that. New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1) Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really). Link to comment Share on other sites More sharing options...
some1 Posted May 7, 2020 Share Posted May 7, 2020 https://forums.eagle.ru/showthread.php?t=253277 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...
Nealius Posted May 7, 2020 Author Share Posted May 7, 2020 Great, so it appears to be a DCS-wide issue. I recall the A-10 had the same blobby smoke problem ages ago, but having the entire screen saturated is a new one. I thought I had cleared my fxo and metashaders folders before this mission, but it's possible I didn't. Link to comment Share on other sites More sharing options...
Gunrun_KS Posted May 8, 2020 Share Posted May 8, 2020 I fly the viper every day and have yet to see it, that's wild. I don't use narrow, but I do zoom in. Maybe it has something to do with that? [sIGPIC][/sIGPIC] I7 4790K / EVGA 1080ti SC / 32GB DDR3 / 1TB SSD / Oculus Rift S / X-56 / MFG Crosswind V2 / ButtKicker + Simshaker for Aviators Link to comment Share on other sites More sharing options...
Nealius Posted May 8, 2020 Author Share Posted May 8, 2020 Still happens when zooming in WIDE. Link to comment Share on other sites More sharing options...
toutenglisse Posted May 8, 2020 Share Posted May 8, 2020 The 3 Tgp (A10-F16-F18 ) are also working ok in Bhot/Whot modes on my side actually (but I had the bug before). What is different from before on my side is that I'm not able to break it again by changing options (before, just changing chimney smoke to other than zero, or changing AA would break Flir but now I'm unable). I use latest NV driver (445.87) installed with prior cleanup of previous driver, BUT I've also done something new that maybe you can try, Nealius and others, if your Flir is still broken : I've deleted Directx Shader Cache using windows Admin Tools / Disk Cleanup / C: / and tick if not already ticked directx shader cache. Just in case there is a relation - IDK for sure and what "seems" to works for one have random chances to work for another… Link to comment Share on other sites More sharing options...
Nealius Posted May 8, 2020 Author Share Posted May 8, 2020 I just tried again after setting chimney smoke to 0 and deleting fxo/metashaders folders. Same problem. I'll try updating my Nvidia drivers, and might try a mission with static weather instead of dynamic weather. If those don't fix it, I'll mess with the DirectX Shader Cache. Link to comment Share on other sites More sharing options...
macedk Posted May 9, 2020 Share Posted May 9, 2020 Before you all go deep diving into changing your computer settings, please note that it is a work in progress. Poking without a good walkback might brake more than it fixes. Horror story from 4 days ago. Some streamer had a problem with his game of choice and said..."well I have to reinstall windows to fix it". :joystick: So if a light bulb stops working, do u rewire the hole house ?? ;) Be careful outthere :) OS: Win10 home 64bit*MB: Asus Strix Z270F/ CPU: Intel I7 7700k /Ram:32gb_ddr4 GFX: Nvidia Asus 1080 8Gb Mon: Asus vg2448qe 24" Disk: SSD Stick: TM Warthog #1400/Saitek pro pedals/TIR5/TM MFDs [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Nealius Posted May 9, 2020 Author Share Posted May 9, 2020 It't not a work in progress if it affects all TPODs across multiple modules. Link to comment Share on other sites More sharing options...
Geraki Posted May 10, 2020 Share Posted May 10, 2020 Different but could be the same realistic ..... https://www.facebook.com/171823043426849/videos/652487598934974/ Link to comment Share on other sites More sharing options...
DrBackJack Posted May 11, 2020 Share Posted May 11, 2020 Different but could be the same realistic ..... https://www.facebook.com/171823043426849/videos/652487598934974/ That's falcon bms :lol::lol: Link to comment Share on other sites More sharing options...
AstonMartinDBS Posted May 11, 2020 Share Posted May 11, 2020 I've deleted Directx Shader Cache using windows Admin Tools / Disk Cleanup / C: / and tick if not already ticked directx shader cache.Had the same issues and deleting the DirectX-Shadercache fixed it (at least for the F-16C). Thx for your hint! :thumbup: [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
Nealius Posted May 11, 2020 Author Share Posted May 11, 2020 Updated Nvidia Drivers. Updated DCS. Deleted fxo and metashaders2 for the millionth time. Cleaned DirectX Shaders cache from my C drive. I still get a blanked TGP every single time. What's interesting, is that when I fly 2D airstart, the TGP works perfectly fine. When I fly VR cold start, it gets blanked out. Link to comment Share on other sites More sharing options...
AstonMartinDBS Posted May 11, 2020 Share Posted May 11, 2020 Updated Nvidia Drivers. Updated DCS. Deleted fxo and metashaders2 for the millionth time. Cleaned DirectX Shaders cache from my C drive. I still get a blanked TGP every single time. What's interesting, is that when I fly 2D airstart, the TGP works perfectly fine. When I fly VR cold start, it gets blanked out. Obviously we only can wait until ED fixes this issue: https://forums.eagle.ru/showpost.php?p=4327048&postcount=5 [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
Harlikwin Posted May 11, 2020 Share Posted May 11, 2020 Updated Nvidia Drivers. Updated DCS. Deleted fxo and metashaders2 for the millionth time. Cleaned DirectX Shaders cache from my C drive. I still get a blanked TGP every single time. What's interesting, is that when I fly 2D airstart, the TGP works perfectly fine. When I fly VR cold start, it gets blanked out. That's a bummer man. I haven't really seen this with the Jeff TGP, since that's all I've been flying most recently. Does it do it on all your TGP's or just the viper? By updated DCS I assume you mean you did the "repair", and you aren't running any mods? New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1) Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really). Link to comment Share on other sites More sharing options...
Nealius Posted May 12, 2020 Author Share Posted May 12, 2020 Only running Mustang's VR shadows mod. Wondering if that's causing issues. I'll give the Jeff a spin and see if the TGP is messed up in that too. Link to comment Share on other sites More sharing options...
Nealius Posted May 28, 2020 Author Share Posted May 28, 2020 Ran the Hornet and it's an issue with the Hornet too. Just a DCS-wide problem. I've narrowed it down to the smoke. Even an SA-2 launch will blank out the TGP, then once the smoke plume disappears the TGP view comes back. Link to comment Share on other sites More sharing options...
Furiz Posted June 13, 2020 Share Posted June 13, 2020 Only happens when some smoke is near by, be it JTAC or from the burning wreckage. Link to comment Share on other sites More sharing options...
Recommended Posts