Is your yaw damper on?
Don’t see flexnet. Nothing in spam folder, & same result with two different email addys

Don’t understand yaw damper. Can’t use the mouse in the cockpit.
Yess but it isn’t doing anything the issue started today
The same email address you used to download the airplane will also be able to receive a confirmation email for the forum and for the support page. If the download access got through the rest will get there too.
Has anybody noticed CTD’s when using the PMDG with Aerosoft Simple Traffic? I had my first 737 CTD today, after reinstalling simple traffic.
I don’t want to blame that tool but it does seem the timing is about right…I add things slowly for exactly this reason.
Any thoughts appreciated.
Check your Hydraulic panel and the FLT Control panel on the overhead. All the guards for the flt controls should be closed (Which forces them on), and Engine and Electric hydraulic pumps should be on while in flight. And check the hydraulic fluid level and pressure on the engine display, could be running low.
So I tried the CI you recommended and it silences the warning for 280 at HONKK because the box now is “cruised” at M .70 or 279 kts. If I subsequently am asked to, say, fly faster at “best forward airspeed” now I’m liable to get violated. I tried bumping the speed up to 310 to see what would happen. The airplane will slow to accommodate and comply with the AARCH 280/11000A but it doesn’t give one iota about HONKK. Didn’t slow or attempt to slow for HONKK. Question is why does it care about AARCH but not HONKK. I’ve been told well its a cruise segment, but arguably so is AARCH because it’s positioned before the T/D. So I don’t know what to think here. I don’t believe this is accurate, but I’m not a 73 guy. I’ll just recruise the box prior to the fix I guess, or use speed intervene.
i am new to flying tubes in the sim. i’ve really been enjoying the pmdg 737.
does anyone have any recommendations for some good manuals that go into more depth than what was bundled with the plane? i had a couple of things happen on a flight today and i would like to be able to reference some documentation on what was going on. for example, in the fmc → legs page, there were some speeds and altitudes listed in magenta. not sure what that means and i couldn’t readily find info on it. also, during a manually initiated descent, my speed (on the fms panel) had the number 8 flashing in front of it.
anyhow, these are the kinds of things i’d like to be able to look up so any reference materials you could point me to would be appreciated.
Google for something like “Boeing 737NG FCOM” - there are several PDF versions floating around the web from a couple different sources and operators. There are also a couple of really good web resource sites.
Yess it’s running low what do I have to do?
I think all is running well now thx for the help if something I’ll ask again!
What is the trick to getting AUTOLAND working?
I am VLOC active, press the second CMD button, it lights for a moment then goes off.
I just cannot figure it out. I have watched videos and THINK I am doing what they do. They just press the second CMD and presto, it works for them, but not me.
Maybe a stupid question, but are you established on the glideslope when you press the second CMD?
Edit: And remember to change CRS and ILS frequency on both sides.
two other things to check. first, make sure you’re using the Collins mcp and not the Honeywell. second, I believe you have to have the system configured for fail operational otherwise it won’t work. g/l!
Second autopilot can be engaged only after pushing the APP button. Type of MCP doesn’t matter, autoland works on both. Make sure to have the correct frequency and courses set on both sides.
Speed intervene would be your best bet. I’m starting to get a little lost here since i’m a visual person and i need to have that scenario again in front of me on my own FMC.
Glad it worked out for you. I could be an error with the navdata too, no idea…
I also use Simple Traffic together with PMDG 737 and I haven’t had any CTD with the 737.
I haven’t followed this topic/issue in its entirety. But on average when the FMS communicates ‘unable speed at ***’ or ‘unable next altitude’ it’s based on the VNAV profile of the aircraft and it’s performance such as weight or weather.
So in a different circumstance in takeoff, the aircraft being very heavy, it could say ‘unable 230 knots at -this waypoint’. It’s just a pre calculation of the current VNAV profile based on the FMS settings, weight and engine thrust rating. It doesn’t mean however that you as a pilot can’t override those calculations for instance by disabling derated thrust and manually give it a full burst on the throttle.
Same for a descent profile, waypoints and their limitations can be too close to each other as I suspect could be the case with this casus. If it’s speed or altitude related the FMS will usually follow up during that phase of the flight with a message saying ‘drag required’ to manually assist it in a forced increased descent or deceleration.
Basically, VNAV always tries to make the ride as fluffy as possible. It calculates the vertical profile based on its own independent engine control with regards to ascent and descent, and also for speed control. It’s limited to that as it can’t deploy spoilers itself, but it doesn’t mean you can’t override it and pilot the aircraft yourself. The FMS indicating to you that it’s confronted with limitations is basically a request to either not care too much given your assesment of the situation or to take over manually if you do care and apply spoilers accordingly.
VNAV is there to assist you in a smooth ride according to pre-published procedures in the airspace, but it’s not there to take over your job commanding an aircraft with 140 people on board. Always be ready to step in yourself.
After VLOC/intercepting the localizer your press Approach (below VLOC) to also arm/intercept the glideslope. After APP is armed, Autopilot B can be engaged too. As long as you made sure you also set its course and ils frequencies.