ChillNG

Campaign updates - OB 18/05/23 Kerman Campiagn M5 - AI Hornets not invisible - fixed. M6 - Added elevation to coordinates given by FAC(A). Persian Freedom M9 - Added failsafe trigger to M9 convoy. Cerberus North M9 - Reduced threat from MANPADS to Tornados

Thanks for the comments, glad you enjoyed it! You're spot on with the implementation of air to air refueling, I've changed the way I've done this for my upcoming viper campaign so it's still optional but far better integrated.

Awesome! Thanks for sharing.

Never a waste, always happy to help.

Also just watched the track, on both stable and OB. The issue was the radio setting, you had it set to 260 but still on preset mode (with preset 1 selected). When I took control and flicked the switch to MAN, the radio started working.

Ok just did a really quick, short test on M12 on stable branch. Got airborne and was asked to set the UHF radio for Gunman, which I did and all worked ok. I used the UHF radio, set for 260 and on manual as well as preset and Ch2. Both triggered the initial comms from Davy. Have you got any other mods installed at all?

Yes that's right, this is the guidance I put out for the campaign: Due to the way the campaign was originally programmed you will always need to observe the following rules: - All Comms listed as VHF AM should be done through the ARC 210 radio. - All Comms listed as UHF should be done through the original UHF radio. Do not use the ARC 210, the mission will not detect UHF frequencies on this radio. - The VHF FM radio is unchanged. I'll download stable and check it over, see what's going on. I'll get back to you soon as possible.

I'll need to do some checking, there were some issues with the new radio, these got resolved pretty quickly in open beta but need to make sure all the fixes made it to stable. And just to check are you still using the UHF radio for wingman Comms? this is the old radio not the new one, wingman Comms won't work on the arc 210 as the Comms are all programed to work with the UHF.

Hi, unfortunately I can't do anything myself about crashes (that's EDs department) but I'll help where I can. First can you check if you have any mods installed, and if you do, try it without please. If that's not the cause we'll flag it with ED so they can take a look at your logs.

No the coords given are the enemy position, however it is fairly close to the friendly position so it can be an easy mistake to make. The enemy position is about 300m to the northeast of the humvees. The green zone, is the name for the area with vegetation in it, so a mix of brown and green - you'll see it outlined in the kneeboard. My suggestion would be to create a waypoint from the coords given, then set a course line from this waypoint of 085 (your attack heading). Fly this course line, when you hit the point where the sand becomes vegetation, you should be in the correct position.. Hope the helps! You can see me demonstrate this on this exact task at around 7 mins in this video (note I deliberately do it wrong to start with):

Awesome, thanks! Love to hear when people make new strategies!

No it is as described. The pipes can be hard to spot though depending on FLIR settings so I put more men on the rooftop to aid spotting.

Cool, thanks for the input, sounds like it had the desired effect - forcing you to re-evaluate and adjust the plan.

This was debated during testing, as the moving cloud update landed just after the mission was built. There is an element of luck depending on how long it takes you to get to this point of the mission and how much the cloud has moved. You can wait it out as well, if the current CAS task allows you to, and it will move on. Final feedback from testers was we should leave as is, it's appropriately difficult for the penultimate campaign mission. But more than happy to look at again if there's a consensus among the community.

Ok thanks, not sure why I can't replicate but I'll add a fix in for the next update anyway.

Hi, no after killing the tanks the convoy will move over the first bridge into the city, then turn left, then right and cross the bridge. After crossing the bridge the next mission event happens. I've just done a short test on the mission to check the ground unit's pathfinding and they proceeded through their route ok, triggering the next phase. Not sure why this didn't happen for you, do you have any mods installed? If so might be worth trying without.

No worries, always happy to help.

Just a thought, hope Reflected doesn't mind me chiming in. I see Quest 2 crashes on Multi threading in campaign missions as well (got pretty much the same setup as you), I've generally stopped my campaign testing on the MT branch as I'm finding it too unstable and really can't afford to waste development time on crashes in testing. MT always starts off with great performance but tanks after a while, leading to a crash. Might be worth trying in normal OB if you haven't.

Hi, just rechecked, all worked ok for me, so not sure what the issue is for you. You still have to press enter on the UFC after selecting the channel to make the option add to F10 menu. Had a check through the triggers to see if I could see any errors that would cause this but to be honest all looks fine. If it keeps happening let me know and I'll see if we can dig deeper.

Hi, tested the above points on both normal OB and MT OB. No issues with the NVGs for me. As a core DCS function these are not anything that will be influenced by a campaign, could it be a mod affecting them? If you've got any mods I'd recommend trying it without them installed, they can affect anything and everything - even if there's no obvious link. No issues for me either with Al Minhad, you wrote 127.5 above for the frequency...not sure if this is just a typo or what you've been using but the frequency for Al Minhad is 125.7. Just tested on 125.7 and all work as should. Hope that helps.

Great to hear, glad you enjoyed!

Yeah it's any missile launch, can be a real pain if there's a big ground battle going.

Triggers are set to only the specific missiles called out so that shouldn't happen, but I'll double check in case something's changed. But the A-10's MWS is triggered by any missile launch, including AT missiles...wondering if that's caused the confusion?

You're right they were missing. Corrected for next patch, thanks for flagging up! If anyone needs in the meantime - first elevation (given by Chieftain) is 5423 feet MSL. Second (from Wolf) is 5618 feet MSL (note not all players will see this set of coordinates).