Chris_FL

I'm not sure if it was raining or not (I know there was lightning) but that's not the point. The point is the that even 20nm out the game KNEW there was supposed to be rain there. Whether or not it was rendered on my graphics card as rain is irrelevant.

I don't know the first thing about how FSX is coded or how weather is handled, but I know BS when I read it. I'll give you a perfect example of how your explanation makes zero sense: I took off out of KFLL on a bright, sunshiny South Florida afternoon. I was using FSX realtime static weather (no 15 minute updates). I could confirm that it was, in fact, a bright sunshiny day in Fort Lauderdale by looking out my window. When I got to Key West, there was a nasty thunderstorm which I could see from many miles off during approach. A binary system, such as you described, cannot achieve these results. If your theory was correct, then the thunderstorm would have suddenly appeared around me without warning.

If I'm in a rainstorm, moving at 250kts, and the "rain bubble" is following me, FSX has to know where rain is SUPPOSED to be. Even if it's not currently rendered the data had to exist on where rain is supposed to be. Otherwise how does FSX know to draw the "rain bubble" when I enter an area with measurable precipitation?I don't care one way or the other if it's modeled. It'd be great to have but if it isnt feasible for them to work out fine. I'm not the kind of person who beats the burned ashes of a long dead horse in any thread possible. I just don't believe the technical limitations being listed here. The data FSX might contain on that percipitation might be limited and not possible to accurately model weather radar on but there has to be some sort of data on rain within the sim environment beyond my immediate location.

There must be an ILS frequency issue here. The course selection on the MCP reads 86 and the heading on the HSI is 226 (or close to those numbers anyway). DME is not reporting either.

What airport, STAR, runway, and freq?Chris

The APU switch is "On" but the EGT shows 0. I believe I read the APU cannot be started above a certain altitude, perhaps thats what happened here?

Cameron, how much memory does your system have? These are classic low memory symptoms.

I noticed after the Hotfix that the aircraft was spawning with no fuel loaded, giving me a flight deck situation like you described. I loaded 10% fuel into the main tank, and then once loaded into the aircraft configured the fuel mode through the FMC like normal.

In the manual it states that it takes around 10 minutes (as I recall) for the heat to spread and trigger the alarms. It also mentions this is an accurately simulated system of the real aircraft. Mist likely a brake calibration issue. The other issue in this thread about the hydraulic temp issues sound like someone forgot to move the landing gear lever to the middle "Off" position after takeoff.

This is most likely caused by improper calibration of your stick or pressure being applied to the stick when loading the preview model.Try recalibrating or adding some deadzone. The best way to prove this is to unplug your controls and then fire up FSX and the NGX.

Great! I'm glad it helped!

Thanks to a cluttered desk I discovered the cause of this. If my yoke has any pressure on it when the preview model of the NGX is being loaded it will crash. I can replicate this over and over. This also occurs after a flight when coming back to the FSX menu.

I'm sorry, but I'm a total novice here. I put in the departure/arrivals into the DEP ARR screen, then go to Route, and it shows ARKES1 ARKES, which seems right. Then I add "J113 then LLNCH" and then go to Arrivals, choose 36R and then the PBI.BAIRN2 and I get the discontinuity. What is the proper way to enter this? Is the flight plan really not ARKES1 ARKES J113 LLNCH BAIRN2 like Flight Aware says? Thanks for all the help!

This was an issue I was having when I first installed the NGX. I did a clean install and everything was working fine. Today, I came home and tossed my yoke to the side of the desk and took care of some business. I wanted to fire up the NGX and play with the FMC a bit...and the issue came back. After banging my head against the desk for a bit, I saw that there was downward pressure being applied to my yoke. I straightened it out and viola...the NGX loads without any issues. I closed FSX, tried it again and sure enough, worked fine. Then I pushed on the yoke, fired up FSX one more time...and it crashed. Go figure. I saw this thread and what Rafgath posted and wanted to confirm what he says is the truth!

The problem I have with Flight Aware is it doesn't provide enough knowledge for total flight plan novices like me. I'm trying to recreate the SWA2892 flight from KFLL to KMCO. Flight Aware says the route is ARKES1 ARKES J113 LLNCH BAIRNS2. But what runway does it land on? If I plug that into the FMC using the BAIRNS2 36L STAR I get a discontinuity between LLNCH and BAIRNS2. I have no idea what I'm doing wrong.