I decided to try re-installing the 767 PIC because I was having some problems with the ".air" file.Well, I don't know what exactly happened, but it ain't good!First of all, when I start up FS, and do a "create" flight with the 767 (POSKY), the panel loads up & all, but the Utility Buses won't turn on. I turn the switches on, but the little "off" is still illuminated. They aren't supplying power either, since the trim air & re-circ fans aren't working.The APU doesn't seem to produce enough air pressure to even run the packs, much less start an engine.The "Load a panel" menu doesn't fix this problem.However, I can save the flight, close FS2002, and restart it, and load that flight, and the above problems are fixed...weird.Anyway, then my other problem became apparent as I was taxing. I turned the corner to hold short of the active (using maximum rudder deflection), and the rudder control "stuck"; it wouldn't move out of maximum deflection. It would "flicker" for a second over to where it should be, but then it went back to its maximum deflection. I used the Windows XP joystick control panel to find that the pedals were imputing the correct signal; they were showing neutral. I managed to fix this problem by re-loading the aircraft (in the Select Aircraft menu). I taxied out to the runway, and managed to take-off, but as I was rotating, the elevator controls "stuck" the same way the rudder controls did, so the plane stalled-out. I quickly re-loaded the plane, and tried to turn to the heading the poor VATSIM controller told me to, but then the ailerons & elevators froze, so the plane went into a sideways dive & I disconnected from VATSIM.Any ideas why this happened?

Ben,The rudder "stuck" probably because of the dreaded rudder spiking problem. Use FSUIPC option "eliminate control spiking" with rudder, ailerons and elevator, and you should be fine.WRT to other problems... if you can't start the engines with APU running, then there's something seriously wrong with it. Are you doing it right ?Tero

It sounds exactly like you are using the POSKY AIR and CFG files with the PIC767....You want to get the merge application from Lee Heatherington and the problems you describe will go away.Do a search on this forum, or the file may be on the AVSIM library, I can't say for sure.Rob.

http://www.pic767flyingclub.com/download.htmdownload v3 of the POSKY PIC merge.There is a seperate one for -200 and -300 models of the 767.

I've already done the merge, both with the program & by hand. It also happens in the 757 merge (with Tero's ".air" file).Again- after I save the flight & restart FS it works ok... Maybe something is wrong with my default flight; I'll set it back to the Meigs one (I've changed it to an Archer at my home airport).Tero- thanks for the FSUIPC tip! I'll try it before my next flight.

Ben,looks like you've found the problem. Your new default flight is causing a conflict in PIC's electrics when it is launched. To cure this all you need to do is select a default aircraft then a PIC aircraft. This should solve the problem.