RLTick

Want to report I'm seeing a similar issue. None of the AI flights never show up on data link for me and I'm following my normal start-up procedure that works in other missions. The GPS on off trick from the video didn't work (tried 4 times). In other missions I don't have this issue and don't need to use the gps on/off trick so it seems specific to at least this mission so far. Thank you

FYI, I tried this mission again and the exact same things happened, so whatever is causing this likely isn't random.

Hello, No mods and the default difficulty, which is Veteran if I recall. Thanks

Hello, I just attempted mission 12 but Uzi flight ended up flying in a circle centered roughly between waypoints 2 and 3. After 15min of them circling I gave up and quit the mission. Track file attached. If flying my flying higher than fragged broke a trigger please let me know so I can replay. Thank you Tacview-20241109-090541-DCS-SYRIA M12 FRIENDS UNITED.zip.acmi

Hello, I'm getting a weird error where I can't enter a waypoint offset of more than 66NM. If I try to enter a larger value it flashes error. If I enter a larger numerical value into smaller units (e.g., 100 meters). I can then enter same same value into NM which will still flash error. but will move the offset to 100 NM. See attached track. Thank you offset range.trk

Adding in that I'm also experiencing this. Had to roll back to an old version to get rid of them

Hello, Looking back at the track I didn't wait for 2 to join (he gets within 1 mile but never forms up), so that's probably where I broke something. I never got any radio/message to press space, no message about climbing, however I did hear the calls for Dodge's engagement. When I left the AO I got a short chit-chat. No radio calls till I was at the tanker, and when I got the split-up message during RTB, matrix stayed with me instead of flying off. On the newest patch, normal version, 64 Gb ram, 4080 Super, no mods

Third try was the charm, not sure if the 45deg is needed but both hit. However, I think I messed up a trigger somehow as Matrix didn't bomb the runway and no migs attacked me. Still got a mission success after RTB. Either way it was fun and I'm looking forward to the next mission. Tacview attacked as track file was too large Tacview-20240810-172310-DCS-ROPL2 M9 PART 2 RUMBLE WITH A GRUMBLE.zip.acmi

I'm also running into issues with bombs falling short. I tried this mission twice today. Both times i waited a few seconds after getting in zone before pickling. It was a different one that fell short each time. I'll try again later today/tomorrow with the 45deg terminal angle and see if that helps. Of note; tacview shows target 1 at E54 46 25.38 while the mission gives E54 46 25.31. This is a very small offset and the bombs are falling much further short than that Tacview-20240810-132804-DCS-ROPL2 M9 PART 2 RUMBLE WITH A GRUMBLE.zip.acmi Tacview-20240810-134852-DCS-ROPL2 M9 PART 2 RUMBLE WITH A GRUMBLE.zip.acmi

I'm getting this as well. I waited about 4 min after finishing my AAR with nothing happening, I tried flying away but smoke kept with the tanker

Tried again today, circled mother right after take off to make sure smoke was in the air before I hit waypoint 1. Got the radio calls at waypoints 1 and 2, but smoke was still circling mother at 2k ft. R1 M2 smoke still bugged.trk

I think I ran into this issue today as well. Passed waypoint one and approached two with no radio calls. F10 map showed smoke going off in a random direction. R1 M2 smoke issue.trk

I'm also getting the same issue on mission 8 and 9

Hello, I'm running into an issue where on the second (and subsequent) firings of AGM-65Fs the "MAVF" indication on the hud stays crossed out even if the mav is locked and tracking on its DDI. In the attached track file I make 4 passes against simple moving targets (along runways on the Syria map). For all 4 passes i start with a point track using the LITENING on the right hand DDI and then switch to the MAV seeker on the left DDI. If it doesn't lock I try a combination of cag/uncage and switching back to the TGP on the right DDI to move the seeker. On the first pass everything works as I'm expecting. On the second pass it locks briefly before loosing lock, but even during that short time the MAVF stays crossed off. On the third and fourth passes the seeker stays locked for longer with the reticle all the way into the center and following the target. In all cases I fire even with the MAVF crossed out and hit the target. Am I doing something wrong or is this a bug? Any advice on this would be appreciated. Thanks AGM65 lock test.trk

Hello, I defeated all hostile aircraft in mission 7 leaving only the mig 29s, which appeared invulnerable to damage. The mission objectives said there were still hostile aircraft but none spawned. Eventually aegis 1 and 2 formed up on me while aegis 4 landed at a nearby airfield. I ended up having to skip the mission as I didn't want to re-do it. Has anyone else ever encountered such an issue? Thank you

Did some further testing and found its dependent on visibility range and not preload radius. I have it set to Ultra and at that setting the camera kicks in at 38 miles. Thanks for the help

I was in active pause for the uploaded track, however, I get the same result regardless of whether or not I'm in active pause. I haven't had any issue with the video kicking in.

Hello, I'm running into an issue where the datalink image for the slam/slam-er is just a green blur with no detail (see attached image). I've followed both chuck's and several video tutorials so I don't think I'm missing any steps. I've verified that the data-link pod is set to the correct channel, cockpit displays are set to 1024, and I'm not using any shaders. Channing track blk/wht doesn't change anything, changing the mdf contrast doesn't either. This happens regardless of distance to the missile and when the plane is pointed directly at the target point. Any advice/help would be appreciated. Thanks SLAM-ER test.trk