Jump to content

Recommended Posts

Posted

hello all, i hope this question has not been asked. if so, i apologize. i seem to have two issues with TGP 'whiteout' and contrast adjustment. i am coming into target from the west all is well. i drop a few bits of ordnance. i do a regress to a safe distance. then i come in from the south and pointing at same target area the tgp image is like someone is shining a flash light into the optics. it is impossible to see the same targets as before. sometimes moving the tgp around a little, zoom a little, or change FOV, the targets may again be visible. i have to guess where the target is. i have seen posts where the OP says similar issue when a bomb explodes. not sure if this is same or another issue. also knobs do not seem to do anything to sharpen the image. any ideas? thanks!

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted

https://forums.eagle.ru/showthread.php?t=272484

 

of course i found something similar. the post implies this is a DCS general issue. i fly A10, F16 and F18. I am going to try on the other modules too. i will try updating drivers to but i am usually with a few days / weeks in doing those.

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted

Been this way for the last 3 months since 2.5.6 - Its a real issue have highlighted across numerous posts.

 

You would think FLIR would be a priority even over A2G radar - ridiculous really especially with JTAC smoke & laser you cannot see any of the targets.

 

So absolutely ruined use of JTACS at night, which in turn ruins alot of very good campaigns such as A10C Operation Piercing Fury and as for multiplayer, it has ruined night op's on our server.

 

Worse is the ground and aircraft night lighting if a moon is present, ground vehicles glisten from 15 miles away, so obvious and get picked off by CAS, fed up of reporting it to be honest to ED and nothing being done.

---------------------------------------------------------------------------------------------------------------------------

 DCS & BMS

F4E | F14B | AV-8B | F15E | F18C | F16C | F5E | F86 | A10C | JF17 | Viggen |M2000 | F1 |  L-39 | C101 | Mig15 | Mig21 | Mig29 | SU27 | SU33 | F15C | AH64 | MI8 | Mi24 | Huey | KA50 | Gazelle | CH47 | OH58D | P47 | P51 | BF109 | FW190A/D | Spitfire | Mossie | CA | Persian Gulf | Nevada | Normandy | Channel | Syria | South Atlantic | Sinai | Kola | Afgan | Iraq

 Liquid Cooled ROG 690 13700K @ 5.9Ghz | RTX3090 FTW Ultra | 64GB DDR4 3600 MHz | 2x2TB SSD m2 Samsung 980/990 | Pimax Crystal/Reverb G2 | MFG Crosswinds | Virpil T50/CM3 | Winwing & Cougar MFD's | Buddyfox UFC | Winwing TOP & CP | Jetseat

Posted

Did you try to delete the DirectX-Shadercache? This fixed the issue for me - at least for my F-16C.

[Modules] A-10C, A-10C II, AH-64D, F-4E, 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, 128 GB DDR5, 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

Posted

It's a general DCS issue. It's likely a part of the FLIR modeling they're working on, that's made it into the game. It needs a lot of tweaking for sure, namely some kind of auto gain control and some temperature level assignments to the existing effects (as in the initial explosion being much hotter than the resulting fire and smoke, so the explosion blanks the FLIR, but only for a second).

Unfortunately, none of the mentioned methods seem to be fail proof (chimney smoke to zero, delete fxo+metashaders in Saved Games and/or in Bazar+Repair, deleting shaderchache). The issue pops up from time to time and I personally can't really pinpoint why/how it comes and goes. Sometimes it fixes itself without any action of my own.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

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

Posted
Unfortunately, none of the mentioned methods seem to be fail proof (chimney smoke to zero, delete fxo+metashaders in Saved Games and/or in Bazar+Repair, deleting shaderchache). The issue pops up from time to time and I personally can't really pinpoint why/how it comes and goes. Sometimes it fixes itself without any action of my own.

Well... so let's hope, ED will fix this soon.

[Modules] A-10C, A-10C II, AH-64D, F-4E, 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, 128 GB DDR5, 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

Posted

thanks for follow-up posts. i updated to latest nvidia driver. deleted the folders. lowered smoke density. i have yet to do shader cache. i will do further testing.

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...