fixed internally Mission 5, Blade won't join

[CH4Pz]

4 hours ago, gabuzomeu said:

Hi,  I'm  facing  the  same  problem and  using Cat2 does not  solve  it.

Baltic,  would  you  be  so   kind  as to  post track  or video of  the  mission  beginning  until rejoin  at  WP1  ?  This  would  help  in finding the  prroperr  way to go. 

Many thanks

 

Have you tried cat 2, wait for him to hook up (and his marshal goes to the side), then launch and as soon as your A2.5, turn RIGHT to wp1. (others reported start as quick as possible, but i just done my standard start)?. when i follow all these steps he follows me, after doing his 7mi departure

[gabuzomeu]

Hi, 

tried again and this works great!

Many thanks

[Jayhawk1971]

Didn't work for me, unfortunately. I've tried taking off immediately, tried waiting for Blade to hook up and launched as soon as his lights turned on, tried letting him launch before me..... all from Cat 2 and using F10 instead of spacebar. Followed departure briefing to the letter. I do get all the correct voice acting bits, up until the part where Flip says he's doing a 360, so at least I know I'm hitting the triggers. He stubbornly insists on flying BRC on full burner and high AOA.

I'll give it one more try tonight, with autostart and initiating taxi to catapults as soon as possible, before the carrier changes course, and see if that works. 

[gabuzomeu]

This might help (?)

When it worked :  launch  cat2, before  8'30  into  the mission, Blade follows shorrtly , turn occurs  8 miles from  carrierr at  10 000feet,  at 10' from  mission   start

It  failed  when launching  from  cat 2, more  than 10' after mission  start.

 

[tsgucci]

I had the same issue.

On the 2nd attempt I used CAT2, waited until Blade is hooked on CAT3. Launched almost simoulaneously, Blade started to go east with burner on, but 1-2 minutes later he turned to ROCK. After that I had no issue with him, although could not finish the mission because I intercepted the bogey too late.

After T/O I went to 240 heading immediately, 300 kts. climbing slowly. The initial Vector is a little bit confusing whether it is a direct vector to be followed after departure or it is the 240 radial of CaseIII dep.

[CH4Pz]

2 hours ago, tsgucci said:

I had the same issue.

On the 2nd attempt I used CAT2, waited until Blade is hooked on CAT3. Launched almost simoulaneously, Blade started to go east with burner on, but 1-2 minutes later he turned to ROCK. After that I had no issue with him, although could not finish the mission because I intercepted the bogey too late.

After T/O I went to 240 heading immediately, 300 kts. climbing slowly. The initial Vector is a little bit confusing whether it is a direct vector to be followed after departure or it is the 240 radial of CaseIII dep.

the initial vector is essentially to WP1, then knight will send you looking after (249 or something for memory)... theres definitely a bear out there to try and send you off the trail and take up time haha i just box WP1 and set a course line to what ever the rock calls are, then you know roughly bearing & distance from rock to be looking on HSI

[baltic_dragon]

I updated the mission and told Blade to turn directly to WP1, which should be released with the upcoming patch. It worked well in my tests, I have no idea what is going on with this mission and Blade...

[danep]

Running yesterday's beta release, had the same problem playing M05: took off cat 2 and Blade just shot off somewhere at angels 14-15 and never rejoined while I orbited WP1. That startup took a few minutes longer than normal due to technical issues. Played the mission again, this time hustling to launch and get to WP1 and he rejoined.

Of course then I was blocked by a bug of never getting a radio prompt for the second bogey

Also note that the briefing text says to use cats 3 and 4, while the dev notes say to use cat 2.

Edited July 22, 2022 by danep

[alip]

I am still getting this bug as of todays version. Blade flies east in full burner high AOA.

Edit: did the mission a second time. Did a quick startup and went straight to CAT 2 and waited there until Blade was just about to launch. Flew the mission normally after that, no problems.

Edited July 30, 2022 by alip

[baltic_dragon]

THis is one of those things I completely do not understand the AI - and can't find the pattern. Was thinking about spawning new Blade mid-air but this will for 105% break something later in the mission... 

[Grodin]

Yesterday i had the same issue too, launched cat 2 and orbited at waypoint 1 for around 30 minutes, went to check what Blade is doing, he is in the good old high AOE full afterburner loop at 40 000ft heading east over land 100 miles away from wp1. Took control of thes plane and flew it myself to wp1 but not surprisingly that propably broke all the triggers and mission didnt advance.

Tried again, did nothing different and it worked fine. Blade went to wp1 like he was supposed to. Man i really love this DCS AI.
i have a suggestion until the AI is fixed - make a trigger that warns player to restart the mission because "something went wrong with the AI" if either an essential AI plane goes too far where it is not supposed to go, something happens to him or he just isn't where he is supposed to be for long enough time to conclude it is impossible to complete the mission.

Alternatively just show a warning that the AI plane is doing something odd and allow player to continue the mission anyway and pretend that plane is there (unless he has an actual task he absolutely needs to do for the mission to work). This mission for example player could complete just fine alone, let the radio messages play and pretend Blade is there. I think this would be much better plan B than to waste multiple startups just for it to possibly fail again.

Edited August 21, 2022 by Grodin

[Andrei]

Been discussed a lot, but I have a track here with reasonably fast start and Cat 2 departure. Tried both times this config, same result - flying to space  

Edit: got it working. The key thing is to expedite - and I mean really expedite. Start APU and engines immediately and do the stored heading alignment. We're on Alert 7, so this is more or less realistic this time. Once you have 0,5 OK on alignment taxi out to CAT 2 and depart ASAP.

I did this mission 6 times and speed off the boat was the only thing that mattered to me.

F18 Rvn2 M5 Bug.trk

Edited August 25, 2022 by Andrei

[baltic_dragon]

Since I still cannot find a reason for Blade behaving as he does, I will play with it a little and either try to put Blade somewhere else on the deck (or even take off before player) OR have player hot start on the deck. One of the things should do the trick I hope. 

[baltic_dragon]

I launched this mission several times on my end, taking different cats and waiting longer before launching. Each time he did rejoin me at WP1, which leads me to thing that this issue should now be fixed in Closed Open Beta which I am using (and pushed with the next OB update). 

[DimSim]

Tried starting mission 5 twice. Each time, Blade flies away in the opposite direction instead of attempting to join up. Last radio message I have is saying that I'm waiting for Blade. Last message from Blade is he's reached 2.4kft so we switch to Pri#3.

Here's a screen shot of me orbiting rock/wp1 while he's flying fast in opposite direction:

(I'm the white F, he's the blue F approaching Wujah...)

Edited February 19, 2023 by DimSim

[speed-of-heat]

I have exactly the same problem, Blade takes off goes east and keeps on going ... i assume he is trying to defect ...   

[speed-of-heat]

@baltic_dragon this is still happening, i took off from Cat 2,  and orbited WP1 for 20 mins, meanwhile Blade was off on burner and heading east like a bat out of hell...  

[baltic_dragon]

On it, will try to fix this tonight.

[speed-of-heat]

Thanks BD

[baltic_dragon]

OK, I made him takeoff before player and in my tests he goes in AB for some time (I guess this is some new Case III logic), but then turns towards WP1 and arrives there roughly at the same time as player. @speed-of-heat @DimSim can you PM me if you're able to check the new version of the mission before I submit it to check it indeed works for you?

[DimSim]

DCS 2.8.3.37556 Open Beta Changelog reports this fixed.

[baltic_dragon]

I also had two other people test it before the release and they both reported it worked OK. 

[speed-of-heat]

it definitely worked for me