Concorde Engine 4 issue

Atebis

Hello,

I'm a at a loss at the moment with Concordes engines.

I'm able to start all 4 engines without problems - but engine 4 is shutting down within (at max) 2 minutes and refuses any attempt for restart.

I tried the cold&dark way from manual and from several YT tutorials.
I tried to start directly on the runway with all settings done automatically.
I tried ctrl + e.

The result is always the same. All settings for all engines are the same. Engine tanks are filled, 1-3 are working normally. 4 is shutting down. I'm using SU8 so this can't be the shutdown-bug-after-afterburner from SU9 beta.

It doesn't matter whether I'm keeping the engines on idle or setting them to xy %. No. 4 even shut down in mid-take off with N2 and N1 percentage slowly decreasing like a normal shutdown.

I was unable to find any post about this topic.

Any ideas?

Best regards,
Atebis

DC1973

@atebis Check the Eng 1_4 switch in the CoG management panel is in the "Norm" position, not "AFT" - this restricts fuel flow to the 1 & 4 engines and may be the cause of your problem.

Beyond that I cannot say - I have not seen this happen, most haven't, but I did hear at least one other person report it so I know it's a thing, we just can't tell what is causing it and have not been able to replicate it.

Atebis

@dc1973 I checked the switch. It's in Norm position.

I tried to find some kind of pattern but was unsuccessful so far. It doesn't matter whatever I'm trying, the engine is shutting down.

I will keep trying. Maybe I'm finding a helpful clue.

DC1973

@atebis If you find it, do let us know, and it might not be Concorde that's entirely behind it. Sometimes the sim does these weird things and nobody knows why ( like the CTDs and black screen bugs ).

Atebis

@dc1973 I found it.

I realized the only common event for every engine shutdown was a movement with my mouse, so I checked the bindings.

There was a binding for the mixture 4 axis to the x-axis of my mouse.

I have no idea where this binding came from but deleting it worked to fix the problem. :-)

DC1973

@atebis Amazing, well done for spotting the problem and thanks very much for sharing it with me. I will pass it on at the MS forums so that as many people are aware of it as possible! :)