metro_fox

Congrats KR...well-deserved buddy!

Try disabling in the scenery library all scenery you won't be using for the particular flight and see how it loads.

According to 737 FCTM for landing without autothrottle, you maintain any gust correction to touchdown, but bleed off the headwind correction approaching touchdown (pg 1.18)

The FCTM method calls for adding to Vref one half of the headwind component, plus the total gust differential. Rule of thumb from the FCTM... "One half of the reported steady headwind component can be estimated by using 50% for a direct headwind, 35% for a 45° crosswind, zero for a direct crosswind and interpolation in between." (pg 1.17) Referring to your example, with the wind offset by 60 degrees, one-half of the headwind component could be estimated with the rule of thumb at around 25% of the total wind...25% of 24 knots is 6 knots, so that is the additive they use.

It's just the sound of rushing air...I don't see why it would sound differently coming through the recirc fan versus straight from the packs. Of course the volume varies with the flow BTW I had CAB/UTIL off in a panel state which is why I wasn't hearing them in the -800.

FMC "Startup State" --> "NGX CLDDRK"

IIRC someone else fixed this by installing/reinstalling their FSUIPC...

Looking at YUL in PFPX...it doesn't appear a J596 crosses YUL. There is a J566 at YUL however...could it be a typo? If it really says J596 YUL then it could be your FSBuild navdata is out of date.

Check your controls for calibration or spiking... maybe its sending some erroneous pitch up input Are you sure you're calculating your V speeds properly? Depending on the variant, the TOW and other factors, 120 KIAS is a perfectly valid Vr...

FCOM Vol.1 provides all the flows under the Normal Procedures chapter, and is of course 100% real-world.

I can hear it distinctly in the -700, but not the -800. Maybe since the -700 only has one recirc fan, the load on it is greater and thus it's more audible from the flight deck?

You could ignore it, just keep in mind if you fly online through VATSIM/IVAO, or even if you use current charts, you will need current data.

I had this problem when I tried the disablepreload=1 "tweak". It would often hang at 6% and then continue loading several minutes later. Check your fsx.cfg.

Yes, Navigraph and Aerosoft NavDataPro are the two choices.

737 deliveries out of KBFI. For example, Norwegian flies their new birds nonstop BFI-Oslo...9 hours.

I have Global, Vector, and will be adding openLC. As KR said, very much worth it. Overhauls the entire planet. OpenLC promises to solve the repeating texture patterns visible at altitude. This has always been one of my "pet peeves" with MSFS...cruising over the Midwest USA and other areas has always looked so horrendous. There is a high-altitude preview at the Orbx forum that show the difference with and without OpenLC, and it appears to deliver.

EDIT: disregard

Pretty sure I read on the DD forums that there would be options for individual airport purchases. I don't see any yet though. Hopefully they add this, as I'm really only interested in EWR, LGA and TEB. EDIT: Found the post. Sure enough, Stanislaw of DD said that options for separate airports will be coming a few days after initial release.

PMDG "NGX" line. No question about it. By far the best 737 sim for FSX, and quite possibly the top-selling addon airliner of all time.

I also have the severe FPS loss and ground flickering. Using FSDT KLAX, FTX Global/Vector. Not using Megascenery or UTX. On my system the scenery uses about 700mb more VAS than default, which is probably normal.

Z key will only toggle the AP on and off. You need to assign the key command to the A/P Disconnect within the NGX FMC options.

^^ Looking good, thanks!

Very nice, Shez... looking forward to the release! How's KRIC coming along?

Yup it's just a line you add to your fsx.cfg. Google HIGHMEMFIX for how to apply it. It won't help the OOM issue but it helps other problems with FSX memory management. It's basically the one "tweak" you can't do without. Another thing you can do is install the app Process Explorer from microsoft, it will let you monitor FSX's VAS (virtual address space) usage so you can see when your approaching the limit. You can also use it to see how particular addons, slider adjustments, graphics settings, scenery, etc effects the VAS size, to learn how best to stay below the limit with your system.

You are encountering the infamous OOM error (out of memory). The chimes are a feature of FSUIPC to warn of an impending OOM. You can search the forums for endless discussions of the issue, but basically the problem is that FSX has a hard-coded limit of 4gb of virtual memory, and will CTD when that load is reached. There's no way around it...only solution is to keep under 4gb by making tradeoffs between reducing sliders, deactivating scenery, etc. Also, make sure you have the HIGHMEMFIX tweak in your fsx.cfg.