Mission 13 - Sting never breaks for IP

[Number481]

After joining up with Sting flight at WP2, and after Sting has been told by Strike to break for IP, they never actually break off.  Just continue to follow around in a (wide) formation with Devil flight.

Also, this is the only mission I recall where I didn't get a "joining up" call from the flight we are grouping with at a given waypoint.  Not sure if thats just not in this mission or if it is a symptom.

Also not sure if this is just the AI script trigger issue that many of the campaigns were facing (which I thought was fixed in the last OB update)

[Badger633]

10 hours ago, mjfrisby said:

After joining up with Sting flight at WP2, and after Sting has been told by Strike to break for IP, they never actually break off.  Just continue to follow around in a (wide) formation with Devil flight.

Also, this is the only mission I recall where I didn't get a "joining up" call from the flight we are grouping with at a given waypoint.  Not sure if thats just not in this mission or if it is a symptom.

Also not sure if this is just the AI script trigger issue that many of the campaigns were facing (which I thought was fixed in the last OB update)

Hi

Thanks for the heads up. Will check it out. Yes the AI issues are making it difficult for campaigns at the moment and yes don’t think the follow issues has been sorted.

Did you keep to 300kts or below to allow Sting to join?

Will update you with what I find.

EDIT: Just flew current issued mission. Sting behaved correctly joining and breaking for IP. Make sure you keep below 300kts until they join. Also are you running any mods? Campaigns are only written and tested with no mods.

Sorry but cannot reproduced this end. Try again as above let me know if you have any issues. If you can send me a Tacview if you have a problem.

Badger633

 

Edited December 27, 2022 by Badger633

[Number481]

Interesting, Thanks. 

I run a few pretty basic mods like custom auto start script and countermeasure setup and OpenComposite/OpenXR for VR as well as Vaicom/VoiceAttack, which I guess is technically a "mod".

Will try pure vanilla and let you know what I find.

 

Thanks

[Number481]

On 12/27/2022 at 3:00 AM, Badger633 said:

Hi

Thanks for the heads up. Will check it out. Yes the AI issues are making it difficult for campaigns at the moment and yes don’t think the follow issues has been sorted.

Did you keep to 300kts or below to allow Sting to join?

Will update you with what I find.

EDIT: Just flew current issued mission. Sting behaved correctly joining and breaking for IP. Make sure you keep below 300kts until they join. Also are you running any mods? Campaigns are only written and tested with no mods.

Sorry but cannot reproduced this end. Try again as above let me know if you have any issues. If you can send me a Tacview if you have a problem.

Badger633

 

 

FYI, after many, many tests, I have been able to isolate the issue to Vaicom Pro (community version).   If I have VoiceAttack running (even if I don't make any calls to it), Sting will not break.  If I leave VoiceAttack shut down, Sting breaks without issue.

 

Theres a new community version of Vaicom that was just released which has the following in the release notes:

"- renamed timer to dev_timer in luas to avoid clashes with other mods"

I'll give the new version a try and report back.  It's unlikely that will resolve it, but worth a shot none the less.

 

 

[Badger633]

46 minutes ago, mjfrisby said:

FYI, after many, many tests, I have been able to isolate the issue to Vaicom Pro (community version).   If I have VoiceAttack running (even if I don't make any calls to it), Sting will not break.  If I leave VoiceAttack shut down, Sting breaks without issue.

 

Theres a new community version of Vaicom that was just released which has the following in the release notes:

"- renamed timer to dev_timer in luas to avoid clashes with other mods"

I'll give the new version a try and report back.  It's unlikely that will resolve it, but worth a shot none the less.

 

 

Thanks so much for that feed back. Have been having strange things happen from time to time when mods are employed but vary rarely  is the cause  identified.

Will pass it on to ED.

Badger633

[Sylosis]

More than a year late, but I have that same problem and it's the first time I try this mission. I have no mod installed and I did wait below 300 for Sting to join. Sting even confirmed they had joined Starboard, way before they had to break for IP. 

Got the radio message to break for IP, they replied they are breaking for IP, but stayed on my wing.

Accelerated time quite a lot to make absolutely sure and they just stay there.

Edited March 7, 2024 by Sylosis

[Badger633]

Ok will take a look. Do you have the free programme Tacview and a Tacview file of that flight? Are you open beta? Have you flown this more than once and did the same thing happen? If your first time could you try it once more.

Thanks

UPDATE

Just tried it here and Sting split as required. Can you run it one more time to see if it works. Thanks 

 

Edited March 7, 2024 by Badger633

[Sylosis]

On 3/7/2024 at 1:41 AM, Badger633 said:

Ok will take a look. Do you have the free programme Tacview and a Tacview file of that flight? Are you open beta? Have you flown this more than once and did the same thing happen? If your first time could you try it once more.

Thanks

UPDATE

Just tried it here and Sting split as required. Can you run it one more time to see if it works. Thanks 

 

 

All right so I tried it two more times and everything was OK on both occasions. (and I still haven't managed to finish the mission! XD)

I'm almost certain I did everything the same on every occasion, but anyway, at least it works.

[Badger633]

Hi @Sylosis

It is just DCS, you can do everything the same and every now and then it won’t work. Sometimes depending on what’s happening the sim seems to miss a command, I have seen it many times. It’s a big problem when designing quite detailed missions it’s as if too much is going on for the system. 
Which part of the mission is giving you a problem now?

[Sylosis]

5 hours ago, Badger633 said:

Hi @Sylosis

It is just DCS, you can do everything the same and every now and then it won’t work. Sometimes depending on what’s happening the sim seems to miss a command, I have seen it many times. It’s a big problem when designing quite detailed missions it’s as if too much is going on for the system. 
Which part of the mission is giving you a problem now?

Ah well it's just me being bad! XD

First try my Mig29 target dodged my missiles and killed me (shot 3 missiles at me, dodged 2, died with the last).

Then the second time, I got too low when trying to rifle the vehicles. They shot AAA at me and they had one lucky shot. ONE bullet hit me and turned out to be a pilot headshot....

[Badger633]

You will get it. I did a tips video on hitting the vehicle in that mission.