ChillNG

Ok cool, thanks for the update. One to keep an eye on in case it crops up again.

Just one of them DCS things I guess! Glad you enjoyed

Ok thanks, for each of the Golf targets there will be an audio confirmation of the target being killed, if you don't hear this from Steep then the target kill has not been detected.

I'd have to look at a track to know any more. There's two Golf targets, you get them both? There's a lot of fail-safes mechanisms built into the targets themselves so its unlikely that if you hit them they didn't trigger the kill, but if you're sure I can look at doing some further testing.

Sounds like you didn't complete or exit the secondary task, if the F10 menu was still showing 'Abort target Golf' then completion of the secondary task was not triggered, as achieving this will remove it.

That does sound frustrating, apologies. You have to wait for them to reach the truck location, should take about 8-9 minutes so sounds like they got lost on the way. This is the first report I've heard of this but it's possible a path finding bug has crept in so they're not reaching it. I'll put a fail-safe fix in to safeguard against it in future. EDIT: I just ran a quick test and path-finding was ok, but it is possible if they are taking fire (depending on how you do in protecting them) that they took a detour. Also note the radio needs to remain set to Forge's freq.

No, restarting the mission shouldn't have any effect as far as I know, nothing should change (at least I would hope not!). For takeoff clearance option to be added the conditions are 'request taxi+10sec' AND be in one of the takeoff zones shown below. Hope that helps!

Hmm that's interesting then, maybe you turned off a switch by accident or something, I've done that before with fuel pumps and the like.

Nope not planned in by me. Do you have random failures enabled in your options?

Thanks glad you're enjoying, IIRC you only get cleared to shoot if they Migs get close enough to you so you can see the markings or if they fire on you.

So when it comes to changing load-outs I always say do it at your own risk, as it's been 3+ years since the missions were built and I struggle to remember every detail of how I built them...but that said on both Missions 9 and 110 I can't see any triggers relating to the Rockeyes so as far as I can see all should be ok if you change them. Personally I don't think the Mk-20s are all that bad in my testing, just got to set the MFUZ correctly in the cockpit. By default the PRI setting will open the canister 1.2 sec after release, so should be used at low altitudes. OPT will open after 4 sec so is better used at higher altitudes.

Excellent, thanks for the update. It is a tricky one that one, let me know if you need any pointers.

I believe they are all over it, they seem to have figured out what's causing it so I'm optimistic.

Did some digging and did find an old script, whose purpose was now replaced by new mission editor functionality, doesn't relate to the ammo truck but have removed it anyway as a possible offender.

Hmm strange one, just ran some tests and couldn't reproduce. Truck spawned ok and went about it's business until it blew itself up with no errors. I'll ask around about the error message, see if anyone has any ideas.

There's a known performance issue with DCS overall at the moment, especially on heavier missions. ED are aware and fixing. If you use Tacview then disabling it can help as we've found it has quite a big impact.

We always advise removing all mods completely then running a DCS repair, unfortunately they just have so many unforeseen side effects in campaigns.

I've seen reports of an intermittent DL bug on the Viper, you might be seeing that. They don't always come up on DL straight away either, but will appear once the mission is a little more underway, still a mystery why but I see it quite often.

That doesn't work anymore in the F-16, was updated a while back. Leave the DL and MIDS switches off until your INS is aligned and set to Nav, then turn them on and all should work ok.

At what point in the startup process are you turning on your data link?

Just done some checks all was ok my end. Mission 12, targets were right where they should be... Mission 13 part 2 started as it should and nothing strange happened. Very unlikely there's an issue with the triggers as they haven't been updated so will keep working as they always have. Would think it's something on your end causing a conflict, most likely culprit is a mod, do you have mods installed?

Just tested didn't have any issues with the radio working on 30.4, no beep for me and comms played as intended on pressing space-bar. I'd have guessed at an issue with your radio settings but to be fair they look ok on your video. If you can link/send a track I'll play it back and see if I get the same issue or ID what the problem is. I've tried to get the tone to play on a new mission when the radio is set the 30.4/manual but all worked fine there as well. Whiplash static is an ED thing, they added extra static into comms based on distance, easy fix, I'll update the mission.

No, data link has no bearing on the HAD, not a factor. If you look at the top of the HAD display where is says PGM2 you'll see some other numbers, these are the north/south and east/west values for the HADs estimated accuracy. If it says 10 and 1 for example then the estimated position is accurate to 10 miles north/south and 1 mile east/west (or something like that, I might have the values the wrong way round).

Ok thanks, I'll do some tests later

Any mods installed? First report I've had but can check ASAP.