Gilligan

The circle flashing is the DTOS que, not the CCRP release que. Wait for the Circle to flash and then go away, your time to release will reset to somewhere between 0:08 an 0:06. Hold WEP RELEASE at this point, a second crossbar will drop down the CCRP line and the LGBs will drop once the timer hits 0:00.

Swap one of your Mav's for a HARM. Set it to POS mode on STPT 9 and send it when you get as close as you are comfortable. I've had pretty consistent success sending it a little bit past the ridgeline once the SA10 starts firing and then going defensive. If you do it this way have your flight hold at STPT 8 and then attack once the SA10 is offline. I use either a spare HARM or MAV to take out the SA15 to the North. I've also had success going North for a bit along the ridgeline after STPT 8 to get a little closer. Just watch the HQ7 and you'll be fine. I set my flight to trail if I go this route and tell them to attack once I send the HARM. Again taking some spare ordinance for the Tor. Sometimes I hit the HQ7 as well on the way out. Going in with MAV's only is full on suicide, and waiting for Springfield flight to suppress with HARMs is unreliable as they get shot down about 50% of the time on the way in.

I think this is largely down to the RNG on if a Heater is going to bite off on a flare or not. I tried 4 different times, once going high and pulling into the missile (dead), going low and pulling into the missile (Dead), going Low and pulling away from the missile (Lived), and going High and Pulling Away form the missile (Lived). All entries were done at or just under mach 1, off burner, and pre-flaring around 5k ASL. The two times I died the missile did not care about the flares and tracked right at me through the defensive maneuver. The two times I survived the Missile went after a flare as I was initiating the defensive maneuver and were not defeated kinematically. So unfortunately it's not a skill based encounter. At least it seems to be entirely up the the RNG of whether the missile will go for a flare or not.

I've been replaying this campaign and all JTAC functionality has been restored. I think there might have been a DCS problem that has since been resolved.

Yeah no sweat. I believe this is an issue with DCS itself, and SPI problems with MAVs is on their short list for known issues being addressed in an upcoming patch, so hopefully that gets things back on track. I've just been setting the mavs to PRE before starting INS and then waiting to boresight them until we are over the mission area and that seems to be working, plus the added benefit of reduced parallax in the boresight alignment.

I have also noticed something similar: For example, there were a couple of instances where I "Fenced in" when I heard the flight lead direct me to in coms, and since I have most of my Fence-In commands bound (or turned on during start up), I am able to do so pretty quickly before the red box with "instructions" is able to show on screen. If I have completed my fence in prior to the red box materializing I will get the Radio Dialogue "Fenced" however the red box will remain until a new "instruction" is shown, and the F10 menu will be stuck with the "Fence In" option with no others showing for the duration of the mission. The couple of times I experienced this is wasn't mission breaking so I didn't report it.

Tried it again today. Same thing. Here's a track file of Tally not Engaging. https://www.dropbox.com/scl/fi/gjnsfgwcghjjqnak0sfy3/M12Tallyfailuretoengage.trk?rlkey=0dcbvqohej5dcvvlsairtt7md&st=wjevbzx6&dl=0 UPDATE: Got it to work if I let Tally Shoot first at the southern technical. I had to hold my Mav until she rifled hers off, then shoot. If I shot first she would not engage. Tried it twice letting her shoot first it worked both times.

I’m also getting this bug. I engaged the rooftop AAA at start and killed it. Killed the northern technical by the mosque. Talley never engaged the southern technical. Just kept flying her racetrack pattern west of the city. no mods.

I also got minus 20 on this one for missing one of the SA6 radars, however I only ever saw two active launchers on both the TPOD and HAD screen. Reviewing the TACVIEW I see all three sets of launchers, but only two of them launch anything, the Northern most and Southern Most, the Middle one remains inactive. Likewise I only see two SA6 Radars, again at the northern and southern sites. There seems to be one missing at the middle site? (Images attached) As specified in the Fighter-to-Fighter I engaged the Southern site and Flash launched on the northern site. My HARM hit the Radar at the southern site, however the northern site goes inactive while Flash's harm is still airborne and it re-directs at the southern site. Wasn't a problem ultimately but seemed strange. I did get engaged during the "uneventful" exfil by an SA11 after following the more northerly 342 heading recommended by Overlord(?). I bonked the snow drift radar with my 2nd harm (CHAOS still calls out "MAGNUM SA6"). Found this fairly humerous.

I think I figured this one out after messing with it some. If the Mavs are set to VIS mode the SPI gets stuck near H4 for me. I suspect it has something to do with that being where I did the Boresight procedure, however I'm certain that I unlocked everything before proceeding. Ensuring your agm65's are set to pre should fix the issue. I don't know if that is working as intended or a bug within DCS.

On mission 6 I think Ghost's laser failed on me or maybe something else, but I missed by first GBU12 drop and I'm not sure why. Profile seemed good, had the correct 1665 laser code. Circled back around and lit up the car with my own laser and hit it a couple meters off but still got the shack. File to large to attach but here's a dropbox link: https://www.dropbox.com/scl/fi/hacvu8znt3qfkm39dsht5/GamblersFailedJTAClaze.trk?rlkey=k11yidtws2xcsfpdkvs1ca222&st=c4lcasth&dl=0

Appreciate your diligence. I was able to get passed this last night - I took two CBU-103's and dumped both over the mortar site. Both CBU's hit the target area and the second CBU killed both trucks after the first damaged them. This seems to have worked to ensure that the trucks were dead before the wingman BDA, and the mission progressed.

any headway on this? I am also experiencing this mission stall.

As the title says - I've never experienced this before, but no matter which STPT I have active the TPOD defaults to H4. If I slew around hitting CZ will send the TPOD focus back to H4. Curious if I am doing something wrong? Only thing I'm doing different during start up here is setting the laser to the code specified in the knee board (1686) vs using the standard 1688. Any help would be great.

It helped, but not significantly. Was able to ingress and hit the target, however it was running down into single digit frames by the time of the mission's "surprise." Unfortunately I'll be shelving the campaign until something changes. Which is a shame because I was really enjoying it.

Oh man that’s a bummer. Unfortunate because otherwise the campaign really is great. Okay, I do have tac view running so I’ll try that then. Thanks for the response.

Really enjoying the campaign, but I'm getting some really bad frame rate issues that are starting to make the missions unplayable. Particularly missions 8, 9.1, 9.2, and now 11 I'm getting frame rates in the single digits. Other missions tend to run in the 45-50 range, occasionally dropping to around 30, which is fine. But I can't really dodge SA11's over Damascus at low level with 7fps. I don't have any issues in any of the instant action missions, regular single missions, or multiplayer. All of that runs in the 90-140 FPS range. The Red Flag campaign I was in the 45-90 range on frames. I've tried turning down the textures and load distances however that doesn't seem to have any effect. Is there something going on that I am missing? EDIT: For reference I'm using an i7-9700, 32gb RAM, x64 Win10, RTX 2070 Super. Game is installed on an M.2 2TB SSD. CPU load during missions is about 55%, RAM at 65%, and GPU load is low at 10-15%. This is where I think the issue is, as in other single player missions and MP my CPU and RAM load is closer to 80-90%, and GPU is maxing out at 100%. So it's almost like something is stopping the campaign from using all the horse power available to it. Definitely seems weird. Thanks.

Just did this mission and had the same issue. No whiplash on channel 20.

Interesting - Okay I'll do some more testing with it. IIRC most of the issues I've been having correlate with a hangar start and that makes sense. Thanks for the tip.

Just went back up. Data Link was working, but not as intended GPS SYSTEM did not show, Turned MIDS on, Had to cycle GPS TIME on in the DED TIME page, Data Link came on. Respawned and it was completely broken. No GPS TIME, No Data Link Tracks if I turned MIDS on. Cycling the GPS TIME in the TIME DED page had no effect. I'd Attach the Track but it's 54 MB. 51 MB Compressed. I'd be happy to upload/Send it some other way. EDIT: Here put it in a drop box: https://www.dropbox.com/scl/fi/r2r2t4alojb3bm34p9asr/Through_The_Inferno_SYRIA_v4.0.6-20240601-201735.trk?rlkey=u7x68nh40guq8cyuqvlu899tb&st=nwgqa2qq&dl=0

Here's a Track where everything worked as intended for comparison. Through_The_Inferno_SYRIA_v4.0.6-20240601-194642.trk

Did another attempt just now. GPS SYSTEM did not come on in the TIME page on the DED, and the DLINK page would not open in the DED HOWEVER, I turned MIDS on without the GPS SYSTEM updating in the time page and the MSD did show Data Link tracks, and I could then open the DLINK DED page and cycle the GPS TIME on/off. None of this got the GPS SYSTEM text to update in the TIME DED page. TRK attached. Through_The_Inferno_SYRIA_v4.0.6-20240601-170755.trk

Can confirm F16 DataLink is still broken. Sometimes it works for a while but eventually the "GPS SYSTEM" will not update in the TIME page on the DED. Sometimes this doesn't matter, and Turning the MIDS to ON will still get the Datalink up and running, but sometimes not. It's very inconsistent. Hitting Enter Does nothing. The DLINK page on the DED is completely broken and will not open. I will try and get a track file the next time this happens. Added a TRK file from just a moment ago where GPS SYSTEM would not come on and the DLINK page in the DED would not open. Through_The_Inferno_SYRIA_v4.0.6-20240601-163923.trk

Was there ever a resolution to this issue? I'm experiencing it now with a severe movement downward on the Y axis of the throttle joystick.

how do you push down the handle?