Hi,referring to this older thread http://forums.avsim.net/dcboard.php?az=sho..._id=1768&page=5I wanted to remind everyone about something.I found out the hard way on a throroughly planned VATSIM flight from a fully staffed airport (now that's a rare one!) that attempting thru flights can cause both the 767 and FS2Crew to go out of whack and ruin your fun :-( What I failed to realize is that I had previously saved a situation at the gate after a flight and then used that saved situation to start off on my flight today.Things started to go wrong right from the FO flows. He moved the IRS switches all the way to ATT instead of NAV. I had to correct it and manually enter the position intu CDU. Then during pushback the FO would not start his engine start flow. I had to complete engine start + after start flows manually. Utility buses stayed off no matter what I do.However I still didn't smell something was burning. Taxi out for takeoff the FO does his talking but on climbout LNAV, VNAV or AP will not engage, the transponder will not squawk and I have to abort the flight. What a disappointment.I try the whole thing again offline with the same result. Only after creating a new flight things go as they should.Don't be like me, create new flights instead.

Hi Kyle,I'd have to look at the 767 SDK again, but I seem to recall (and this going back), that the position of the IRS switches was one of the few things that I could not read.Saved flights: Saved flights have historically always been dicey, hit-and-miss, with the complex add-ons.You're right: It's always best to start fresh.Cheers,Byran

Oh, by the way, I noticed someone had exactly the same problems earlier: http://forums.avsim.net/dcboard.php?az=sho..._id=1780&page=5..with the N1, LNAV, VNAV and AP problems and all. At least I can now positively confirm it was caused by a faulty panel state from a previous flight.

Hi Kyle,I'm glad you identified that.I hope it will help other users, too.Cheers,Bryan