Chaos81

Yep. I flew out of KOAK earlier, and just sat there for a couple minutes watching the weather move on the radar. :lol: And yes, I realize how sad that sounds. :blush: Like this from the real world (Go 95 seconds in, not sure if it'll link properly). Notice how you can see it sweep when it crosses over the weather. That's what it looks like. And just as an FYI, the terrain radar will do this too with SP1.

Rynardt nailed it. FSX is "freezing" because choosing to view the license key opens shows the key in a dialog box, not inside FSX . You need to click ok on that to get back to FSX again.

Peter, There's a readme file in the FSX\PMDG\WX file that should have the information you're looking for.

They mentioned a few days ago on their forum that they've programmed this already. It's in testing with a few other things and should be released soon.

EDIT: My mistake, as Tony says below, no need to manually enter the name of the .wx file. Just entering the airports is enough to get the FMC to read the proper file if you have it named correctly. Wasn't thinking clearly.

AJ, There is no need to erase the existing route in the FMC, there's also a way to select a specific file. Obviously i didn't explain things very well, so here's another attempt. This is all with AS2012. First I did what I you already know how to do. I loaded a flightplan named CYULEGLL1, and copied the winds to CYULEGLL1.wx. These winds were actually from a previous flight, which was only to make sure they were different than the current winds I'll be using in a bit. Then I went to the RTE DATA page and did a wind data request. In the first picture, those winds are currently loaded, and as you can see, it's showing me arriving in EGLL at 415z with 16.2K pounds of fuel remaining. So from here, obviously you might want to update the winds at some point during the flight. First I copied the new winds from AS2012 to a new file named CYULEGLL3.wx. Then I entered the name of this new file into the scratchpad. Again looking at the first picture, you can see that I've done this. From here it operates just like it did before. Click the request button for wind data, then execute it. This loads the winds from the file that was named in the scratchpad (CYULEGLL3). The second picture is after I executed the wind data request on CYULEGLL3. You can see that the fuel lines on the RTE DATA page have changed slightly, and that the progress page is now showing me arriving in EGLL at 5 minutes earlier (410z v 415z), and with an extra 1.2K pounds of fuel (17.2 v 16.4). This is due to the new winds I just loaded into the FMC. Hope this helps. z

Unsure if this is exactly what you're looking for, but the TOCG will turn yellow just like the weights if you're out of the limit. So if it's still white, you're should be good to go.

Did you press the MIC button on the ACP?

I think the answer to this is as Rob and Dan described above. This gets saved with the panel state, and from what you posted, it seems like you were loading the PMDG short turn panel state, which had 18K set as the TA when saved. The reason it worked for me, is because I didn't load a panel state, I was doing it straight from the default engines running. This seems to be proper behavior going off what the intro manual states, but it's possible I've completely misunderstood things. Page 72:

Just tried it and it worked as expected. Here's what I did. 1) Changed default TA to 10,000 - Was originally set at 18,000 for Delta livery. 2) Restarted FSX - The TA option isn't a change on the fly option like some of the other ones, you need to restart FSX for it to save properly. Are you possibly skipping this step? 3) Took the picture below. 10,000 on the VNAV CLB page.

Try copying the new winds to a new .wx file than the one you originally loaded, and then name it something different. So if you started with CYULEGLL.wx, copy the new winds to a file named CYULEGLL1.wx. Then enter "CYULEGLL1" into the scratchpad, and press the wind data request button, followed by the EXEC button. That should load the winds from the CYULEGLL1.wx file and now your winds should be updated with the new data. Note: I haven't tried this mid-flight, so it's possible there's an issue there, but I did just give it a shot on the ground and it looked to work without issue. This was with AS2012.

Unsure if this was the exact issue some had with the NGX, but I believe some of these climb issues were fixed when people deleted their FSUIPC.ini file and let the sim generate a new one. Maybe try that, and make sure you back up your current copy somewhere just in case that's not the fix.

Somewhere over the rainbow.

Please, please, please read the intro manual. Tons of information in there, including this exact question. Page 37 of the intro manual covers this.

The cabin only loads with an external view, if you only use the VC, disabling it won't change anything. Try moving outside the VC sometime, kind of a cool view and it'll show you just how little outside of the VC is loaded (basically nothing).

Looks like it was EGLL-KIAD. http://en.wikipedia.org/wiki/Boeing_777#Entry_into_service

Looks like your TAT is +29C. Don't know if you're still flying, but what happens if you try clearing all weather?

I used the Saitek yoke for probably 25% of my flights during wide beta without issue for what it's worth.

It does indeed support third party liveries.

Rick, It was installed with the 777. Start Menu > PMDG Simulations > PMDG Operations Center.

PMDG Operations Center. Start menu > PMDG Simulations > PMDG Operations Center. If you need help figuring things out after you open up Ops, check the intro manual, there's a bunch of information in there.

Daniel, Move the EICAS to one of the inboard screens using the knob labeled "inboard display" under the screen. Then use the DSP (Display Select Panel), the thing on the right side of the MCP, and select the screen you just moved the EICAS to, and push the ENG button on the DSP. Then just move the EICAS back to the middle screen and away you go.

Page 60 of the intro manual:

I've been using AS2012 and haven't had any issues FWIW. Not sure what anyone on the team is using.

Can't post a picture of a livery we don't have.