baltic_dragon

Glad you like it! Though I am hesitant to touch anything, making him behave as he does now took several hours of trial and error.. if it works, let it work :)

Its fine. I mean it is not, and I am pretty upset with the whole situation (as it is completely out of my hands), but at least I know how to fix this and it will be fixed for the next update (which should roll out in 1-2 weeks)

There should be a campaign patch now 2 weeks after the normal one, so we will have all the fixes submitted to ED by Friday and hope they will be out soon after that.

Thanks, will update the cards!

I didn't really change much in terms of logic, apart from adding an option of skipping SPACE BAR / F-10 radio menu and binding them to your HOTAS (it is explained at the beginning of the mission as a picture). Still it should work with SPACE BAR normally and nobody else reported similar problems. I'd need to check how it is programmed as I don't really remember the exact scripting now (too many missions built).

Are you using the stock DCS comms for supercarrier? As soon as you contact the Carrier the DCS takes over and I have zero control over the recovery part... worst case scenario just use an option to skip this mission in Campaign menu (since you already finished it) and move on, but this indeed is quite weird.

It is not intentional and the AI is told to only engage the L-39. Guess the AI is being at their best behaviour there in mission editor everything is set up as it should, so perhaps try to get out of there ASAP when they shoot. BTW there is no way to make the blue side attack any other blue assets in the mission editor...

I was told to wait with trying to fix it on my own as ED was supposed to change some of the settings. No news so far I am afraid... however, I'll run this mission this week and have a look so I can include some fixes for the next campaign update cycle in around two weeks.

The datalink system changed since the campaign was built and I am having trouble making it work. Surely you can continue with the campaign though even if you don't see Biff on the TAD?

Thanks for the info. As I said, I am inclined to wait for the taxi directors as they will break all the missions and will require general overhaul of the campaign, which will make it much better. The changes with taxi logic and supercarrier seem to be linked to behind-the-hood work on the directors and I have already fixed some missions which were broken with the next patch because of that. Since my desire to wait for a level playing field...

No worries. Just part of the problems Ugra threw on us with their Syria map update... other half of the campaign is also broken as AI refuses to taxi, but luckily we found the way to fix it.

Yes the gear failure and whole comms associated with it was intended.

We did some tests and for me and my tester the AI behaved as he should, ie. attacked the target... please see Jakes post a little above and try some of his advice, as it looks as something on your end (which happens a lot recently: bugs that happen consistently to some people, but which me or many other people are not able to reproduce - I hate this kind of bugs, as there is usually nothing I can do to fix them).

Yes, this is a bug introduced with Syria map update. Merging this post with another thread.

Honestly, I am not sure if it made it there or there was another issue with the scoring. I'll have to double check.

Guys, this is a bug introduced during Syria map update. We asked the map producers to fix this but just in case also found a workaround which - if fix is not provided by them - we will include in the campaign patch cycle, that should be less than 2 weeks away. Apologies for this, but it is completely out of my hands and forces me to spend time fixing issues caused by other people instead of focusing on new content. Rest assured this will be fixed though.

I'll check again, obviously something is not right (facepalm).

This is a kind of post I like to read!

Great! Glad to hear the helo landing was fixed. I still have to make a deep dive into Iron Flag comms and will do so shortly...

We were promised that this will be fixed on the ED side (as manually re-doing all the VOs are hours upon hours of work, and it used to work well before). I'll check with them what is the status.

Hey Chase, the campaign was built before the datalink functionality was added. I am currently waiting for the taxi directors not to have to do a full overhaul of the campaign twice (as it takes a lot of time, and taxi directors will make things better, but initially are going to break all missions probably). All should be done soon (ie still this year I hope)

Guys, I'll look at all these issues soon when we get the taxi directors, as I will then need to make a general overhaul of all carrier based campaigns (as taxi directors, although great, will surely mess things up). I will then also check the SA page, add the I/R option to all the missions etc.

I think this is a bug. I've extracted all the coordinates and elevations directly from the mission editor... So no idea why this happens.

But it worked fine on second try?

Glad to hear that it worked!