Issues with LEvel D 767?

allegro · Post by **allegro** » Tue Dec 05, 2006 1:18 am

Are there any known issues with the Level D 767 and FlyNET? I'm having a weird problem where the autopilot won't stay on whenever I'm trying to do a "real" flight, but works fine when I'm just messing about, and about the only thing I can think of that's different is that I run the FlyNET client when I'm trying to do a real flight and don't when I'm not. I didn't see anything searching on the forums, and I can't believe nobody else is trying to fly this bird w/FlyNET considering how popular it is, but I thought I'd post anyway. Anybody hear anything about this?

I have a post up at the LevelD forums as well...

allegro · Post by **allegro** » Tue Dec 05, 2006 1:24 am

Hmm... just replicated my last flight as closely as I could, except w/o flynet client, and everything is working..

allegro · Post by **allegro** » Thu Dec 07, 2006 2:27 am

Some more data...

I have this exact same problem whether I am using FSInn or Squawkbox, and it ONLY happens when FlyNET is running. If I am not online, I do not have this problem. I don't have this problem in any other aircraft.

Truly clueless

CAPFlyer · Post by **CAPFlyer** » Thu Dec 07, 2006 4:26 am

Are you starting the VATSIM programs and signing onto the network before starting FlyNET or after?

allegro · Post by **allegro** » Thu Dec 07, 2006 4:28 am

I think, sir, you may be onto something... I'm not sure which I have been doing. Is there one that is known/suspected to work better?

CAPFlyer · Post by **CAPFlyer** » Thu Dec 07, 2006 4:36 am

Once you start FlyNET several sections of Flightsim become locked out, including access to the mutiplayer functions and the "Aircraft" menu among other things. If you don't have everything setup and running before starting FlyNET, there have been several reports of issues that result from those functions being blocked out. I have a feeling that you are encountering this problem and that when SB or FSINN have their functions blocked by FlyNET (actually, its FSUIPC doing the work) they cause a log-jam that then turns in the result you're seeing as I have a feeling that the Level-D 767's autopilot is dependent on FSUIPC to function correctly and the logjam that is occuring is preventing this from happening. Try starting FlyNET last after you've signed on and just before calling for push and start (I typically sign on about 15-20 before departure to get my clearances and final information so this gives time for the airplane to be "fueled" after I start FlyNET and set my fuel). See if this fixes your problem.