Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

airhub

Members
  • Joined

  • Last visited

  1. A Short Term 'Dirty' Fix: Not ideal but at least can get fly again: Firstly thankyou all for your kind replys. @twinturbo99 - I checked and everything appeared to be off/not active under failures but I'll have to spend some more checking it out. It's v.useful to know about so thankyou for pointing me in that direction, it helped me find the temp. fix :) @RYR738 - thankyou too for pointing those out. I made the changes but unfortunately they didn't solve my particular issue. The 'Dirty' fix that has at least allowed me to engage the A/P on my first tests and therefore continue my flight. (Need to test more to see how it fully works): 1) goto FMC -> Menu -> PMDG SETUP2) select AIRCRAFT3) select EQUIPMENT4) select REALISTIC AP ENGAGEMENT to OFF (was set to on)5) enjoy your flight :) It's not an ideal solution but at least I can hopefully enjoy a few flights before going back to try and figure out what's really going on.My hunch is something to do with the controls as @Gerardius kindly pointed out. I'm using just mouse and keyboard with autorudder -> OFF.I'll have to do some test flights and use the SYS display to check actual flight surface positions. @badderjet - maybe this might help if you want to remove the stress of spending time setting up only for your flight to be ruined :| Again thankyou to everyone for your assistance. I hope this thread maybe of help to you if your face this or a similar issue. If I find the real cause I'll post back whenever that may be. Happy Flying to you!
  2. @Henri Tried reloading aircraft and got a Crash To Desktop :( Never mind, thankyou for the suggestion anyway :)
  3. Pls find some screenshots below: have departed EDDK, VNAV and LNAV are armed, aircraft is ~15000ft and leveling off to make sure trim is set correctly - from around 1500ft AGL to this point I've tried engaging either CMD-A or CMD-B but the button just depresses with no autopilot engagement. I tried at several phases in the flight up to this point with no engagement of AP. (Weather set at fair weather (so little/no wind) - clouds by REX) Many thanks some more screenshots:There are a couple more but won't upload...bear with mesome FMS screens at same point in time (failed to engage any autopilot)Apologies for the duplicate images the uploader doesn't seem to like any images >1Mb
  4. Hi George, thanks. I'll try it again in a bit and post the screen shots. many thanks
  5. Hi Henri, Thanks for your suggestion I'll try it out. It's a weird issue since i tried it in fair weather several times to avoid any crazy inputs and for perfect trim, but no joy! Hope I don't have to resort to reinstalling everything :( Thanks for your help.
  6. Hi, Not sure if i'm posting in the right place so forgive me if i'm not: My issue: After my first few flights in the excellent NGX my autopilot stopped engaging. I tried everything, making sure both flight directors were on, making sure aircraft was trimmed with no control inputs, cycling a/p on and off but no joy! So I re-installed fsuipc4, no change! I re-installed NGX and bingo...it started working again! Now after 3/4 flights it won't engage at all again. I've tried the exact same flights with when it was working, with fair weather, light load, balanaced trim...but no joy! Has anyone else experienced this? Can anyone tell me what might be wrong? Any help would be appreciated as this is killing the experience for me. [ps I have a v.modest system but I've managed to get an acceptable balance of settings that make successful flight v.enjoyable...thankyou PMDG + testers!] Many thanks,
  7. ==============================QUICK UPDATE and some more understanding==============================OK, after some more testing I have come to the following conclusions:1) The default 737 Autopilot or any aircraft aliased to it's VC appears to be sensitive to ELEVATOR POSITION at the time the AP is disengaged. This would explain my nose-down pitching on first disengage of the autopilot as I would have been pushing the nose down to begin acceleration for flap retraction before first engaging the autopilot. Not touching the yoke again till disengaging the autopilot meant that at autopilot disengage the aircraft appears to take this as a pitch-down command rather than leaving the controls/flight surfaces at the last position the AP had commanded. Why my centering the controls(by keying num5) didn't work!?It would appear num5 only centers the ailerons and NOT the elevators thus only centering the controls in the roll axis. I don't have rudder pedals so I can't test this for yaw :( ! So my efforts to center the controls before disengaging the AP were ok for rolling but USELESS for pitch!...hence that didn't help.2) The nose-up pitch on Engaging the AP would appear to be due to having the ALT HOLD button selected when engaging the AP. From what I've tried so far it's OK to select SPEED/HDG HOLD/NAVLOC before engaing the AP and then selecting ALT HOLD after the AP is engaged. I need to test this more.These seem to be some peculiarities in the default 737. Apologies again for those who fly these regularly if this is old news but I've got used to more realistic flight logic and this really threw me. At least I can continue and enjoy my Posky merge with this knowledge...Before I hit Google again, can anyone reccomend any utils for FSX that show control control surface position in flight?Many thanks and Happy Flying folks!
  8. =====================================QUICK UPDATE=====================================Firstly thankyou for your kind replies.A temporary fix/solution: disconnect autopilot in level flight, correct the immediate nose-down pitch on AP disengage and re-engage AP whilst pulling nose-up. This seems to take care of the nose down pitching earlier, likewise, doing the same early on approach and hand flying down. However,it doesn't get to the root cause of why I'm getting this pitch down attitude on AP disconnect. Conversely, I get a nose-up pitch of some 3000 fpm on first ENGAGING the autopilot. This can be reduced by making sure there is a speed set in the V/S window on the MCP prior to engaging the AP (I currently have use_no_default_pitch = 1 in the aircraft.cfg but will also try setting a default pitch mode and see if that changes anything)@413X3 Thankyou, I got all mixed up :( !@Brett_Henderson Thankyou you're absolutely right. Tightening up approach speed/flap settings certainly make for better approaches and landings but unfortunetly it doesn't stop this odd pitching behaviour in my case.@WarpD Not in this case. Using keyboard and mouse as yoke. Elevator trim down assigned to keypad (num7) + Elevator trim up assigned to keypad (num5)@rabid_david Thanks for the suggestion but I have an unregistered copy of FSUIPC so I don't think I can access that option.The quest continues. Just to reiterate the problem is a sudden nose down pitch on disengaging the AP and a sudden nose-up pitch on engaing the AP. Also it would appear that this only happens the first time AP is engaged and disengaged. But I would have to test that further before I could say for sure.Apologies if this is old hat or known issue but before re-installing I was mostly flying Carenado Cherokee and Captain Sim 757. It's been a long while since I flew default aircraft or Posky. Maybe this is why I stayed away from them? :( Happy Flying! Tomorrow's a new day...========================================CORRECTION=======================================:(WarpD Elevator trim down assigned to keypad (num7) + Elevator trim up assigned to keypad (num1)
  9. =====================================QUICK UPDATE=====================================Forced FSX to reload fsx.cfg by renaming fsx.cfg to fsx.cfg.oldTried my test flight in default Airbus A321 and aircraft behaved normally...NO NOSEDIVE ON AUTOPILOT DISENGAGE and nice smooth landing. Tried again in default 737 and same problem persisting :( .Will retry Airbus tomorrow to make sure it wasn't a fluke (or self-delusion :( )...will also try Qualitywings 757-200 and -300 and see what happens.At this stage it would appear that this problem is only with default 738 or 737 models aliased to default 738 !?By the looks of things this might also turn out to be a one-man thread :( . Good night for now!Happy Flying!
  10. Hi Paul, thanks for the reply and warm welcome! I'm centering the controls (Num5) to test whether it might have been some control position issue. It would appear this had no effect whatsoever. On disengaging the AP the nose takes a steep dive and it would appear that somehow the trim is going all the way to full nose-down on disengaging the AP.
  11. Greetings fellow aviation lovers! This is my first post so please excuse any noob mistakes/lack of etiquette.I'm using FSX SP2 in Win XP SP3 and recently re-installed FSX onto a new dedicated 640mb SataII drive with 64mb cache. Everything appears fine except for some odd flight characteristics. My main problem/key frustration:Flying the default 737 and posky 737-600/737-700 (both aliased to default 738 Virtual Cockpit), they fly very well with and without aircraft.cfg tweaks EXCEPT for landing. When on short finals using localizer/glidescope with autopilot in APP mode, the aircraft fly the glidepath as intended. At around 500 feet AGL I disconnect the autothrottle and at just above 200 feet AGL I disconnect the autopilot and this is where my problem is!Just after I disengage the AP i get a sudden and pronounced nose down attitude which can only be recovered from with a huge input of pull-back on the control-column! The result is either a very firm '3-point' touchdown or 'porpoising' either of which is very frustrating and takes away from the whole simming experience. I believe on disengaging the AP the aircraft should be trimmed correctly at the current attitude so this is really killing my experience.Before you ask, the aircraft is lightly loaded,well-balanced and take-off with correct trim/power-settings are pretty smooth!I read somewhere that the FSX default AP returns the control surface (or at least ailerons) to the last position BEFORE the AP is engaged. So I tried engaging AP at around 1000 feet after takeoff whilst commanding nose-up. I then centred the controls on finals before disengaging the AP...no joy! Nose pitched down on finals.So I tried centering the controls using Numpad-5 after take-off and then engaging AP. I again centred the controls on finals before disengaging the AP...no joy! Nose pitched down on finals.After googling for some time I found the following post where one poster states So I take off again on my testing flight as above with each of the above aircraft. After establishing on localizer and glidescope, aircraft configured with good speed I check the trim and it's within the green band. I center the controls and disengage autothrottle...no problem everything is looking good! I disengage the AP and the nose dives. I manage to recover and get on the ground.At the end of the runway I pause the sim and take a look at my throttle quadrant/pedestal.To my dismay ( and great horror) I see that my pitch has gone from within the green band to right up against the stop somewhere around 0.1!!!What I'd like to know:1) Has anyone experienced this and can you shed any light on this?2) Is there a solution to this problem (other than massive control inputs so close to the ground!)3) I'm using keyboard and mouse NOT a joystick...could this be the problem even though hand-flying is perfectly fine.I'm stumped on this one and could sure use some help. Many thanks.(I haven't tried any other AP controlled aircraft as yet but will try once I overcome my frustration with this :( )

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.