Paul Deemer

I think you guys are making this a little more complicated than it needs to be. When descending I always set the Altimeter after passing 18,000 feet unless I am in Europe somewhere where the transition is 6,000 feet? When using Activesky and Xgauge in the Cockpit its easy to see what the altimeter is at your arrival airport. Soon as you pass the trans altitude set the altimeter to the correct setting.Even if your at a level above your Trans altitude and given permission to descend to a level below it I would wait until the trans level before resetting the altimeter that way you never forget to do so. There is always something that could happen that could cause you to have to level off before the trans altitude and then maybe you forget to set it back to standard. If you always wait until the trans altitude your reflexes will kick in at the appropriate time by habit. This makes the most sense to me. If you randomly change procedures and mix them up your more likely to forget something.

One other thing to consider if this ever happens again. Same thing happened to me one time when I had a corrupted install of FS Dreamteam KLAX. I know it was FSDT cause it happened right after I installed the Demo. The solution was uninstall FSDT KLAX Demo and the Stand Alone addon on manager. Then reinstall the very latest FSDT Stand Alone Addon Manager. That fixed it. Later on I purchased the full version of KLAX and never had any further issues after that. The only other time I had that kind of issue was related to uninstalling Shader 3.0 and fixing that issue was much more complicated.

One important thing you guys are leaving out when talking about your FPS. Whether or not your using the Virtual Cockpit or Not. The difference in FPS between Virtual Cockpit and 2D-Panel is Huge!

What would the Chocks have to do with the Engines Thrust?

Write it off as corrupt panel state has happend to me twice before and then was fine the next time.

You can do close to Full Fuel and Pax if you do the following with the 737-800Pax - 162Fuel - 43,000 lbs ( 3,000 lbs less than max fuel)Cargo - 12,000 lbs (Allows each pax 74 lbs in luggage)At this configuration I can get roughly 7 hours + reserve.

One difference between SP1b and SP1c is that Visual C++ 2010 is now required. Did you run the NGX installer as administrator and allow it to do a complete install? After you installed it and loaded up the plane did you say yes to all the FSX prompts?

If they get enough support tickets and information and can track down what is causing it they will probably release a hotfix to resolve the issue. In the meantime you could always upgrade to FSUIPC 4.8 like I did and see if that solves the problem. Will let you know the results of my NGX test flight from PHOG to KLAX after I do it later today.

Depending on how fast or slow your computer is will determine for how many seconds the freeze is. Most likely reason your having this freeze is because of FSUIPC Autosave. With the 747-400 and MD-11 the saves are not even noticable but with the NGX it takes awhile. Example on my system I have FSUIPC set to save twice an hour. When it starts saving it takes about 3-4 seconds to resume again. The reason it takes so long vs other PMDG aircraft is because the NGX is much more complex and there is a lot more data for FSUIPC to save. While flying from PHOG to KLAX about half way through the 5 hour flight computer just froze up and not even ctrl alt del would work. Only thing I could do was a hard reboot. Gave up on that flight and waited until the next day. Tried the same flight again and this time about 1.5 hours into the flight it froze up again. Gave up on the flight and on the third day I decided to use the MD-11. Made it to KLAX without any freezes.The difference in my case is I was not entering any info into the FMC, was just at cruizing along and it froze. I am not using FS2Crew. I am flying in 2d Panel Mode, using GEX, UTX, AS2012 and FS Global 2010. System specs: Windows Vista 64-Bit, 3.0 ghz, 8 gig ram, Quad Core, 8800GTX Video Card with 768 meg vram.Prior to SP1C I was able to fly the NGX on long range 7 hour flights without any problems whatsoever. Only after SP1c did the system freeze start. After the 2 freezes with the NGX I did make a change before using the MD-11 on the PHOG to KLAX flight. I upgraded FSUIPC from 4.7 to 4.8 which just came out this month. I am going to try another test flight from PHOG to KLAX in the NGX later today. If it does not freeze then I will know that upgrading FSUIPC helped fix the issue. However I am not very optimistic that this will fix it. I am just guessing here but is it possible the move to Visual C++ 2010 with the NGX caused a problem somewhere and that there is some code that needs optimized or cleaned up?

-300 would be considered a hard landing. -150 or better would be considered a good landing and under -100 would be considered excellent.Also you can see all the animations of the NGX if you use FS-Recorder instead.

http://forum.avsim.n...-product-range/Scroll down and find the Download Links under INSTALLATION INSTRUCTIONS:

The Radios Stack colors are now correct, and previous Service Packs are never required, only the most current one. (SP1c) If you took the time to read the release notes you would know this already.

Once you install the NGX the first time your not going to be asked for the activation code again.

SP1c is required for all future NGX expansions. Would not make sense not to include it on the CD now would it?So yes you will get the very latest, greatest SP1c on your Backup CD. :(

Only thing Xgauge installer does is to install by default to panel #5 in all your aircraft. Then you just setup a shortcut for it. Very useful and you can keep it open the entire flight if you want cause it has 0 effect on FPS. Very useful if you want a weather radar and be able to instantly see Turbulence, Rain, ATIS, and Altimeter info at your Arrival, Enroute and Destination.

Disregard. Just realized Activesky 2012 modifys that file whenever you load a theme. So after using the custom MD-11 spot and I want to go back to the original just need to load an AS2012 Theme to get it back to normal.

Okay not sure what to do here. When NGX installed it made its own custom spotlight bitmap for the landing lights. However it been awhile since I used the MD-11 so was going to use that now at RKSI and its night time there. There is an issue with the MD-11 Landing lights and you have to use a custom spot for the lights to show up correctly instead of way ahead and off to the right of the runway. Well I forgot to backup the Spotlight for the NGX. So can I get this file somewhere without having to reinstall the ngx again? Looks like when I switch between the NGX and the MD-11 I am going to have to use different spots.

Not sure why this is happening but I noticed when I switched to AS 2012 even on Ocean flights it seems like I always have a ton of clouds around me. There is never any clear days or just party cloudy days like before with ASE. Any ideas? I using the default AS2012 settings with the following exceptions.Set Download interval to 15 minMax Surface Visibility 55 nmMax Upper Visibility 110 nmFSX Cloud Draw is at 110 nm when at Cruise and 60 nm when descendingCloud Density set to MaximumI would think maybe its the FSX cloud settings that causing all the clouds but even if i switch to high and 60 nm there seems like there a ton of clouds all time and rare to see clear days or just wispy cloud days at cruise. Is this normal?

Then try one of these. :(http://www.737yoke.com/basket.php

Actually the best solution would be something like this with matching Rudder gear.http://secure.simmarket.com/fi-hw-ffb-737-force-feedback-b737-yoke.phtmlThe reason I just said a joystick to start is because obviously he is of limited means at the moment. Of course the Pedals would make it more enjoyable, but hey you got to start somewhere.

I have the NGX, MD-11, and 747-400 and they all co-exist perfectly. I think the reason some people have issues is they have corrupted installs or did not fully install everything that was required.Example: FSX Service Pack 2, Visual C++ 2008, and be sure Windows is up to date.

If all you have is a keyboard to fly with why did you buy the NGX in the first place? The most logical thing to have done was buy a good controller first and fly with default planes. Your really missing out on a lot by flying with a keyboard. I used to just fly with a single cheap joystick for many years until I got the Saitek X52 Pro and Rudder pedals. Now I wonder how I got by all those years without them. Yeah I know controllers cost money, but thats just a fact of life in the world of FS. My suggestion would be save your money and start out with a good joystick controller. There are plenty out there that cost less than what you paid for the NGX.Something like this for example: ($49.99 USD) http://www.saitek.co.../prod/fly5.html

Well I guess we will find out when the SDK released, if C++ for Dummies is enough.

I think too many folks have the misconception that the SDK is going to be like an NGX Paint Kit, where the Ordinary Joe without any programming skills would be able to custom tailor the NGX to their liking. The lowdown and short version is you will need some programming skills that are on par of a Developer to be able to use and take advantage of the Software Development Kit.

I have always wondered about this but never asked. I have the MD-11, NGX, and 747-400. By default the 747-400 shows all the traffic no matter what the altitude. In the NGX you can choose this as an option or you can use filter. But what about the MD-11 is there any way to display all traffic? It displays traffic that is within maybe 2500 feet above or below you but thats it. Never saw any options anywhere to change it.