v1.0.9 EGT

[dib669]

Thought I'd try a quick flight in v1.0.9 today, encouraged by the expansive change log and promise of many improvements.

Unfortunately, from a turnaround state (not having been flown before today) engine 1 has an EGT at gate of 1495C (engine 2 is at 10C - i.e. ambient) hence I haven't been able to get engine 1 started.

Any ideas on how to reset this? I've cleared all WASM folders, although I don't supose that's got anything to do with the problem.

Thanks, dib

[JS2Tango]

Exact same issue here, Engine 1 won't start, continuously cools.

[deepblue_80]

I observe the same issue with both the 900 and 1000 variants, all liveries, WASM folders cleared after update. Sometimes, EGT 1 directly jumps to 1495C and is not coming down anymore (i.e. engine start not possible), sometimes I see the EGT 1 rise as soon as I switch on the batteries and look at the ENG page up to roughly 350C, while EGT 2 remains at outside air temperature. In the latter case, an engine start is at least possible after some cooling.

I have not yet been able to reproduce that 100%, but it seems to me that the first issue (EGT unrecoverable) appears with some liveries (G-XWBJ, for example), while others simply develop a slightly elevated EGT 1. But in all cases, EGT 1 is always not where it should be.

Edited Saturday at 11:14 AM by deepblue_80

[JS2Tango]

Putting engine one into CRANK for a minute, and then straight across to IGN START seems to solve the bug. Come on iniBuilds, you had a great aircraft prior, now full of silly bugs - where was the testing? Please sign me up to your testing team, I have IRL experience that you'll find helpful I'm sure. 

[deepblue_80]

51 minutes ago, JS2Tango said:

Putting engine one into CRANK for a minute, and then straight across to IGN START seems to solve the bug. Come on iniBuilds, you had a great aircraft prior, now full of silly bugs - where was the testing? Please sign me up to your testing team, I have IRL experience that you'll find helpful I'm sure. 

It does, in the second case I described, but not in the first one. Once the EGT is at maximum, I found no way to reduce it again by any means. Engine 2 simply works totally normal.

[JS2Tango]

2 minutes ago, deepblue_80 said:

It does, in the second case I described, but not in the first one. Once the EGT is at maximum, I found no way to reduce it again by any means. Engine 2 simply works totally normal.

The solution I put was from the EGT on ENG1 being locked at its maximum.

[Serano]

Exact same issue here, but it´s Engine 2

[alex6463]

Exact same issue here but on engine 1 . Also did it on 2020 as well.

Edited Saturday at 05:30 PM by alex6463

[mari8it]

same here, ridiculous don't they test before update release?

 

[ykeyre]

2020 or 2024???

[Powie]

2024

[Powie]

[Brendan03]

 

11 hours ago, JS2Tango said:

Putting engine one into CRANK for a minute, and then straight across to IGN START seems to solve the bug. Come on iniBuilds, you had a great aircraft prior, now full of silly bugs - where was the testing? Please sign me up to your testing team, I have IRL experience that you'll find helpful I'm sure. 

I attempted this, as well as a WASM Reset, MSFS Restarted (3 times) and no change/improvement.

The oddity is that I flew yesterday without any issues on 1.0.9. I spent an hour on this issue, Tried fiddling with the FADEC switches, Using the Manual start. Nothing. ENG2 was on Cooling but eventually started. ENG1 just would not play.

Ended up finding a backup of 1.0.7 and I'm flying that now.

Edited Saturday at 10:58 PM by Brendan03
Wording

[MaxiMoose]

Same exact Issue here..... the suggested solution of putting it into CRANK for a minute did not work for me either unfortunately. Come on Inibuilds, how do you guys miss something like this?

[P4RZ1VAL]

Hello, i have the same Problem. I can "fix" & replicate it with my Thrustmaster Throttle.

To "fix" it i have to switch to crank, to off, to ign and then to norm. The EGT will go down slowly. Or if fast enough after loading not rising at all. I monitor the LVAR "INI_ENG1_EGT" with my Streamdeck so i dont have to switch on the Batterys

I can only guess the cause of this error.

But i can replicate the error if i switch to crank and back to norm. If i do that the EGT shoots up again. 

Maybe this helps :)

Edited Sunday at 04:29 PM by P4RZ1VAL

[Isiattie]

Same here. 2020

[Estray One]

Exact same issue with hot engine 1 on fs2020

[AlexLacolle]

5 hours ago, P4RZ1VAL said:

Hello, i have the same Problem. I can "fix" & replicate it with my Thrustmaster Throttle.

To "fix" it i have to switch to crank, to off, to ign and then to norm. The EGT will go down slowly. Or if fast enough after loading not rising at all. I monitor the LVAR "INI_ENG1_EGT" with my Streamdeck so i dont have to switch on the Batterys

I can only guess the cause of this error.

But i can replicate the error if i switch to crank and back to norm. If i do that the EGT shoots up again. 

Maybe this helps 🙂

It work for me.

[Transair]

yes...also getting temp set as 315 on Eng#1 (first flight - not turnaround).  On cranking, N3, N2 rise, then N1 to 9.5% with no fuel flow + 'COOLING' advice illum.  So I uncranked the engine, start Eng#2, waited for #1 to reduce temp - about 165 worked, then re-started #1.  That seems to work, but agree with others - should be a ready inibuilds fix for it. ( MSFS2020)

Edited yesterday at 12:59 AM by Transair

[LineDX]

Same