baltic_dragon

It should be fixed with the upcoming patch, so on 21 Feb

Will do. I knew this new radio system will bring nothing but problems... working hard to get it working again.

This sounds like the DCS bug with stop flag not being fired for some people. Do you have any 3rd party mods installed? Do you have Vaicom or Voice Attack? Finally, are you on MT or ST? All these things may be the reason.

AFAIK this can be something else, but colours make most sense. I've seen it being used by USMC (as described in one of the books) and also USAF, so I guess this would be the most standard procedure. And thanks for the kind words!

Just replied in the other thread. Seems that all is fine on your end. I'll try tomorrow and see if it works for me. They are tinkering with the Supercarrier for the flight directors so it is possible that something got borked, but all the waypoints and triggers are set correctly for Smoke and I have no idea what I could do to change his behaviour. Will report back.

Hey @NavalAV8TR. I cannot reproduce this bug, but I've heard it may be happening to some people - likely the same issue as the bug with task stop flags not working for some folks. Do you have any unofficial 3rd party mods installed? Also, do you have VAICOM or Voice Attack? These may cause strange AI behaviour in DLC campaigns. On top of that for some people switching from MT to ST helps. And finally - try to run a full repair of the DCS, that also worked for some. As I say, for me and all of my testers this mission works as it should and that is why it is difficult to troubleshoot... let me know pls!

By all means please do! I'll do my best to fix these as quickly as possible. Thanks!

Glad to hear that. Enjoy!

Glad to hear that it worked on second run, this must be some DCS ghost in the machine this mission for some reason is creating a lot of trouble for some people and on my end works flawlessly.

I didn't update the legacy version as there are more and more differences between the two airframes and it is getting increasingly difficult to keep up - and huge majority of people are using the A-10C II. But I'll see what I can do.

Hey @nikoel and thank you for your feedback, well received! Just a few comments: On MGRS: I assume the issue with 37 or 38Y (or T or whatever it is) that causes issues in Caucasus. This is done on purpose and many people learned this the hard way, but were happy afterwards. Unless your'e talking about something else here On M21: not sure what happens there, but please PM me the details, I'll look into it. In general the stock AI wingman is a nightmare and now I am exclusively using wingmen as separate flights. Less flexibility, but much more reliable. About talkative pilots: it was my first campaign and should I do it today with everything I know now, I would have built it differently in many places, including idle chatter which I almost never have now (apart from ferry flights, like the first mission in the upcoming Gamblers campaign, where during 8+ hours of flying pilots not only talk a lot, but also play games like ships in their cockpits). But this point is valid and I've moved away from this since having worked with many real life pilots (especially in the Navy they seem not to like any redundant radio comms). As for the Mirage - with the help of one of the community Members, I'll submit an updated stock campaign for the M-2000C (with some bug fixes and improvements). I hear it is still fun (although also pretty old). Anyway thanks for taking the time to type this & your honest evaluation. I really appreciate it and thanks to posts like this I am evolving as mission / campaign designer.

Yeah, I think these are glitches that are caused by the deck crew coming and once these are in, things should work better (I've seen them in action and the deck is much more orderly when these guys are around). We just need to wait a bit.

I am so waiting for the taxi directors, as AI behaves much better on the deck with them... what is happening now on the deck of super carrier is absolutely crazy.

That is weird, I did update that... I'll check. And in long mission they already spawn in the air, which is even more weird.. OK - it is internally fixed, but there was no update in January and that is why I thought I submitted it. Fix will be out with February patch.

Glad to hear that! Hope you'll be a much better Hornet driver when you finish this!

Gratz & thanks @pbt31!

We're working to fix this issue and should have it sorted for the next patch!

Yeah, because the super carrier is getting the taxi directors, the logic for AI during landings and take offs is constantly changing - so I'll be able to fix all the missions only after the deck crew is properly implemented. Otherwise I'm afraid my work will be wasted as things seem to be in a flux right now.. sorry about this.

Most likely that is the issue, the campaign should be more up-to-date on Open Beta. Soon there will be no distinction and also I will overhaul all the mission to take into account the upcoming deck crew - so any bugs and problems will be fixed, although it will take some time... stay tuned and sorry for any bugs you encounter (most of them just are introduced with changes to core DCS and sometimes are difficult to fix straight away).

It shouldn't be anymore unless some new bug was released with last update. The next one is still some time away, which should give me time to fix the fix (sighs)

Yeah, that would be an easy fix but requires time I don't have now with lots of fixes I still need to make and a lot of backlog on my new material. But I'll get to it. Will keep you posted about M15.

Hey. It is not possible, since in the first place I am not able to reproduce this bug so don't even know where to start. And building safeguards into my campaigns, which have several hundred of triggers (or well over a thousand) in each mission would just not be humanly doable. I am just hoping that ED, who acknowledged the problem, will be able to find a fix....

Thanks, I will check this. I'll have to refresh my M-2000 skills though, I don't remember how to fly it anymore

Seems like some user error to me. Are you checking the in-game kneeboard or the pdf document (though I don't think any frequencies changed)? This all worked for me last time I tried it.

Perhaps. Glad you got it sorted though!