>I'm not an owner of any PMDG product, but i'm interested in>them, and i was browsing the forum to gather information about>them (onestly at the moment i'm discouraged by the high price>of the entire series).To quote myself, i just bought them both :)I'm onboard :)

>Alberto:>>ActiveSky in order to simulate the effects of the wake>turbulences, practically places a firm hand on your controls>and stirr them.>It is equal to haveing your stick fully deflected.>Usually this situation is stabilized by you takeing control of>the wheel, and the default FS autopilot is not affected.>But complex autopilots may be (i've seen this happen in other>commercial products) because of other things.>It may be seen as a failure in the command surfaces, and thus>the autop would disconnect, or whatever.I believe the PMDG autopilot disconnects if strong enough control inputs are detected. I think it reverts to CWS mode when this happens. Alberto, when the AP disconnects, does the PFD indicate CWS mode?I discovered this feature one day when I was flying on VATSIM in autopilot mode, and I had my 1 year old daughter on my lap ... she reached out and gave the CH Yoke a good hard pull to the left, and I discovered the aircraft in a nice gradual turn in CWS mode. Luckily I was able to get back on course before ATC called to see why I was deviating. :)

Funny my force feedback joystick sometimes had a mind of it's own and would MOVE my stick (going to neutral I suppose) and would revert me to CWS. So I had to disable force feedback (not that it was that important to me ;-))[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 |

Claudio, thank you very much for your precious indications!!I unchecked the wake turbolence simulation in AS and my problem is solved;Thank you again Alberto

At all, di niente :)Now i've bought the 737 i've also experienced such problems.I believe my initial hypotesis was correct: the pmdg thinks it's a glitch in the command surfaces and disconnets, because the surfaces are stuck in the maximu extent position.Edit:i keep forgetting my name :(Claudio

[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 |