Ithronwise

I confirm, it is still there, less strong than before in my opinion but it still exists.

I still see this black flashing whether the mirrors are on or off, but in my case only at night.

I am interested, too.

Hello fellows, yesterday I had a strange and probably rare bug. I flew a mission over Syria to destroy two warehouses of the IS with GBU-10's. Because of the cloud layers and an SA-6 SAM site nearby I flew below 10,000 ft AGL. On the second run over the target area I was hit by an SA-18 Grail. But I did hear no explosion, I saw no plume. Actually I saw the missile missing my tail and going straight into the sky. The flight behavior of the F-16 was normal, no warning lights, no fuel or hydraulic leaking. I realised the heavy damage just after switching to the external view. But something was strange. The SA-6 stopped tracking me right after this "ghost" hit. I couldn't radio the AWACs, nor the tanker or my homebase and on the F10 map the F-16 was gone (see video below). Nevertheless all was fine until I dropped the landing gear on final approach to Akrotiri. In this moment the plane went into a deep unrecoverable dive and I had to eject. In the debriefing I saw the only damaged system was the AN/ALE-47. In this mission I had activated some mods, but only one that affected the F-16 (CFT Mod 2.0.2 by Nightwolf). This is not a serious bug and I think it is very rare, but I have seen some other reports similar to this in the WWII subforums. I have no track file because they are completely useless for longer missions, especially with A/A refueling (in not a single replay of such tracks I saved, the plane was able to connect to the tanker). Attached you can find the dcs.log and the debriefing.log. dcs.log debrief.log

Hello everyone, not sure whether this is already known but I found a small graphics glitch in the upper right corner of the upfront panel (black flickering square): Best Regards, Rene

That may be, but I think you'll agree that if this problem occurs in 2.7 and not 2.5.6, something has changed between those two versions and is causing this issue. When I experienced this problem, nothing had changed on my system, and when I went back to 2.5.6 a day later, my system was still unchanged. Perhaps it is a side effect of another change in the 2.7 source code.

Sorry, but I highly doubt that. The problem occurred after upgrading to 2.7 and was gone after I downgraded back to 2.5.6 because of it. So the only thing that had changed was DCS.

This issue doesn't matter to me anymore since I bought a larger monitor with native WQHD resolution and higher pixel density. But apart from that, in version 2.5.6 the super resolution worked very well. Why is it problematic now in version 2.7? Your explanation is not really convincing, because other game manufacturers don't see it as a problem.

I have investigated this bug a little bit and it seems it is related to the wind settings combined with lighting at night (at least in my case). But only the Marianas map is affected. I created test missions with the same settings on Caucasus, Persian Gulf, Syria and Marianas: - LHA-1 Tarawa, 25 knots, course approx. 225 - 1 AV-8B for the Player - 3 AV-8B uncontrolled aboard - Time is 21:00, Date is 12th July 2002 - Cloud setting is High scattered 1 - Wind is 4 knots, 65° With wind settings the black flickering appears, without it is gone. Only on the Marianas map I could reproduce this. Here is a video to demonstrate it.

I experience this issue only since version 2.7.5 or 2.7.6. I never saw it in the versions before.

Looks like the same issue I am having:

Giant tree on Tinian island near North Field:

I have experienced a similar black flickering which only happens at night probably caused by lights. In daylight I cannot reproduce this bug. Here is a video: Here is a second video captured from the same track but in daylight: Here is the trackfile: Black Flickering Bug at Night Track Marianas.trk My CPU, RAM and GPU aren't overclocked nor undervolted. My windows drivers are up to date. My graphics driver is the second last WHQL driver recommended by AMD (the newest WHQL driver has only optimizations for some new games, no bug fixing in the release notes). Best regards Rene

I tested the track file on my system, result: SSAO = On: black flickering spots along the bridge SSAO = Off: no black flickering spots along the bridge (and also nowhere else)