baltic_dragon

OK, I'll have a look. Thanks.

Mission 6 - it is a bug with AI F-14s, reported ages ago. Maybe try to move a little bit forward in the beginning of the mission. To fix it I would have to rebuild the whole departure sequence, which means - with so many VOs - around 6-8h of work to find a workaround for a core game bug which I hope will be finally fixed. I'll check if there is any update on that.

Hey guys, a hute A-10C II overhaul is out, but it is quite possible I missed some things - or they changed in DCS in the meantime. For the time being I see such example in M02. When you contact Prowler, you won't hear comms with him (6 lines in total) until he gets to Bravo. Not a mission-breaking thing, but letting you know. Apparently core code for the radios changed between me updating this mission and releasing the overhaul. I will fix it for next update.

Hey - was it after the update? If not, try it again in new OB (and in A-10C II), everything should be working now.

@Spirale thanks. For F-16 yes, Reflected is doing one for Kola Map (and I am doing F-18). But I also am quite advanced with F-16 campaign in Syria I am working on with John "Rain" Waters, former F-16 demo pilot (host of the Afterburn podcast).

I tested the whole campaign and in 90% of cases he did work (note: do not use specific commands, "like engage tank with maverick" which indeed does not work, but "engage armour"). That is on DCS. As for spikes all the time, I silenced this comms in the overhaul, he should be much more quiet. What can I say.. the AI wingman has a lot of flaws currently. That is why in other campaigns I use AI flights which you can give limited amount of orders, but at least they obey...

Yes. Guess what.. in the meantime (ie after I finished working on this mission) the core code in DCS introduced a new bug which killed all the communications on FM sent by airborne assets (or maybe it is on purpose, not sure). So in M2 you won't hear the comms from checking in with Prowler to the moment when they enter Bravo 2, after that everything works OK. Sorry about that, love situations like this... EDIT: it looks like it is an intended change - aircraft that do not have FM radio cannot transmit on FM frequencies anymore... I'll have to update this mission and check others if that doesnt happen somewhere else. Guess I'll need to prepare an overhaul of an overhaul

@Gloopyare you on stable or Open Beta?

That will be one of the last ones.

Because they are two separate flights and DCS does not allow me to change the second digit, so it will have to stay like this or one will be 21 and other one 31, both wrong...

Thanks @Sulfa!

Thanks! I will just tell the player to go to CAT 1 good find!

Yeah, kinda scary! Not campaign related for sure...

Yep, will look into it for May update.

I cannot reproduce this, it works fine for me every time. Thing that helped some people was full repair of DCS. Other than that I have no idea what to do, sorry A track from your playthrough would be helpful, there may be some user error with the radios involved.

I can't tell the AI not to refuel, but I'll try to figure something out...

Uh, I love the SC AI.. I'll fix R1 for May update, won't be able to do that for April

This is very weird. I'll have a closer look at R1 for the next (May) update, no time for April (troubleshooting missions that used to work but get broken with every other update takes waay to much of my time anyway). Thanks for the track and the report.

The user files section is very old, unless stated otherwise use the latest version of the campaign that gets automatically installed. TACAN doesn't work in A-A mode for tankers for quite some time now, you need to be in T/R as rob10 says. AI crashing into the tanker.. well, I have completely no control over that. I just assign the AI a mundane task which it messes up royally, which breaks missions making people upset with my campaigns but that's part of DCS and we all have to live with it I guess...

@CH4Pztry to run a full repair of the campaign and check if you have 3rd party unofficial mods installed. They also tend to break things...

But that would mean that the author should be constantly playing all his campaigns on several versions of the DCS to be able to tell that, and this author barely has time to keep up with updating the old stuff that constantly gets broken (on top of many projects he has open). So while a good idea, I am afraid completely unrealistic... Don't get me wrong - I will still aim for the same level of fidelity, but avoid huge strike packages or things that are too scripted / rely on AI too much. But I am sure you'll like what I am working on!

Hey. This mission will need a solid rework, so many things went tango uniform after several DCS updates that I might need to re-build it from ground up, which I'll do for May update. As for the coordinates - I spoke to some pilots and they said it was a common confusion to get coordinates in specific format without mentioning which one it was, so I did it on purpose here confusion is part of the job!

Hm.. so they show SD as they should (first and last letter of the callsign)? This is on purpose (and wasn't possible to do in many other missions).

There is no way for me to tell if you hit or miss but to use a timer - if something doesn't happen within X seconds, mission assumes it didn't. You probably shot at maximum range or something else changed. This mission needs a solid re-work (also because of the still existing bug with the coordinates I think) so it will have to wait for the May update.

I just finished updating the A-10C II version of TEW, all of the missions. But Harrier has to wait until I am done with majority of work on F-15E and F-16 campaign at the moment...