AstonMartinDBS

Great!

I observed the same and reported the issue (which is related to the ATFLIR as well as to the LITENING) already in the bug section. I hope, ED sets a high priority to fix this issue. It's an absolute no-go when a FLIR is only useable under daylight conditions and nearly useless at night or dusk/dawn.

Let's wait and see... I'm optimistic and trust in ED. At least the A-10C (II) pod works under the same conditions.

He is using the LITENING already. But ATFLIR isn't an option, because the issue occurs sadly on both pods (already reported here) Tracking should IMO be dependend on contrast only but not on time of day and/or distance.

This is propably related to an already reported issue:

Did you set TDC priority to the correct DDI?

The already reported and in this thread described issue is still present in the current OB. I'm unable to track the movin' tanks - even under a distance of 1 nm. @BIGNEWY commented there as follows: Tracks: LITENING: FA-18C LITENING PT issue.trk ATFLIR: FA-18C ATFLIR AUTO issue.trk BTW: Sorry for opening a new thread, but the original one has already been closed.

1. Check your bindings for the cage/uncage button, if the Hand-Off doesn't work, even if you've set the SOI to the correct DDI (HARM page). 2. Watch Wags' tutorial and exactly follow the steps: 3. If this still doesn't work, attach a track so we can see, what's goin' on exactly.

At least the issue has been fixed in the OB. Fix in the stable version will follow.

Let us know how you solved the problem, please. I'm still unable to track movin' targets under certain conditions.

Good news: This issue has already been reported to the developers, thanks @BIGNEWY btw. Thread can be closed.

I think the issue occurs, if you look in the direction of the sun, and that in a certain angle. In my mission setup this angle is reached around 05:15 (+/- a few minutes) at an altitude of 25k+ ft. The track F-16C GraphicsIssue9.trk shows, that it is not mandatory to look to the right out of the cockpit. The F-16C is heading to 090, I'm looking straight ahead and the bug occurs as well. I don't know, if other maps are also affected.

I continued testing but didn't manage to find the source of the problem. What I tried so far (summary): Repair/Integrity check of my DCS installation (Steam) Updated to the latest nVidia drivers 466.27 deleted the directories "fxo" and "metashaders2" disabled the XBox Gamebar disabled Steam overlay DCS: different cloud presets for mission DCS: clouds low/standard/high/ultra DCS: civilian traffic low/off DCS: anisotropic filtering 16x/off DCS: terrain object shadows: default/off nVidia control panel: all settings to default (usually I only change vSync to "fast" via nVidia control panel to eliminate stuttering on the ground) Remark: My default settings are marked bold. I didn't have any video issues pre 2.7 with those settings. I used the XBox Gamebar, which automatically downsized the resolution from 4k to FullHD. I didn't find any option to change this setting in the XBox Gamebar. Can you recommend a 3rd parity video recording software?

Disabling the XBox Game Bar did not eliminate the issue unfortunately. GeForce experience was never installed on my system. But thanks for your hints!

I did some further testing. The bug doesn't occure, when I change the mission time from 05:13 to 15:13 or remove the clouds (preset "NOTHING", density 0) But the issue returns, when I set mission time back to 05:13 and select another cloud preset ("Broken 5" for example) or change to the preset "NOTHING" and increase the cloud density (tested with base 8530 ft, thickness 5315 ft, density 6). The graphics option "Cloud" doesn't seem to affect the issue. The bug appears with settings "LOW", "STANDARD", "HIGH" and "ULTRA".

Exactly. The issue is to 100 % reproduceable for me, independent of the used aircraft. Here's another example using the Hornet. Compared to the previous samples I've changed the cloud settings now from standard to high. Track: FA-18C GraphicsIssue7.trk Mission: 000e GraphicsIssuePGDawn.miz DCS Log: dcs.zip DXDiag: DxDiag.zip Capture: Edit: DXDiag attached

I had absolutely zero problems so far. As I already wrote the issue occurs also with other planes in the attached mission. Probably it's related to a certain mission timeframe (sunrise). I saw this bug first during a flight in the mission 510a F-14B AA AIM-7.miz, shortly after WP1 at an altitude of ~25k ft. As you can see in the captured video the issue occurs only during a period of ~2 mins out of a total of ~50 mins mission time. NVIDIA 2080 SUPER, 8 GB GDDR6, latest drivers, never overclocked

Assuming it was a specific problem with the Tomcat, I reported the problem initially in the F-14 bug forum. Later, during further testing I realized, that the same problem occurs also with other aircraft (F-16C and F/A-18C for instance). You can find detailed infos about the issue including tracks and logs in this thread: @NineLine, @BIGNEWY or any other admin: it would be great, if you could merge the threads. Thanks!

Excellent work @Minsky - as always!

Well, obviously this isn't a F-14 specific issue. I've just tested the same mission with the F-16C and F/A-18C and the bug is also present. Mission: 000d GraphicsIssuePGDawn.miz Track: F-16C GraphicsIssue6.trk Log: dcs.zip Maybe any mod or admin can move this thread to the general DCS 2.7 bug subforum? Thanks!

Here's another example with the most current nVidia drivers (version 466.27): Mission: 000c F-14B GraphicsIssue.miz Track: F-14B GraphicsIssue5.trk Log: dcs.zip Capture:

repair of the DCS installation update to nVidia drivers 466.27 deleting the directories "fxo" and "metashaders2" didn't solve the problem.

During a flight of a self made training mission for the F-14B at Persian Gulf sometimes large black boxes are appearing, at least in the cockpit view. The issue is rare. During the last flight (totally ~50 minutes) this bug occured only three times within a time frame of 3 minutes. I didn't have any similar issues so far under DCS 2.7 with my other aircrafts. Demonstraton: DCS OB 2.7.0.5118 nVidia 466.11 Mission: 510a F-14B AA AIM-7.miz Track: F-14B GraphicsIssue2.trk DCS Log: dcs.log-20210430-154000.zip Hardware: see signature This issue is reproduceable for me. Just fly the mission, climb to ~25k ft and follow the waypoints. The bug occurs usually between WP1 and WP2. Edit: replaced the 18 MB track with a much shorter trackfile

Pease use the forum search before you open a new thread relating to a already discussed topic, here are three examples: BTW: DCS 2.6 was never released (2.5.6 -> 2.7)

I'm unable to get a point track in this mission as well - not even under 2 nm. This behaviour is related to an already reported bug for the LITENING II and ATFLIR for the Hornet. I hope, this issue will be fixed soon.