baltic_dragon

The RTB is linked to time on station so if you take too long to find targets this may happen. Still, I am about to start the overhaul of whole RO:DF in preparation for taxi directors so I'll make sure this mission works as intended.

Yeah, but there can be ways for me to fix it too. In any case I will soon be updating whole campaign (making it ready for taxi directors) so will try to address this issue as well. Many thanks for the report @dggoofy

I'll make sure to update the coordinates when doing the RO-DF overhaul. Thanks guys!

Glad to hear that. I am almost done with the update for the Raven One and I'll get on RO:DF next, fixing bugs and updating stuff - will have it done hopefully for December update.

Hey! I know there are issues with M11 and thanks for this detailed description. I am now working on major overhaul of the campaign (today on M10) and I intend to spend as much time as it takes to make M11 work as well as possible. Now, first JSOW is intended to miss but yeah, the wingman is absolutely necessary for this mission - I’ll fix his behaviour. You can expect a fully refurbished campaign during November update. I’ve already stumbled upon problems with AI flights that took hours to fix somehow (sometimes deleting the old flight and creating a new one from scratch). Thanks!

So I thought I'd start making regular updates on what is coming, starting from October.. you'll see the most recent one in the initial post.

Hey guys, update - seems for some reason the unit that was transmitting the messages got its frequency completely reset to something else. I've fixed this, also updated the logic of how Chevy 4 and 5 get on station. Hope this works better now!

Hm.. possibly Smoke is going stupid if he takes off long before you do? I think I've updated it for the campaign overhaul - but glad it worked & sorry you had to spend so much time on this!

Hey @DaveDewhurst. I've updated this mission and flew it probably a 5 times recently and each time it worked well for me. In any case, perhaps the upcoming OB patch may fix things with the AI behaviour. I'll also have a fully updated Raven One (with lots of bug fixes and goodies added) ready for November patch (unfortunately I wasn't able to get all the missions updated in time for October, I spent hours on two of the missions trying to make the AI do what they were supposed to). In any case, this is a mission where some people have problems, but for the majority (including myself) it works as intended - so it is difficult to troubleshoot it. I will check the track file. BTW, are you using any unofficial 3rd party aircraft mods, Voice Attack etc? These are known to break the AI behaviour in DLC campaigns. Also have a look at this thread, same mission, different problems magically disappearing at some point... gotta love the AI

Hey! Thanks. Not really, this is the wonky DCS AI at its best. I've seen the helos do a lot of weird things in this mission, but also saw them performing perfectly well.. I did all I could to tweak / deconflict them, but some things I just can't control...

@CH4Pz this is now fixed. Thanks

@Emuyen replicated and fixed. Thanks!

And it is internally fixed now. Thanks for reporting.

OK will try to fix this for next OB patch!

Thanks for the info! Yeah it works fine every time on my end...

I'll try to fix it today for the upcoming OB patch. Thanks!

Hm.. try to run a repair. It doesn't seem like a campaign problem (I have no control over things such as wheel chocks etc). If this persists please send me a track.

Well, Saint will be back in the third part which IS going to be a training one (akin to Iron Flag).. so this should be fun.

It will be in the next update. Was meant for September but there was none

Yes, AFAIR you have to wait for Sluggo to shoot first. As for the external software I don’t really know, should be enought to not load / run it, but this is something that is really difficult to put one’s finger on.

I am using Closed Open Beta for updating missions because I can catch bugs about to be added early.. but that means I won't be able to send you updated version of the mission for testing because it likely won't work at all, at least until next OB patch hits. Apologies! But I can do a different thing, if you are in Discord, please hit me up there (balticdragon). Thanks!

No idea @algherghezghez. I flew it twice as I am updating whole campaign and it works for me normally, as it does for two of my testers. Do you have any unofficial 3rd party mods installed or use software such as voice attack etc? Also, perhaps try to run a full repair. This problem seems to affect certain people but works OK for most and we've discovered some time ago that 3rd party mods can affect AI behaviour in campaigns... Another thing - what are your PC specs? On slower machines it takes some time for the AI to notice "stop" flag (in this case: "stop following" flag) and may cause behaviour like this. Let me try something and send you an unprotected version of the mission to check if it works for you, ok?

I also ran quite an extensive update for this mission today, fixing instances where Olive would not attack with Mavs. And noticed that now you can finally see labels (I am using dot-neutral) in NVGs, making this mission very enjoyable!

Thanks @RogerRoadie! I am updating Raven One right now and for the most part missions work OK, but there is always something that can be improved or made to work better. I've made some changes to M3 as well, but nothing ground-breaking so far. Enjoy the rest!

You shouldn't use in-game comms for AWACS and wingmen, the Marshal works normally apart from M01 which is completely custom - built, the rest uses normal supercarrier comms. Maybe I need to update the readme to be more specific on that as for the ADF.. I didn't use ADF in any of the missions, I honestly forgot it was even implemented in the Hornet. So not sure what happened there!