baltic_dragon

@pbt31 @B.B.Blender my apologies, when fixing all the missions broken by the update of the Syria map I left one tiny unit too close to the runway in M01, which led to this situation. This is now internally fixed and I hope the campaign-specific patch will be out within a week or so, then all the missions should be working like a charm again. I am really sorry about this situation.

Thanks! Stealing this post for my FB

@DarkTempest I'll be adding the kneeboards as PDF files to the docs folder with the next update (there should be a campaign-specific one shortly)

You'd be amazed how much I learn when I am creating these missions enjoy them and let me know if something is not working or needs to be improved.

Thank you very much. Noted down for fixing today. Enjoy the rest!

@VirusAM IIRC there was some issue with guard if it is selected on both radios... not sure now, but it is safer to only enable it on one. I will run some tests today and if I can confirm this on vanilla, will report it. We did check the mission after release and two of the beta testers had no trouble hearing Chainsaw, so I suspect some user error here.

Hey guys, sorry for not replying earlier - I was AFK over the weekend. I had this report just before launch from one other fellow campaign dev and he had the same issue. We tested it with 3 different beta testers and none of us could reproduce this problem. The triggers are all set as they should be, frequencies are OK - there is nothing I can do on my end to fix this one unless I have more information about it. What sometimes helps in situations like this: 0) Obviously check that you are on correct radio channels 1) Make sure that EASY COMMS are set to OFF (that one is crucial) 2) Check that you don't have any unofficial 3rd party mods installed / enabled 3) Apps like VAICOM / VOICE ATTACK also tend to mess up the mission logic for some people, try to disable those 4) If nothing helps, run a repair. @rob10 I'll have a look at your track a bit later today and see what is happening (or what is not happening there). I'll get back to you guys with more info as soon as I can.

I didn't attach the printable kneeboards to the campaign @Critter. Good point though, I will update the attached documents and add them there. Thanks! Waiting for a dedicated forum thread for Arctic Thunder.

Hm, this is weird - the waypoints are there in the mission editor. Anyone else experienced this? I will check on my end, but just to be safe maybe try to run a repair?

It is an interesting idea, I'll see what I can do. I wish I had a model of a downed pilot and a downed pilot in the water...

It fixed everything except from M01, which was our mistake in fixing the mess Ugra made but we already found what is wrong!

Below you will find the changelogs for the Rave One Dominant Fury campaign after each DCS update. DCS 2.9.8.1107 (04.12.2024) All Missions: updated to work well with taxi directors Mission 01: fixed message with script error; updated mission for taxi directors; updated aircraft placement on deck; updated pattern for the S-3 tanker, it won't keep 40 degrees bank during AAR Mission 03: updated triggers so that both MANUAL and AUTO tapes will gain points for player (previously only in AUTO); fixed static during radio check; fixed static on Strike frequency; switched outdated F-4 models to new Heatblur ones for Turkish aggressors M12: completely re-done the Case 3 departure to match new taxi order with taxi directors NOTE: all RO:DF missions will be updated to the new standard (using HOTAS instead of SPACE BAR, seamless radio transitions, datalink updates) for the next patch.

Below you will find the changelogs for the Rave One campaign after each DCS update. DCS 2.9.8.1107 (04.12.2024) Updated all missions to work with the taxi directors Mission 05: huge improvement in Prince behaviour during the training dogfight; enemy aircraft targeting Prince should no longer hit player instead and correctly shows on RWR; other numerous updates and fixes to the mission.

DCS 2.9.10.3948 Fixes in missions: Missions 1 to 7: - fixed bug with AI aircraft not taxiing from shelters - repositioned Patriot system at H4 and rearranged the vehicles according to Patriot handbook - tuned the route of the safety patrol around the base - fixed flares amount in one mission - changed Lau adapter for single-carried AGM-65D from triple rail version into single rail version with less drag. - updated loadout in several missions - added windsocks at the same spot in all missions - updated assigned shelter number for every F-16 as shelters numbering changed with the update - W31 properly follows B1 on egress (in M02) - Updated AAR part for W31 in M02 (it will refuel correctly every time) Known issues - Mission 01: flight lead and his wingman fails to correctly land at H4 and diverts (critical)

Try to just switch the channels from 1 to 2 and then back to 1.

@feefifofum any thoughts on that?

So far no news on part 2, my co-author changed jobs and has little time to work on the second part. I might get around to doing it myself, but he has a LOT of knowledge on this..

Perhaps. I'll try to have a look shortly, need to finally sort out the radio problems as I don't think fix from ED is coming anytime soon...

The Ugra media update to the map broke many campaigns. As far as I know they haven't addressed it but forced the campaign devs to do so themselves. I will think twice before producing any campaign on their map in the future just to avoid surprises like this one

I don't have any control over where he lands or even if he ejects properly (took me a few hours to set the triggers to make him eject almost every time). Also, unfortunately we can't place shot down pilots on the water (never understood why this wasn't added to DCS yet). So you have to forgive some of the shortcuts...

@gonvise moreover, the campaign will reset time to 1x whenever something important happens, so you won't miss anything while accelerating.

I haven't - and I think somebody is already working on it! Thanks for your kind words!

@Soundman766 @Alkaline @Backsoon @wct24 Guys I understand you completely, but please for a moment put ourselves in our boots (as 3rd party campaign devs): we spend months if not years building campaigns, testing them, updating them in the process to the changing DCS ecosystem (which is a good thing that it evolves!). Then we ship them out, working as intended (with Gamblers there was just one minor hiccup at the start). But then the map update breaks ALL of the missions. Trust me, you couldn't find the more annoyed person than myself when I learned about it.. but then together with some people helping me (big shoutout to Jakes and Gumidek) we just started going over each mission in order to fix what has been broken without our knowledge and involvement. This is the way things work and I think no matter how much controls, tests etc we have, these things will keep happening, with so many 3rd party devs. Yes, I agree Ugra should have communicated with us better - and as far as I know this part of the things (in general) is being addressed. I have to say ED has been very responsive to us and is putting in place different safeguards and systems that will minimize the waiting time for campaign fixes. In the meantime I guess everyone has to just be patient.. all the Gamblers missions should work as advertised as soon as the patch is there. The worst approach for us, as small devs is when people get upset with ED / Ugra / whoever and stop buying our 10$ campaigns as a sign of protest. Trust me, it hits people like myself most.

This is not my fault @Soundman766, we have no control over the patch cycle. Ugra media broke the campaign with their map update, and there was no hot fix until - hopefully - today. We're trying to figure out a way ahead with ED so this doesn't happen again in the future. But we are at patch cycle mercy and we have absolutely nothing to say about it as campaign devs.

I think I might have fixed the missing fence out call.. and as for the AI, he is told to wait, maybe some trigger didn't fire. I saw after recent internal updates that some checkboxes silencing the AI stopped working suddenly..