Hi all,I have been having a big problem recently with the MD11. After every flight, as soon as I disengage the autopilot I have no pitch control whatsoever. I am using a Saitek X52. I have read a previous topic on this forum about other users having this problem , but it seems to be unresolved. Has anyone found the solution? I have very limited time to fly the md 11 so it is extremely irritating when this happens after a long flight right before landing. Last week disengaged the autopilot at about 800 feet when on the ILS and I had no pitch. I tried the same flight just now, and I sidengaged the auopilot in cruise to test the problem. No pitch. Roll and yaw were fine. I must add that the keyboard commands for pitch still work which is extremely puzzling. I have tried all the LSAS sensitivity options with no success. When I move the joystick nothing happens to pitch. Also tried disconnecting and reconnecting the joystick!

Full names here please.If keyboard pitch is working then I believe this tells you that the problem is with your controller. I am not familiar with the Saitek, try plugging in a cheap joystick and calibrate it then see if same thing happens or not.

I have had similar issues too. I have not been able to track it down so far, but I am wondering if it is something to do with the fact that I have enabled null zones for the Saitek Pro Flight yoke I have via the calibration interface. I suppose I should remove the null zones and work with FSUIPC directly. I don't remember this happening when I first started using the MD in FSX. Given time, I will report back with my findings. There may be some interaction with the LSAS and the hardware null zones. Andrew Entwistle

Well, I took out the hardware assigned null zones on the joystick axes and had no issue during a 90 minute run gate to gate EGSS - EDDV. A/P disconnected on final approach at 1000'AGL and I had full control of all the axes.Need to carry out some further flight tests to see if this remains to be the case...I have an odd case with the ground lights (taxi/ldg lights) not illuminating the full ground directly ahead of the aircraft (different pattern from the posted issues here...), though this may be to do with a rogue spotlight.bmp... need to check on that one as well...Andrew

Hi all,I have finally tried the same flight again and same problem, I lose all elevator control. This happened on short final (flight KFLL - MGGT) Reading on this forum I tried disengaging LSAS from the overhead panel and I regained control as the elevators responded again. I tried switching it on again and, again, no elevators. I also noticed (another problem reported elsewhere in the other topic relating to the elevators locking up) that my VC displays were not updating properly. Switching to 2D and back to virtual cockpit fixed this. I had no null zones for my Saitex X52. This seems to point to a memory issue. I find this hard to believe though since I have 6 gigs of RAM and a 64 bit system. All this is very frustrating since I upgraded my system specifically to use FSX and the MD11 since I always had CTDs due to insufficient memories on my old system!Regards,Andrea Faggiani

Dan, I had the lock up again yesterday. Keyboard pitch is not active either, as I specifically looked to see. It is definitely not an issue with the yoke.I was coming into Hamburg (Aerosoft scenery) and the displays in the VC stopped responding, although the aircraft was still flying. I had no feedback as to current speed, glideslope and LOC tracking, nothing. Then when the displays started to respond, with AP off, I had no elevator authority until I switched off LSAS on all channels. After landing and rollout, I reconnected LSAS and noticed that I had deflection of the surfaces again on the CONFIG display.I am going to try the flight EDDM - EDDH with reduced scenery complexity and autogen settings to see what happens in EDDH on approach.There has to be some issue with my system here, otherwise more people would have noticed an error here. I just need to find out what the error is.BTW: The spotlight.bmp issue has been sorted. The landing lights illuminate correctly. I just had to reinstate the original FSX spotlight.bmp, REX's seem to screw around with some addons...Andrew

OK, a little update...This time I kicked off the AP further out... The axes responded fine, then I had displays lock up. ATS was active still, and I lost ATS. I was unable to work the thrust levers, and ended up in a thrust lock situation. After around 30 seconds, I managed to regain control of the thrust and Khe Sanh'ed into Hamburg... I hit the tarmac a little hard and probably bounced a little but managed to keep the right way up. I forgot to arm the spoilers in all the hassle, and it seems the autobrakes, although set, did not respond on touchdown... (perhaps a link between spoiler deployment and autobrake... I forget right now)...I am beginning to believe it is a RAM issue, particularly as it occurs when coming into heavier payware loads. EDDH does hit a bit when loading...Maybe things might improve if and when I can build that i7 950 OC with SSD and all that jazz...I can only hope. I need as much time as I can get in the MD11, so as to get the most out of an hour in the full motion sim in Frankfurt...I would be really grateful if someone could do a test for me:EDDM - EDDH (1.5 hours' flight time) with Aerosoft EDDM and EDDH over third party ground environment X with REX2 clouds. I used normal scenery complexity, sparse autogen, REX2 clouds were the 512 sets... I know a little specific, but perhaps there is someone out there on this forum who can help?Andrew

Well, it has happened again.Given the frequency of recently affected flights and the limited time I have in sim these days, I have grounded the MD11X for the minute. I think it is a RAM issue, because the loss of the axis always occurs following the lock up of the displays. We all know the MD11 is not the lightest on resources, and my system is certainly not the fastest around these days...I am sure she will roll out of the hangar anew when I can get a new i7 based system up and running... it is too nice to lose out on...And of course I will want a shiny new system to house the 73NGX when the doors open... :)Andrew

Andrew,I tried the same flight again yesterday, which had given me the problem 3 times in a row. KFLL Fs Dream Team to MGGT Latin VFR, with UTX USA, Real Environment X and Ultra HD REX textures. This time however, I changed the REX textures to 1096, and also set the maximum textureload resolution in the cfg file to this same number using the freeware texture max load editor from frostysoftware. I also reduced the level of detail radius (first setting in scenery tab) to medium form the rightmost setting I had.i had no problems at all on the flight which further points to the RAM problem. Last time when everything went crazy I was using up 3.7 gig of ram, this time I periodically checked it and it was much lower than this, at around 2.2 gigs. I suspect that the problems occurred as the simulator loaded the large amount of photorealisitic scenery near MGGT, and this, combined with the high detail clouds and MD11 made the system short on RAM and I suspect the first symptoms are non responding VC displays and disruptions to the LSAS system.I hope this was the problem as I can definitely do with lower res clouds and scenery to fly the MD11. I will try more flights to detailed sceneries, especially longer ones to see if effectively I have got an improvement, if not like you I will have to change plane!Andrea