ChillNG

Probably not a campaign issue, nothing I've set in the editor should interfere with this, but I saw in the change log some changes to CCIP and CCRP, so it's possible the methodology has changed slightly.

Thanks for the feedback!

Ok thanks, glad you're sorted.

Thanks very much!

Thanks very much, glad you're enjoying! Overhead break is fine, but you need to avoid overflying Ruwaished at less than 7500 (IIRC) feet as per noise abatement procedure. Violating that will cost score.

No that shouldn't make a difference, it's probably the issue above still rearing it's head but I'll do some more checks and see what I can see.

Thanks, yeah I've noticed the battery instruction has caught a few out already. I've changed the wording for the next update.

Not the way I like to do things. My system allows me a lot more fidelity over how the attack is controlled and the conditions for approving the attack, adds another level of immersion to the gameplay. Plus I hate having the default comms voice from the default JTAC playing when the player/JTAC are taking in different voices.

As it's all custom built and you can't link into the aircraft's CAS page via the mission editor.

No probs, happy flying!

Hi, not it's not a Bug, there's a few common mistakes people make so please see this thread for descriptions of what they are: Also worth saying that most of the time not following instructions/ATC won't break the mission, you will get told off but the campaign is designed to allow you to ignore things/mess up and it will carry on working. You might get some grief from your superiors though! If you need any more help please let me know.

Most likely put the coordinates in wrong, I do it all the time!

No it's still working ok...you're just using the F5 ATC menu option, you should be using the F10 option. For anyone with radio problems please see this thread for guidance.

Ha ha thanks, glad you got it sorted!

New products always land on beta first, stable follows later. I think the store page might not be clear, it says v2.8.8, but at the bottom it also says you need to be on OB.

Have you updated to 2.9?

I suspect you might need to update, judging from the unknown module message on the log. I saw the same prior to the update when the campaign was available for download in the testing branch but not yet released. If there's a reason you're not updating I'd suggest raising a support ticket with ED to see if they can rectify it.

Good to hear, enjoy!

Thanks, much appreciated Make sure you're on open beta, and if so it might be the localisation issue above. I'd advise opening a support ticket if so.

My pleasure, hope you enjoy the campaign! No the new data link settings aren't in at launch, but I have updated them all today so they should be in the next patch. Until then the data link network will work just like before the update so there won't be any issues. TDOA however will need some testing before I implement it, my main concern is how the TDOA request affects the AI when it is sent to them. If their assigned task is disrupted will they go back to the original task without any issues, and will it affect the timing of their tasks, which can be important. But with all that said, as TDOA wasn't in DCS when the campaign was built there aren't actually all that many opportunities to use it, due to flight sizes and assigned roles. So I'll see where testing goes and take if from there.

The first mission of all my campaigns are available as demo through my discord server, so if you want to give First In - Weasels Over Syria a try before you buy then please come join us. https://discord.gg/F6x7G4buJk

Ok no worries, if the problem persists then raise a support ticket.

Well the Comms settings are always the biggest thing people struggle with so hopefully you've shone a light on it for anyone else having issues.

From what Bignewy says above, sounds like a bug in the shop and sounds like they are fixing it. I had a user on my discord with a similar issue this morning, they opened a support ticket and it got fixed within the hour.

Thanks for the track, that helped me spot what you were doing wrong, you set the pre set incorrectly. The option you selected I think was determining what the presets are set to, to set the radio to that preset, just dobber over to the value on the right, type the channel number and press UFC ENTER. Once I did that and pressed spacebar, all worked as it should. null