dorianR666

+1 but this belongs in the bug section.

im having this SAME exact issue when seeing civilian traffic at best LOD on the channel map. definitely dcs bug. amd rx 580

this has nothing to do with clouds its the broken milkyway skybox they added with 2.5.6 (or was it 2.5.5?) you can remove it from the game by deleting that texture file btw

dcs core bug, happens with other modules missions too. some say it happens when certain kinds of objects are destroyed. you can simply modify the logbook file to progress in the campaign, or open the fifth mission from editor and play from there (its the last mission of this campaign).

Hm, that is weird.

CA really needs some love from ED.

Its because they are being loaded from disk into memory. Generally there is one base texture and then "spots" of different textures on top of it. You can see it in the video at the end, most of the screen is this "spot" but in top left the base remained in view unobscured by the spot. Probably not much ED can do about it without increasing memory usage.

i believe flat shadows are still used with default setting for distant objects

This affects all planes with external CM pods. AI units in DCS cannot use the pods, so they are given certain amount of CM "internally" and the pods are just cosmetic for them.

too much danger will make them RTB you can prevent this with the Reaction to threat waypoint action, by default its Allow abort mission. Pick the one next to it.

i see this too.

this happens to me too.

repairing viggen still doesnt work just today, on latest OB, on hoggit server: landed at friendly airport, engine shutdown, parking brake on, canopy open, batery off. ground crew says "copy" but no timer appears and no repair happens

just so this isnt forgotten: doesnt work in 2.7 either

send the .miz file

Hm, now that i think about it, you might be right and the "held in" may mean magnetically held perhaps? It would make much more sense. I suppose this should be added to the manual. Still, the manual section for P4 is self-contradicting. One of those two sentences must go. Found a PDF made by someone here on forums allegedly based on IRL Viggen documentation claiming the P4 program should be started by streak selector being moved to 4. https://forums.eagle.ru/applications/core/interface/file/attachment.php?id=73239 A kneeboard set made by another forum user claims the same: https://forums.eagle.ru/uploads/monthly_2017_04/Viggen-ff19-Countermeasures.png.8b6452d565be1601693ea1f7e53e09c5.png Perhaps the behaviour changed at some point.

Amazing work!

This seems to be a DCS binding functionality. There is no mention in the manual of a difference between Kont and Int, no mention of Int returning after 6 seconds etc. as far as I know. The manual says "held in INT or KONT" multiple times, so that sounds like pilot has to hold it there IRL. The manual also says: When the streak selector is set to mode 4, the pods begin to dispense chaff slowly (1/5th the speed of program 1). Which doesnt happen and is in direct contradiction with a sentence right below it: Release switch is either held in INT (intervals) or KONT. The manual also says: The left pod will empty before the right pod begins to dispense chaff. Which again isnt true in game, both pods dispense simultaneously. It seems P4 is broken all around.

Hello Heatblur The program 4 is supposed to release chaff at very low frequency, depleting one pod after 8 minutes of use and two pods after 16 minutes. The program is to be initiated by the action of moving the streak mode selector to position 4. This is bugged, currently the program is only running when, in addition to the previous, holding the dispense switch in Kont or Int like all the other programs - that shouldnt be a requirement for P4. This means the pilot would have to non-stop hold the switch in Kont or Int for several minutes when performing its intended use, which would make this program completely unusable. Pls fix.

not new with 2.7, i have it on video from over a year ago and 9:35 on the left it appeared since ED added the city night light "glow" effect at distance. edit: fixed link

im experiencing the same issue whenever cars of civilian traffic at nearest LOD on the channel map come into view. once i look away, or the car drives away so its LOD decreases, the black screen goes away. usually the whole screen is black, but rarely only horizontally part is, as if a large black rectangle is over the screen. amd rx 580

correct, it happened to me in singleplayer in a mission i made. i couldnt replicate it though.

there is an old bug which results in ka-50 ai being unable to fire the guided missiles. does it happen for you if you remove the guided missiles from the ai ?

i have seen it with litening too long time ago. but now that i think about it, its been some time since it happened to me. perhaps they reintroduced the same bug with atflir, that would be funny.

i have seen this too. its a very old bug, definitely not since 2.7. i have no idea what causes it.