[BUG] Right Engine start

[Kultteri]

So I had this bug where my right engine just wouldn’t spool up at all. Have started the same way from yesterday always but today suddenly after about three hours of flying SP and MP I couldn’t start her up. Left engine spooled just fine always but no luck on the right. The problem only faded after restarting DCS. Maybe something to look into if anyone else has had this

 

 

Sent from my iPhone using Tapatalk

Edited April 1, 2019 by Cobra847

[ScopeDope]

I've had the same issue, and had one other squad mate say the same. The issue for me happened for the first time on a MP server with human RIO. All other 20+ starts I've done have been fine before that, with Jester.

[Kultteri]

I've had the same issue, and had one other squad mate say the same. The issue for me happened for the first time on a MP server with human RIO. All other 20+ starts I've done have been fine before that, with Jester.

 

 

 

I had that issue also pop up first on MP and it transferred over to SP. No human RIOs though

 

 

Sent from my iPhone using Tapatalk

[IronMike]

I marked it as DCS bug, simply because stuff like this can happen in different shapes and forms if flying for too long without restarting with DCS. We will take a look if there is something we can do on our side. But in general a restart is adviced after each longer mission.

 

Thank you for reporting.

[Cobra847]

To contradict IronMike, this issue is tracked in another thread. The Right engine will not light after repair or re-start. Fix in progress.

[QuiGon]

To contradict IronMike, this issue is tracked in another thread. The Right engine will not light after repair or re-start. Fix in progress.

The other thread: https://forums.eagle.ru/showthread.php?t=235738

[Kultteri]

I marked it as DCS bug, simply because stuff like this can happen in different shapes and forms if flying for too long without restarting with DCS. We will take a look if there is something we can do on our side. But in general a restart is adviced after each longer mission.

 

Thank you for reporting.

 

 

 

I believe I flew for about 2 hours before I had the problem. At first I could after a few tries to start it but maybe 1 hour later it refused to start alltogether.

 

Now as you said it could be a DCS side issue as I have had similiar things happen with the Mi-8 aswell. However that could be me just doing something wrong as after is just let the engine spool down and then try to start it it works always.

 

Also as with the tomcat I have always done the startup the same way.

 

 

Sent from my iPhone using Tapatalk

[Aisxos]

I have this same bug. Happens only on certain servers, and happens regularly on those same servers. Essentially every few times I get shot down and respawn in the B tomcat there is a chance it will happen. Not sure if relevant, but it happens often on a server running foothold.

[Enigma89]

Just had this bug, restarting computer fixed it.

[RedeyeStorm]

Yep me too and no repair or rearming of the bird. Only fresh planes will do!

[XCNuse]

Friend just had this as well again; surprised this bug still exists 3 years down the line.

For the sake he instead quit to main menu, loaded into a "quick flight" cold start, and engines would not ignite (F14 Bravo)

F14A would not start either

 

 

Crashing the F14 means you can't fly it until a game restart.

Unfortunately I forgot to remind him you have to save tracks on single player so I have no tracks.

 

But seems to be the case again if you crash the aircraft, it has the likelihood of not starting.

[Hummingbird]

this bug is back

[IronMike]

Thanks guys, another one of those we keep fixing that keeps coming back for some reason. We'll take another look.

[Shadow86]

It's a pretty major bug if you have to restart the game every time you need to have an effective respawn.

Complete buzzkill.

Edited June 9, 2022 by Shadow86

[LanceCriminal86]

I experienced it but didn't have to restart the whole of DCS. Crashed the jet, and either did the shift-tab for a new jet or hit re-fly and as mentioned the right engine wouldn't start after moving the throttle up. Exited the mission back to mission editor, and hitting fly again worked.

[cailean_556]

Literally having this bug at the moment in the F-14A - I thought I was losing my mind.

I had just respawned from a "controlled rapid disassembly" - pulled back on the stick as much as I could while supersonic at low level. For science...

Seems I'll have to restart the mission.

EDIT: Restarting the mission and getting out of and back into the Mission Editor didn't fix the 'right engine won't start' issue. Had to quit out of DCS completely.

Edited June 21, 2022 by cailean_556

[Shadow86]

An update on my end: it doesn't happen every time you respawn, which I assume is why this bug is so elusive.

It had happened to me twice in a row in the F-14B. I don't remember the circumstances of the second instance, but in the first one I had simply ran off the side of the runway when recklessly taking off on afterburners. The aircraft wasn't completely destroyed, but it ended up in flames and most definitely not air-worthy, nor even land-worthy.

From my humble (humbler than before) perspective, the plane has some issues resetting damage states. Just like repairing doesn't fix jammed flaps or blown tires, it may be failing to reset certain specific engine damage at least after respawn (Shift+R).

[dorianR666]

not sure if same bug, but i once spawned as air start and both engines died right away and couldnt be reignited. and before someone asks, no, it wasnt because my throttle was in off position, my hw isnt capable of that function.

i didnt have to restart the game though, just restarting the mission was enough.

  

On 6/21/2022 at 2:09 PM, Shadow86 said:

From my humble (humbler than before) perspective, the plane has some issues resetting damage states.

agreed

reminds me of identical issues in xplane addons

Edited June 23, 2022 by dorianR666