denerin

But as far as I understand it, and from what I can read from the checklist (both 737 and 777) the engine restart checklist comes after selecting the engine start lever to Cutoff. So if you: Fail the engine -> Engine start lever cutoff (as per the checklist) -> clear the failure (the engine of course will not start at this point) -> do the Engine In-flight checklist. This could be a workaround (as I understand it, this is also what is suggested in the FSiPanel forum).

The program should run under WinXP, but, the program is written as a WPF (windows presentation foundation) so you may have to install a newer .net on your XP machine. (sorry, but I don't have XP anymore so I can't test it. I've only tested it with Win 7 and 8.1) Yes, I know that you can't restart the engine as long as it is failed in the FSX meny.. and as soon as you reset it it relights. Of course if you cutoff the fuel control switch it will not relight.. so that's why I added the "Reset failure.." option.. in the checklist "ENG FAIL L, R" step nr 4 is "FUEL CONTROL SWITCH -> CUTOFF"... then you could reset the failure and attempt a restart. I know it's not optimal in any way.. but just tried to do something with it. ^_^

Done. http://library.avsim.net/download.php?DLID=189287 Hope you enjoy ^_^

Sure. I'll have to make it little more "graphically appealing" to share, but give me a few days.

I quickly wrote a little program in C# where you can specify a speed that you want an engine to fail at (communicates via FSUIPC) and it actually works great.

Making it fail at a specific speed shouldn't be that difficult. (One could read the current airspeed via Simconnect or FSUIPC for example.) Have you tried failing the engine in the FSX menu (Aircraft -> failures, engine tab -> Complete failure)? I just tried it and from what I can see that replicates the behavior from the FSiPanel video. (N1 rotation, but no Auto-relight). Hope this helps,

Using the default panel state solved it for me. (I made my own "long panel state" based on the default)

I can confirm that this is the case for me as well.

http://forum.avsim.net/topic/454211-would-random-failures-on-provide-more-realism/ My guess is that this has something to do with it.

Thanks for posting this! I will definitely try it. (heading to the hardware store).

I get the same results as before in the 200LR (British Airways (Fictional) livery (decreased effectiveness on both) . My trim buttons (A1/A2 on the yoke, button 2/3 in FSUIPC) are assigned in FSUIPC to: -Buttons + Switches - Control sent when button pressed - Elev Trip Up/Down

Yes, I am using FSUIPC. I use "Send to FS as normal axis" and I don't calibrate in FSUIPC. I have a Saitek pro flight Yoke, Saitek Pro flight rudders and GoFlight TQ6 throttles. I did the test in 777-300ER, British Airways livery. (If any of these things matter)

I just tried the experiment (post 141), trying to do it as exactly by the instructions as I could, and my results are that the yoke effectiveness decreases in both situations (FBW trim speed extreme above AND below actual speed). Very very strange indeed that your system is doing something completely different!

It's funny nether the less that searching for "GPU" in the 777 introduction manual (which, on my computer anyway, is about 160 pages) will not give you any info relating to the problem. (You'll only find something about GPU memory, which of course is something completely different.). As far as I can tell the manual doesn't say anything about the problem of the GPU still being attached to the aircraft from an outside view even when you have disconnected it. What it does say is: "One shortcoming of all PMDG products for FSX is that our products do not like to be “re-loaded” on top of themselves. This means that if you have one livery or variant of the airplane selected and running within the simulation world (say, a 777F) and you wish to change liveries to a different 777F, you will need to shut down the simulator and then select the new variant or livery you wish to switch to from scratch. If you load a 777 livery or variant on top of itself you will see strange issues in the cockpit, FSX may CTD or otherwise crash etc."

I experienced this some times and the solution for me has always been to let FSX rebuild the fsx.cfg file. (if you delete, or rename it, it will automatically rebuild itself when you start up FSX). Hope this helps.

SAS