ChillNG

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.

Thanks very much, appreciate the detailed comments and great to hear you enjoyed the campaign!

Thanks very much! Eventually I hope to, but nothing planned yet.

Ha ha fair enough, it is a helo! I stand corrected.

Your controllers disconnecting won't have anything to do with the campaign. Wish I could offer you some advice but no expert in that area, maybe someone else will throw a few ideas out if they read this. Did some data link tests yesterday, think there's a bug in the Viper from what I've read, so might need to wait on a fix from ED for that, but it is will have very little bearing on the mission.

I've had a look at it, everything's set correctly, although I saw the same as you and Bug's DL never appeared. Don't think its a helo you've seen on the DL as it doesn't have DL, and what ever it was for me it was green so not part of your flights network. Think it's a general Viper bug, everything is set up correctly and verified in cockpit through the DL page, so just a case of waiting for an update to fix it. Shouldn't affect the campaign in any way, and if you really want to know where your wingman is, you can use the F10 map.

Yeah it's a case of waiting for the next update, took about 5 seconds to fix, but unfortunately things don't get patched out until the next ED update to DCS. The crash site isn't where the pilot is, he's in the woods to the south.

Thanks for the track, really helpful. Looks like Newts manages to lock himself into some ridiculous self induced fall out the sky, he has quite a tight orbit to maintain so this is probably the cause. Easily fixed .