baltic_dragon

For any of my campaigns you need to disable easy communications, otherwise you might get a lot of bugs.

I wish there was an option like this for AI, this would help A LOT with development. We've asked ED for that many times, but never got a positive reply.

Had to script it with two APP channels so that flights don't step on each other when player is not exact with the timing. Unfortunately there are limits to what can be done with the ME and I always have to account for user error...

@This thank you so much for your feedback. You hit the nail on the head there, especially with the bug - update - new bug vicious circle which does take a lot of my time. Thanks to great community I recently started a closed group of people who are trying to test the reported bugs and suggest fixes, which should buy me a lot of time I would otherwise have to spend re-flying everything, but still constant new problems with AI are generating quite some trouble. On the other hand - DCS is a very complex beast with code that dates back to Lock On days at some places and this has to be almost impossible to keep bug free. Guess we all have to live with it - and also focus on less complex missions, which I intend to do in the future (don't get me wrong - it does not mean less realistic, just less reliant on AI and probably a tad shorter). Once again, appreciate your feedback a lot!

Yeah, need to find a way to disable AAR for the Mirages. In the worst case I can just de-spawn them.

OK, I'll need to have a proper look at the whole mission, there seem to be several things wrong with it now.

Thanks, I'll check this.

Knob should be on OFF I think the way the mission is build. I'll update it because too many people are experiencing the issue there.

Another one I'll have to have a close look at, there seems to be many different and conflicting bug reports. I'll have a look.

Unfortunately to have the mission work as intended I have to despawn the old carrier and spawn a new one, and DCS doesn't handle it well. There is no fix, you just can't use TACAN for this one.

Hm, and I fixed it twice already... I'll have a look again, but last time I checked it worked OK on my end. Unless the AI ground units pathfinding was borked again.

Yes, he is set to "invulnerable" because of the storyline. He probably ran out of fuel and if immortal AI does it, then it just bounces like that. The real issue is why he ran out of fuel as he should not have unless it took a really long time for you to figure out the targets... I'll have to rework this mission as it seems there are a lot of trouble with it.

Hey! As for the area, I had to put the action there to be able to recreate this iconic mission from the Raven One book - and had to build the city there from scratch using the statics. I know this is not perfect and I had a lot of doubts whether I should go ahead with it, but in the end decided the sortie is worth it. As for the maps - I can use what we have in DCS, I am not capable of producing additional maps. Or maybe I could but it would take a crazy amount of time which I don't really have (I am struggling to fix bugs / work on new content in 2-3h I have a day for DCS already). As for rejoin - if it is added to the briefing it is mostly for flavour, because DCS AI will do its own thing anyway. The only difference is if you are to join up at a specific waypoint, but normally you have to treat it lightly...

I think DF works fine at the moment, though DCS is DCS and there always will be some bugs and issues with the campaigns. But I don't have any major outstanding issues with it at the moment. Haven't tested in MT version though.

Not yet and I am not sure I'll be able to fix it for the next OB given very tight deadlines I have now for the Strike Eagle. But I'll do my best. The problem is that each bug requires me to re-fly the mission, find the problem, apply the fix and then re-fly the mission to test it... and I effectively have around 2h for DCS a day given day job and family. But I'm putting together a team of volunteers to help me with testing, which I hope can speed things up!

@GumidekCZ that is a good idea. The date won't match to the briefed one, but it doesn't matter that much I think - if you can find a better setting, let me know, happy to update it. Otherwise yeah, I'd have to change the whole mission which I may do at some point (planning to run & overhaul the whole campaign in the future, but too busy with a lot of other projects currently to be able to do it).

Yes, that is my general lesson too after both Raven One parts. That campaigns need to be less complicated and much less relying on AI, which I am implementing moving forward with the F-16 campaign and the Kola one. Thanks for the feedback @Taz1004

Ah, the old problem of 37/38. Yeah, the grid changes in the middle of Georgia which led to problems before. Marking it as 'not a bug' then.

Comms or just wrong freq? I assume the latter, wrong radio discipline can lead to a lot of problems (even for me, I had this happen a few times during testing when I forgot to switch the freq). But I will have a look, maybe I forgot to change something with the freqs.

It is touch and go. Sometimes he acts like Tom Cruise on steroids and sometimes they just die soon after takeoff. That is why I stopped using the stock wingman all together in other campaigns.

Thanks! Yeah, I think for FM just use the bottom radio and things should be fine for most part. For the ARC-210 only AM and UHF.

Yep, all is there in all my campaigns!

Yeah, make sure to read the manual and follow the instructions, this is I think the most complicated part of the whole campaign (and also was to write in a comprehendible way, which probably I did not really succeed in doing, LOL). Have fun with the rest!

I don't think needles work & assume radio channels messed up if you didn't hear anything? This mission has a lot of moving parts and it is easy to break something by not following procedures - so please let me know if it happens again or if someone else has experienced it.

You can also ask your wingman to engage the targets. I'll check this when able, but since the mission works it isn't a very high priority at the moment.