netshadoe

I bought 3

Please please please!!!!

Gotcha! No problem, just wanted to make sure!!

Actually, that isn't correct. ASN is a direct replacement to AS2012. AS2012 and ASN should not be running together. They are both weather engines and will conflict. The only thing AS2012 has that ASN does not are cloud textures. Once you choose your textures in AS2012, it should then be shut down and ASN should run on its own. The real difference between AS2012 and ASN is how they control weather. AS2012 uses SimConnect exclusively. ASN also uses SimConnect, but it uses the as_btstrp.dll to actively hook into the program itself (much like FSUIPC does) to control weather in different ways SimConnect can not do. This allows, among many things, consistent smooth weather changes...no more popping clouds or sudden shifting winds. * edited because I can't spell!!!

The fire handle on engine 2 is pulled. That would shut down the engine.

That looks really neat! I'll give it a shot.

Make sure "Track up" is NOT selected. The background map doesn't render when this option is selected.

Turbine Duke V2. To the dismay of my wife, ive logged many, many hours in the T-Duke!

Clouds are sprites and they do rotate. That hasn't changed since FS2002. Like Jay said, they are kinda 2.5D...a bunch of 2D sprites placed in a group to make them look 3D, and they rotate to keep that "3D volume" illusion.

Bob, Check out page 40 of the "NGX REBOOT MAIN OPS MANUAL". It will show you how to run the preflight. Without that, the first officer doesn't do any of his setting up, such as walk around, oxygen test, and of course Autobrake to RTO among many other setups. And, it also sequences FS2Crew regarding the FA and Fuel loading, etc.

Ah! I see what you are doing. I was assuming you were starting as a "crew change" or "first flight". I your case, I believe you have to set RTO as part of your preflight (like Bryan mentioned). Either way work, you just have to adjust to the procedure you're using.

The FO should have set the autobrake to RTO during the Preflight (page 14 in the tutorial). The caveat at the top of the page is "TUTORIAL ASSUMES FO WILL DO IT BASED ON DEFAULT CONFIG OPTION" He sets RTO on my setup, so it does work.

I posted on the forum for you Ray. D

You have to acknowledge the push back with the "roger" key ("\") You control GSX like normal. Get ready for pushback like normal (request tug). Use PF3 to request pushback. Once you have permission, release the brakes, and GSX pushes you out. Once your pushback is complete and you're ready to go, call PF3 for taxi.

I'm trying to. I'm waiting on support for flight plan loading. Essentially looks like PFE, but without the cumbersome converting of flightplans PFE had. I'll let you know once the FP problem is sorted out. Probably some kind of formatting error because I use PFPX to generate the plans.

Glad I live in Canada where we don't have that kind of weather!! :LMAO: Seriously, we've had it good for the past few years. All the major storms have been south of us hitting Pennsylvania, New York, Massachusetts (think Boston) and moving on to the Canadian Maritimes. I think we had less that 2 feet of snow last year. Right now, there's only about a foot on the ground at most.

Probably one of the retiring Virgin Atlantic birds. They're all paid for!!

Thanks Justin! I entered my registration too! Welcome back.

There's a whole study on it. Here you go: http://www.southampton.ac.uk/engineering/research/projects/buzz_saw_noise_and_non_linear_acoustics.page

Ask Aerosoft support.

Do you have any active failures? Do you have service based failures on and is there a failure? NGX simulates failures. You can actively set them. Service based failures happen over time. You can even break stuff by not flying the plane properly (there is a thread somewhere around here about someone manually pushing the elevator while the AP was on and broke the AP system that controls the elevator). Did you check to make sure your hardware was not the culprit (a bad controller sends "spikes" to FSX and causes the AP to disengage or not engage at all)? Is your system up to the task of flying the NGX? (Issues have been caused by not enough horsepower) Are you using a 3rd party weather program? (Some cause the S-Turn issue...search for it) Many factors can cause your problem. The NGX has been out for years...I highly doubt it's a bug.

Not really. The 737MAX has bigger engines and a taller landing gear because of those bigger engines, not to mention a new wing.. Along with these major changes come smaller changes. It's a whole new generation, not just a NGX update.

Not so complicated? It takes hundreds of hours just to do the VC. You have to model it in 3D. Gauges have to be created and programmed...do you know how many thousands of lines of code is needed to just run the FMC, let alone the code in the other gauges to work with just the FMC? Then you have the MCP. Then you have systems logic. etc. etc. Then, like you say, the wing has changed. This alters not only flight dynamics such as lift and drag, but other factors like fuel flow, stall speed, how flaps affect the airframe, reaction of the airframe in different phases of flight (takeoff, cruise, approach), etc, etc. Then there are new engines. Again, flight dynamics and fuel usage will be completely different. Sound will be different. Then you have to BETA test for hundreds of hours finding and fixing bugs and tweaking things. Think more in years. It's not a "quick fix". It's not a patch. The 737MAX is a whole new beast. It a new generation of aircraft. It would have to be created from the ground up to be done right by PMDG standards.

That's FSX for you...give and take. Microsoft's weather engine left a lot to be desired! High fidelity aircraft doesn't like FSX's LoFi weather engine. So unfortunately, as it has been mentioned in an answer earlier in this post, you have to turn off FSX turbulence. ASN solves this problem by directly hooking into FSX and bypassing FSX's weather engine completely, thus eliminating the S-Turn problems you are encountering. It's not a PMDG bug...it's an FSX bug. Setting the autobrake is part of the "BEFORE DESCENT CHECKLIST", so it happens in Cruise before descent....long before finals.

Mine doesn't do that. When I'm at max GW, the NGX just sits there at idle. I need about 31-32% N1 to get moving and small blips of power to keep moving. At low GW, once I'm rolling, it keeps rolling at idle power. Are you using the DynamicFriction.lua file included with FSUIPC? Is PatchSim1friction off (or not present) in your FSUIPC.ini (Both can't run together) Other than that, you can play with the friction co-efficients to get them to suit your needs. (I have no experience in this. Sorry).