The one thing I have in common with all my engine failures is that I changed the styles of the glass cockpit AFTER I started the engines. If I start engines and change from the "777" style to the "T-Stack" style engines will fail. Changing the reverse way will also cause engines to fail. Changing the styles before engine start does not cause the engine failure.I am careful to do everything else exactly the same way everytime.Whenever I leave the styles alone, I can takeoff with no problems.So far, I've reproduced this 8 times already, in the 700, 800 and 900. Also happens at any airport I try. I have mostly the stock airports with UT afcads (I have UT installed).I'm not saying that is the reason for the engine failures.....it may well be something to do with my FS setup. However it is something to consider. Hope this bug gets found and solved soon.

What is your default startup scenario? Which aircraft is deafult in this scenario and in what state is it?I've changed the DU layouts a lot of times during beta testing and afterwards and never had a V1 failure after changing. Actually I've never had a V1 engine failure. So there got to be something else triggering it.Thanks,

I guess we are somehow lucky Mats?? Why o why do I not have engine failuers? I do not have anything special going on and certainly switch the displays around. I wonder if you guys with the issue can pick a LONG rwy and not touch your controls or TO, just let the bird go down the rwy IN TOGA as far as it can and see if you get the engine failuers still....[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/forum/betaimg.jpgAMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | WD SATA 80 GIG | 512 DDR 400 |

Well, I am enjoying the airplane immensely. I have only had 4 engine failures so far (not counting the times I've been able to make it happen deliberately). Hopefully I won't have any more cause I now know how to prevent it...on MY system at least (take a baseball bat to wood not just "knock on wood").As for the long runway test...will do that tomorrow. Right now I'm happily cruising along at FL350 on my way to KMSY. Life is sweet.BTW, to answer Mats question: I always start from my saved situation which consists of the default cessna at KSEA with engines off, avionics off and batteries off. I then choose my aircraft, airport, time, and PMDG variant, then click "Fly Now".

Anthony-email me privately, pls: lefteris (at) precisionmanuals.comThanks,Lefteris

glad you got it figured out for your box. I still will have the dreaded V1 cut (always the no. 1 engine) about 30-40% of the time. I actually assume it will happen now and I just fly off and restart the engine inflight. Which will immediately fail when reversers are selected at landing, which again I restart to taxi. I have gotten really good at the single engine ops.Personally, I cant force a repeat (wish I could). However, I can say this, it seems to have started when I changed my default setup to the PMDG 'cold and dark'. Why? well when I was using my KSEA MS default (out of the box default), the PMDG engines would be running on plane switch.Ok, shut down the engines on the KSEA default, save as new default with the PMDG and it will load up with the engines spooling down. I got a gut feeling its in the way things are loading.I will be switching startups over the next few days to see what happens. BTW, both the MS and PMDG failures all show blank, however, this is weird - if I continue with another flight after a flight with this engine shutdown thing, the next takeoff, engine 1 WILL fail - but this time FS failure will indicate an electrical failure (blank on the PMDG side of things).I have been tracking this stuff for about a week now (about 25 flights). Never sent a note because I cant reproduce it - therefore I cant really help, sorry. If I get anywhere I will post up.

>>>>>>>>>Anthony-email me privately, pls: lefteris (at) precisionmanuals.comThanks,LefterisLefteris KalamarasPrecision Manuals Development Group<<<<<<

For any bug, problem, that seems to be nonsense, try deleting your fs9.cfg file for once, and run the game again. When it is loaded up, quit, and let the program rewrite a default fs9.cfg.After you reload your sim, many problems are solved concerning the 800/900 update, i.e. engine failures, unwanted crashes, systems not functioning as stated. I do not know how, but it just worked for me, no problems at all, no matter how hard I try to bring it down.Hope it helps,Cheers,

Anthony-yes, something's spelled incorrectly... (I should know better than to post so late at night).It's lkalamaras (at) precisionmanuals.comDuh. :-)

Done

Hey guysThis is a real long shot but what about the "V1" sound that gets played at V1. Could playing the sound on some systems be somehow causing the engine cuts. Is there a common thread with the types of sound card being used.Could you try setting V1 speeds manually with the knob on the panel as per Timothy's tutorial lesson 1 and see if you still get the cuts?I would not have thought this a possibility but after reading about the radio problems and the virtual cockpit I though it may be worth a try.hope it helps, NickPS never had an engine cut at V1, fly 737-600 mostly.