I have still that problem with both 767 PIC and the PIC Posky 767s. When I fly at cruise level and speed up the simulation to 2x or 4x I get some terrific pitch oscillations, altitude varying between +/- 200 feet, the aircraft continues flying but I get sick :-( I use the newest FSUICP, turbulences and gusts disabled, peak elimination for rudder/ailerons/elevators activated, slow pressure changes. The problem occurs both when flying with the MS default weather or using ActiveSky.I have not that much time for my flying that I can whatch the aircraft crossing the North Atlantic in 7 hours, so every help to my problem would be much appreciated!(somebody was talking about new FDEs, whould this help and where can I download them?)Andreas (EDDH)

Hello, You will find that PIC was designed by an airline pilot, and a few others to mention. It was designed to be the most realistic aircraft simulation avaliable, and is. Since you cannot time warp a 767 across the ocean in real life you cannot here, You are pilot in command, so choose to fly shorter routes or sit it out. Sorry.Don Harrison

I principally agree with you, Don, that real time is the best way to fly this aircraft ;) . Nevertheless, when I had her installed on my older computer with FS2002 on Windows 2000, I did never had that problem. In addition, Wilco stated with their patch, that operation in time compressed mode whould become possible.I remember also, that there are other flightsimmers who like to do rather long haul flights with that beautyful aircraft and stick to at least 2x compression mode to shorten the time over water somewhat.Additionally I may mention that I have never seen these pitch oscillations with any other add-on as PSS 747/777/A3xx or Dreamfleet 737, which imo also can be considered as high end add-ons...So, if anybody could give me a hint how to solve the problem it will be much appreciated.

If I remember correctly, the PSS and DF series all have FS2002 autopilots, with a little bit of eyecandy to make them look different. The FS2002 autopilots were designed for up to 16x time compression. The PIC autopilot was designed for (at best) 2x time compression. The patch says you can do it, but the speedometer in your car also probably says you can go 120 miles per hour ;) . Just like driving your car 120 mph, you can probably do it, but adding time compression to PIC is taking your life into your own hands. Later,Neil

>So, if anybody could give me a hint how to solve the problem >it will be much appreciated. Doc, it hurts when I do this.Don't do that.DSCVA3339

For some weeks ago, there was a threat in this forum about exactly the same problem with about 25 replies, at last newer FDEs were mentioned.I couln

I've had this problem and have a fix for it!Solution - When you set 2x or 4x sim rate, reduce your target frame rate until the oscillations stop/reduce signficantly. When you go back to 1x, crank the target frame rate back up to whatever it was!Explanation - 767 PIC uses its own autopilot which likes to have regular and timely access to the CPU. 2x / 4x sim rate upsets this balance, thus causing the "hunting" that you are experiencing. Reducing the target frame rate improves CPU availability for the autopilot, since the CPU is not concentrating so much on drawing your pretty picture as many times a second. Visual impact is minimal, since you are likely to introduce blurry textures with higher sim rates, and reduced frame rate minimises, but unfortunately doesn't eliminate, this too.15fps target frame rate at 4x time accel was the sweet spot on my 1.4G Athlon, GF3 Ti200, 512M SDR machine. Haven't tried it on my new P4 2.7G rig yet.Gary

Thanks Gary, I will try this tonight. My target framerate is set to 30 at the present. I have a P4 1,8G, 512 RAM, nVidia DDR 64 mb machine. So, I hope, the effect will be quite similar...cheers