scandinavian13

Nope. You can either simply type it into each post, or you can go to your user settings (top right, click on your user name, click on My Settings and "Signature" will be the 5th option down on the left). Add your info. Click save at the bottom.

Not sure if the save files will work, but the knowledge is definitely the same.

This, to me, indicates that you didn't have your hydraulics on, which would limit your ability to change control surface positions.
 
Full names in the forum, too, please.

Then the only remaining option would be to install via the installer you downloaded without the CD, which is actually the correct way of doing it. The CD, while nice and shiny, is no longer required with the file you downloaded. Make sure to remove all currently installed NGXs before installing the newest version.
 
 
 
It's in the latest update (the file you downloaded).
 
 
 
 
Nope.

As Steve mentioned, the options are set per livery. Please have a look at the intro manual. It explains this, why it's done, and the vast array of options provided to you and what the options change/allow.

Did you check the sound settings in the FMC menu PMDG SETUP > settings?
 
We really didn't mess with the sound at all between the last version and this one, so anything going on here is going to be coincidental. This is the first report I've seen regarding sound.

Did you select the livery after previously having the same aircraft selected? As an example: a United 737-800 and then to the Alaska 737-800.

Sounds like you have an alternate click programmed via another program or through Windows at its default. Check your mouse settings and/or sim settings to ensure your middle mouse click isn't programmed to zoom, instead of behave like a normal middle mouse button.
 
Also, full names are required in the forum. Please include this in future posts.

That's the part that matters.
 
If you're flying around and notice anything odd, an uninstall/reinstall will probably do the trick.

Guys,
 
All of our versions are the same. If one were to take the download version, put it on a DVD and slap a pretty picture on it, it would be a DVD version. I'm guessing someone threw "DVD" in there as a reminder that it was an update to bring it up to the level of a DVD-version-update release candidate (like we did with the NGX recently).

The altitude is usually set to the next higher altitude in GA aircraft (100-500' above, depending on the unit/aircraft/etc). NZAA being 23' MSL, set the pressurization panel to 50' (using NGX numbers, here). The idea is that, when descending through 50', the pressurization system will seek equilibrium by opening the valves prior to touchdown.
 
On the other hand, the 777's system will automatically set an altitude intentionally below the landing field elevation to maintain positive pressurization until the weight on wheels indication (I'm guessing for structural rigidity), where the pressure will be removed by opening the outflow valves. From what I'm reading of Boeing aircraft, despite having to set the elevation manually, the AUTO mode of pressurization seems to always force slight pressurization by setting the landing alt artificially to 200-300 below the set/stored altitude. Knowing this, it seems that setting it to whatever is closest will work, though I recall seeing an airline SOP that follows the "next highest" value setting, just for consistency.

Compared to the 777, the NGX is a pretty light plane. Add that to the FSX Runway-Covered-In-Peanut-Butter coefficient of friction (read that as "friction is way too high in the sim") issue and you get an autobrake that really doesn't add much breaking to the sim to get it to match the autobrake level values. Because of this, the brake temp indicates lower than it should for the same operation in the real world.
 
If you do a few rejected takeoffs, you'll see it, though.

Yep. It's installed with the aircraft and already on your computer. Start > All Programs > PMDG Simulations > 777 > Tutorial #1.

That's the issue, then. I'm not quite comfortable with offering up ideas on how to go into the registry to resolve those issues, though, because editing the registry can cause a decent amount of damage to a computer (in a software function sense).
 
This thread explains the issue:
http://forum.avsim.net/topic/458665-a-couple-of-tips-for-fsxse-users/
 
Also, full names are required in the forum, please.

No. Just run the brief before unpausing. That, or brief during the initial descent.

The default FSX replay feature does not show these functions. You might want to consider other tools like FSRecorder.

This is the customer support forum. The ticketing system is linked from the same spot and references itself as "official support" or something similar.
 
Regardless:
Support.Precisionmanuals.com

Pull your FSUIPC.ini onto your desktop to let it rebuild to eliminate that as a cause.
 
Full names in the forum, please.

No. We do not offer trial versions.
 
Additionally, full names are required to be in all of your posts in this part of the forum.

Correct. This is modeled correctly in the 777. We have it in the tracker to evaluate in a future service pack.

Search for "side by side" as I'd mentioned earlier.

Remove the chocks.
 
MENU key. FS ACTIONS > GROUND CONNECTIONS > CHOCKS.
 
Edit:
Full names in the forum, please.

Since you ordered it with your old email account, you were able to log into your account on our website with those credentials (doesn't matter if you still use the email address to receive emails). Log back in, click on View Previous Orders, and then click on your latest order. Your links will be in there at the bottom. This will allow you to get the product without waiting for us to get to your ticket.
 
We can certainly merge the two accounts, though, for your convenience in the future. Just go to support.precisionmanuals.com and submit a ticket with what you're considering the old account, and the account you'd like us to merge everything into and we'll take care of it.

Welcome!
 
That's understandable.

The code behind panel was added. The click functionality wasn't added to the front end. Perhaps in SP2.