reported Right LEF Stuck

[MstrCmdr]

This has only happened twice but after a shutdown, rearm, refuel, restart, and takeoff the right LEF shows a scheduled depression (not the sad kind) on up to 400IAS (the picture below) way after the left LEF is retracted. This causes a right lean during flight. I tried FCS reset and an in-air bit test which doesn't work obviously but I tried it. I slowed down to 135, deployed flaps and gear and looked to see the right wing the LEF was not physically (physically simulated?) in a downward -24degs. The wing looked flat when I sped up as well even though the FCS page showed depression.

Edited June 3, 2018 by Mstr&Cmdr

[luknets]

I've just had similar issue with right LEF.

Had to do front tire repairs. Shut down engines, requested repairs. and after startup right LEF was stuck. Have track file but it's 250MB.

 

Flaps:

Left LEF works OK.

Right LEF stuck.

 

FCS Page:

Left LEF shows 12

Right LEF shows changing values.

 

This behaves as if during repair the "technicians" crossed the position sensors wires for the flaps ;)

[Tholozor]

Possibly related to: https://forums.eagle.ru/showthread.php?t=272711

Check if MC2 shows NOT RDY on the BIT page.

[Hollister56]

I've been having this same issue, land on the SC, taxi to parking, do a complete shutdown.  Start back up, preflight checks, and do the FCS check and I get the same indications as the OP.  Happens every time.

Is there a reason for this or a solution?  

I sure would like to know what the problem is or if I'm doing something wrong?

Anyone else had/have this issue?

Edited October 4, 2024 by Hollister56
Picture Added

[Kah0tika]

Hello,

Whenever I restart the engine 2 the left slat remains partially extended when going back to Flaps auto.
The left slat remains partially extended although it shows the Right being partially extended on the FCS page.
As soon as the engine 2 is shut down the issue goes away.

This must be a bug.

Here's a video I've made to illustrate the issue:

 

 

Edited October 5, 2024 by Kah0tika

[Tholozor]

This has been reported earlier: 

 

 

[Kah0tika]

So it's been a bug for more than 6 years.
Great.

[Hollister56]

Okay thanks.   I like to land on the carrier, shutdown and then re-start and go for another launch, but for now I will just re-spawn until it is fixed.

[MAXsenna]

Title says missing track file. Some of you might want to produce one, perhaps?

[Kah0tika]

12 hours ago, MAXsenna said:

Title says missing track file. Some of you might want to produce one, perhaps?

Just spawn the jet with engine running.
Shut it down and restart to reproduce.
But here goes a track file anyway.

 

LEF Bug.trkLEF Bug.trk

Edited October 6, 2024 by Kah0tika

[MAXsenna]

Who needs a track file?
Just spawn the jet with engine running.
Shut it down and restart to reproduce.

Ah, didn't know that. Read a post above about this happening after landing on the boat. Oh, well. People are asking for TF radar...

Sent from my SM-A536B using Tapatalk

[Kah0tika]

It's just a FCS bug linked to engine 2 restart. Also the indications are wrong on FSC page as it shows LEF 0 and 12 while it's actually the opposite.
I like new features too but basic a/c systems should be a priority in order to take this sim seriously.

Edited October 6, 2024 by Kah0tika

[Hollister56]

It appears to happen after shutdown and then restarting, easy to reproduce and for me it happens every time.

It's anyone's guess to why this is happening?

The first cold start the FCS BITE test works as it should, after shutting down and attempting a second cold start it happens.

[MAXsenna]

It's just a FCS bug linked to engine 2 restart. Also the indications are wrong on FSC page as it shows LEF 0 and 12 while it's actually the opposite.
I like new features too but basic a/c systems should be a priority in order to take this sim seriously.

I agree! And that's what I meant.

Sent from my SM-A536B using Tapatalk

[Hollister56]

10 hours ago, Kah0tika said:

It's just a FCS bug linked to engine 2 restart. Also the indications are wrong on FSC page as it shows LEF 0 and 12 while it's actually the opposite.
I like new features too but basic a/c systems should be a priority in order to take this sim seriously.

 

This is an old thread and I am surprised it hasn't been fixed yet.  Who knows, maybe ED isn't aware of the issue?

Edited October 6, 2024 by Hollister56

[G21pilot]

I'm having this problem. any word on an anwer?

 

[ssn]

Minimal reproduction I found:

• start right then left
• reset fcs (necessary)
• flaps up (necessary)
• shutdown right then left (necessary)
• start right then left

Leading edge flaps are asymmetric, FCS BIT won't pass.

If either: flaps are down during shutdown or left engine is shutdown first or SVs are crossed out during shutdown the FCS will be ok.

Some tracks w/o mods, on Caucasus buit-in instant mission to support above & debugging attached.

Hope this helps to put this 6yo bug to rest. @BIGNEWY

f18-rl-fup-norst-fdown-rl-rl-ok.trk f18-rl-rst-fup-fdown-rl-rl-ok.trk f18-rl-rst-fup-lr-rl-ok.trk f18-rl-rst-fup-rl-rl-asymmetric-lef.trk

[Kah0tika]

As far as I'm aware it wont happen if you start from a cold A/C.
Otherwise every time you have to shutdown in order to repair, you're done. LEF stuck.

It's crazy that nobody at ED is looking here and doing something to fix this.

[Kah0tika]

It's been reported 7 years ago and it's still not fixed.

[BIGNEWY]

Hi, 

I will remind the team, but currently it is a lower priority issue. 

thank you 

[Kah0tika]

Not only this bug has not been fixed for 7 years but also with the last update it got worse as now trying to restart a "hot" plane will generate the LEF bug compared to before where it would only happen if you'd try to restart a cold aircraft....
This is really irritating.
 

[BIGNEWY]

5 hours ago, Kah0tika said:

Not only this bug has not been fixed for 7 years but also with the last update it got worse as now trying to restart a "hot" plane will generate the LEF bug compared to before where it would only happen if you'd try to restart a cold aircraft....
This is really irritating.
 

As mentioned above its a low priority issue, I will remind the team however