SignorMagnifico

I can attest to this happening to me as well in the current DCS version. (DCS 2.9.20.15384) I tried this mission out today and could not complete it because the Tu-22 does not fire the Kh-22 missile as expected. In the F-86 version of the mission, the missile launch happens just fine. The only difference I spotted was that the Tu-22 has the UNCONTROLLED flag enabled in the MiG-15 version of the mission whereas the the flag is not enabled in the F-86 version. I have attached a track file of the mission and linked a YouTube video of the bug happening below. Track File (too large to upload) https://www.dropbox.com/scl/fi/6891qml6p7cj1hzg8m9mu/relicmig3kh22launchbug.rar?rlkey=ep85u1fpdtg9rz671runsys9z&st=05mydksy&dl=0

The kneeboard page referencing waypoints and speeds (headings & airspeed) in Mission 10 of the Museum Relic Campaign is incorrect. The kneeboard displays all speeds in km/h instead of knots. The chart in the mission briefing window is correct; however, the page in the kneeboard is not correct and does not match the briefing window. Within the mission file, filename Waypoint Grid 512.png in the l10n > DEFAULT folder should replace the KB F86 MR10c.png file in the KNEEBOARD > IMAGES folder. Tested on DCS 2.9.20.15384. As a temporary workaround, it should be sufficient for the user to move the Waypoint Grid 512.png file into the users > saved games > DCS > Kneeboard > F-86F Sabre folder.

The kneeboard images are not visible in Mission 7 because the images are placed directly in the mission's KNEEBOARD folder instead of the KNEEBOARD > IMAGES subfolder. I resolved this by extracting the images from the mission file and placing them in my C:\ > users > username > Saved Games > DCS > Kneeboard > F86F Sabre folder, so I could fly the mission.

Update: I managed to complete the mission and stop the AI collisions. What worked for me was changing the flightplans of SARAH and LIONCUB to instruct them to follow DOG flight at a distance of 2500m and 1000m, respectively. I also set SARAH to follow DOG flight at the same altitude, but LIONCUB follows at 200ft above DOG flight. Turning off wake turbulence made no difference in the outcome. I also made the coastline and target waypoints VIP points.

Has anyone else encountered this issue with mission 5 in the Frog-7 campaign? (Strike on Damascus International) Both times that I have tried to complete Mission 5 of this campaign, SARAH 1 crashes due to a midair collision with another one of the AI flights. In this last try, LIONCUB 3 crashed into both SARAH 1 and SARAH 2, causing this message to appear: "SARAH 1 has been lost in action. Abort and change to waypoint 15 for RTB instructions." I'm wondering if it could be due to the AI not being able to handle being in such close formation or something else. Screenshot of the mission result and a .rar file with the track file attached. I'm going to try turning off wake turbulence in my game settings and instructing the AI flights to go into a "trail" formation during the low altitude section to see if that helps. Here is a video of the collision on YouTube. (Latest attempt done in DCS 2.9.19.13478.) Side Note: For QOL update, I think the coastal waypoint should be set to a VIP point over the bridge, so Jester can get a nav fix. frog7m5.rar

Thanks for letting me know! I hope the LUA file for the MiG-15 gets fixed soon.

If the AI MiG-15 does not have a supernatural climbing ability, then how is it able to outclimb an F-15? Or was this reported bug already fixed? Maybe I missed the patch note.

Thanks, Flappie! There seems to be some link between the module and the engine smoke effect combined with the motion blur. @HR-CrumbleI have an Nvidia RTX 5080.

I can confirm I'm also experiencing this black texture flickering issue on objects when motion blur is turned on in the latest DCS version 2.9.18.12722. This has been persistent across multiple patches, and I agree with @HR-Crumble that the issue occurs most commonly with "smoke logic/effects of varying types: fog, dust storm, missile smoke, engine smoke (F4, Migs, older jets etc), catapult steam, vehicle dust trails." Attaching a track file, screenshots, my graphics settings, dxdiag, and a YouTube video of the issue happening in hopes the dev team can replicate this and fix it. Turning off motion blur stops the flickering, but that's a band-aid. @Flappie Are you able to replicate this? DxDiag.txt textureflickering.trk

I noticed this bug in the Hunters Over the Yalu Campaign Mission 11. The Mig-15 AI is set to ace level and randomly crashes itself into the ground at the beginning of the mission when the player flight is taking off. The chance of the AI crashing itself is random as reflying the mission does not always result in the AI crashing. It seems to happen roughly 20 - 30% of the time. Track file and YouTube video of the bug attached. Recorded on DCS 2.9.17.12034. caseyjonesdead.rar

Thank you for the response and for checking with the team!

Thank you for looking into it!

I guess this is correct as is? No control loss seems to be happening during high speed dives.

This is absolutely a must-have to make the core sim better. It's quite a pain having to fast forward through a mission multiple times to capture more than one angle of the same scene. The replay system should also work just like a "replay" and accurately portray what happened. The AI doesn't make the same choices during the replay that it does in the original scene, so it's impossible to use the track file to capture cool angles of air to air or air to ground kills. Not all of us have an army of cameramen ready to record the scenes live on a moment's notice, either. Fantastic work on this! It must have taken many, many, many attempts to get it right.

In the current DCS version 2.9.16.10523 I noticed that I'm able to dive the Sabre at full throttle from 30,000ft, exceeding Mach 1.1, and I can recover from the dive without the use of air brakes. I haven't flown the Sabre in a while, but I recall that normally during steep dives, I had to deploy the airbrakes to ensure I could pull out of the dive. Additionally, there seems to be weird vibrations going on at the wing tips once it exceeds Mach 1.0. Track file attached. F86MachTest.rar