[MISSING TRACK FILE] Right engine stuck in afterburner and then the airplane dies

[ikonane]

- Multiplayer

- Mission that worked a couple of months ago

- Several airplanes got the same errors at the same time

 

 

 

We started with USA Hornets, Hueys and Tomcats cold on Stennis.

My hornet flight had Stennsi TCN at the start but lost it a couple of minutes into the flight.

We never had each other or any friendly aircraft on the SA-page.

 

But me and my flight lead got the same problem at the same time. Our right engine got stuck in afterburner.

 

 

 

We tried to restart the engine which worked but still stuck in afterburner. We turned the right engine completely off but still stuck in afterburner.

 

 

 

We hit the tanker and refueled.

 

 

 

On the way back to Stennis (via radio directions) both of our aircraft died. I managed to start my left engine again and continued on but after a while the hornet spun out of control and I had to eject.

 

 

 

 

Some further problems we had in our four flight Hornets was that no one saw the MiG29S on the radar. Even with an human AWACS giving heading, altitude e.t.c....

 

I only managed to lock them up at almost merge distance in WACQ-mode.

 

On the up side, the IFF worked...

 

 

 

The Hueys altimiter didn't seem to work either.

 

We were down in the lowest left part of the Caucasus map.

 

TacView:

https://www.dropbox.com/s/v8jf1agwsy1ppgx/Tacview-20191121-194906-DCS-ThT%20V47%20Goin%20Fishin%20v3.zip.acmi?dl=0

 

Track file:

https://www.dropbox.com/s/dyuixffcolusasp/ThT%20V47%20Goin%20Fishin%20v3-20191121-194846.trk?dl=0

(Too big to be attached to the post)

Edited November 24, 2019 by ikonane

[ikonane]

Added track file(?) to first post.

 

Can also be found here:

https://www.dropbox.com/s/dyuixffcolusasp/ThT%20V47%20Goin%20Fishin%20v3-20191121-194846.trk?dl=0

[Bankler]

As I participated on the mission event in question, I investigated this issue after this session. It turned out that random failures was enabled in the mission. It wasn't visible in the ME, since there was no "player" slot. Still, when looking through the mission lua file, it was clearly enabled with several failures happening at different times.

 

I was under the impression that random failures only could happen in SP, but that is not the case. Random failures also happens in MP, and affect all planes with the same failure at the same time. No idea if this is intended or not, but it's how it currently works.

 

Some details:

* Nowadays, the failures will be removed from the mission file if you change the Player aircraft to a Client. This was not the case before it seems though, as the mission in question was an old one, had (hidden) random failures, and no "Player" slot. Re-saving the mission did not help, but you could remove them manually in the lua.

 

* With more recently made missions, since you can have a Player slot even in MP, you can still effectively get random failures in MP, as long as you keep that Player slot. The failures will happen on all clients as well.