baltic_dragon

Thanks. Fixed

@Tripomastigote is it in the A-10C II or old A-10C?

Hey. Is it in A-10C II or A-10C version? I am pretty sure I fixed it for A-10C II and I will soon stop supporting the A-10C as almost nobody uses it and the differences between two versions are getting so big it is not sustainable to support both (though I still will fix this issue of course).

Thanks for reporting, will check. There is a DCS bug that makes the AI repeat the same message over and over again... but this should be an easy fix. @CH4Pz is it in A-10C or A-10C II version? If the latter, I am pretty sure I fixed it. If it is former, I am moving away from supporting the A-10C version of the campaign as almost nobody uses it and the two versions are getting more and more different...

Hey! Possibly, but since there is more and more differences between the two versions, I am not really supporting the A-10C version anymore, as huge majority of players use the A-10C II now. I might look into it when I have some time, but currently I need to review all my super carrier campaigns because of new taxi directors being added and forcing me to update all the missions in a short time... apologies for that.

It was more difficult than just swapping the planes, but I think it should work as you describe it - although not 100% sure if everything would work correctly as each campaign maker uses different ways to create their missions. For instance, if you had any cockpit arguments detected that would not work, as some are different for both aircraft.

You can't really use FM for anything else than two digit frequencies (so 30.0 etc). Anything higher than that will require AM modulation AFAIK.

Hey. Yes, this is a know bug that I cannot fix, just the way AI works at Nellis. AFAIK it doesn't happen in any other mission, so don't worry and move on.

Glad you solved it. Didn't know they added chocks to A-10C. I'd say pilot body for VR would be more important

We're reported it long time ago and it is completely out of our hands, one of those DCS issues that happen especially often in Nellis...

We're thinking about adding an extra mission that would cover the new radio, no deadlines to share for now though.

The funny thing is: I played this mission twice recently and it all worked fine on my end. Still, I'll try to make it work when I update a whole campaign for taxi directors etc.

This is a funny one I saw reported but cannot reproduce. Still, the whole taxi logic will soon change and I'll have to run through all the campaign and update it so I am sure this problem will be solved. BTW, didn't know there now are such nice holes on the deck afterxplosions!

Hey, thanks a lot. The AI AAR is wonky and every few updates some bugs with it return that are later repaired.. unfortunately I have no control over the AI and how it behaves. I will have a look at the tanker part on RTB and see if I can do something about it. Funny thing is I just read two or three reviews of this mission (quite recent) where everything work as intended - tanking and "incident" when returning to mother - but I learned long time ago there are bugs that appear for some people and will not for others (I know 3rd party mods do have impact on campaigns as others programs like Voice Attack etc.) In any case - I will be going through the whole campaign and updating it for taxi directors (and adding some other goodies, check the video below for the details) so I'll make sure to make things as playable as possible.

Sorry, didn't have time to get to it yet, but will soon - will need to go through the whole campaign and update it for taxi directors, and will polish a lot of things along the way (currently doing it with the Raven One). Some extra features I am planning to add explained here: https://youtu.be/I3Xyq8TME9Q?si=xfIOzcEdu4z5e3XJ

Thanks. I'll have a proper look at this mission when I start overhauling whole campaign for taxi directors and adding some cool extra features (check video below). I did try it twice and it worked OK for me and VAICOM is known to (for some unknown reason) mess the DLC campaigns and create bugs with AI behaviour others cannot recreate. Still, I'll try to get to bottom of this, but most likely not before full campaign redo which I hope to have finished by November. The BRC will be something that is dynamically changing during the recovery. I will have a look at it but I might not be able to fix it (I had to use several tricks to make this mission interesting that limit my options). In any case that is not a huge thing. The Texaco and Cajun turning.. yeah, that's the AI being AI. Not much I can do about it.

Yep, those things happen. Having said that, I will be checking whole campaign soon to prepare it for Taxi Directors and also add some other goodies, as described here: Raven One should be ready for October and hopefully RO:DF for November.

@Jalava thanks, will check what's going on there.

Thanks. Got it on my to-do list. I'll see if I can squeeze fixing it for the October patch, if not I'll have it sorted out with the full campaign review / overhaul for taxi directors. Thanks!

I admit to having used some tricks, otherwise it would be impossible to get the custom Knight bullseye calls. There is no way around it. As to difficulties locking the proper aircraft - I have no control over that.. but I did try this mission not that long ago and it did work OK for me.

Thanks. I'll see what is going on there soon, as I will have to run through whole campaign to make it ready for taxi directors and polishing / improving things as I go. Already halfway through original Raven One, I plan to have RO:DF ready for November. Also, I am going to implement all this:

Thanks @Jasonmoofang. I will soon have to go through all of Raven One campaign to get it ready for the taxi directors (it will be a lot of work with all the custom voiceovers for Case 3 departure) - so I will also try to address any other issues like the ones you mentioned above. I'm trying to have Raven One ready for October OB patch (not sure if taxi directors will be available then), and RO:DF for November if things work out well.

You just need a DL - having said that, new link4 system is being implemented now and things should be better once it hits the OB. But I have no control over all that and the "dolly sweet" call is more for immersion than anything else in this campaign

Another update, guys - please check this teaser: Thanks to Blinxis for creating this video!

Hey guys, I just came home after almost 2 months away and tried to launch the DCS in VR mode as always (using Closed Open Beta). Before I did I ran Windows Update, grabbed new nVidia drivers etc. I am using HP Reverb 2 with WMR and native OpenXR support. However, despite the headset working OK in WMR, the DCS doesn't load - it just hangs on the first splash screen forever. Any ideas what could be happening and how to fix that?