scandinavian13

Depends on the arrival, but there are ways to get around using it.
 
 
 
 
Overthinking it. Change it as soon as you stop hearing "descend and maintain Flight Level X," and first hear "descend and maintain X."
 
This might be helpful:

Go into your root sim folder > PMDG > NAVDATA
 
Look in there (or in the subfolders) for a runways.dat file. Delete it to let it rebuild. Something corrupted it.

This could simply mean that the LOC array does not have an associated DME. This is pretty normal.
 
 
 
 
This could simply mean that the sim scenery you're using isn't using the correct frequencies compared to the real world. Keep in mind that FSX is now over a decade old, so if you haven't updated the scenery, but you're using new charts, things could be very, very different.
 
 
 
 
The default FSX LOC arrays are hard coded to about 20-25. You can adjust this with custom scenery. I highly doubt an aircraft would read DME info from hundreds of miles away for a LOC installation. They're intentionally lower-powered installations so that you can use the same frequencies in several locations.
 
 
 
 
Full names in the forum, please - first and last.

Probably because you were using an installer that supported v2.5.
 
Unless you've downloaded the latest installer (any time after 01 October) that supports v3, then the installer won't be aware of a v3 installation, and will give you the message you're seeing.
 
If you don't have the latest installer, you can obtain it by logging into your account, selecting View Previous Orders, and downloading from your existing order page.

No. If you got rid of the last computer, you had it crash, you reinstalled the OS, or something similar, then you can't return the license. Install and attempt to activate on the new machine/installation. If it rejects the attempt, then submit a ticket using the link in my signature.

Andrew,
 
Welcome to the forum.
 
First - thanks for following the forum rule and including your name in your posts. This has allowed me to look into the issue without having to ask you for more information, and prolong the wait.
 
Second - if you're looking for one of the PMDG Team to address your issue, then the official avenue is via Support.Precisionmanuals.com (linked in my signature). This is the community support forum, where members help members, though we do have the team in here often to moderate, and ensure things are running smoothly. This is a public forum, though, so certain issues are best left to the official portal.
 
On that note - please avoid posing your order information in the forum. I don't think you posted anything incredibly sensitive, but it's best to avoid it entirely.
 
 
 
As to the issue - looks like something got hung up in the system, so I knocked it loose. Check now - you should be good to go now.

Note the fact that the line is also called PLAN. Interesting name for it if we were only concerned with the amount of fuel in the tank currently  :wink:
 
 
Reduced thrust will actually use more fuel over the course of the takeoff and climb, but it's not a huge difference.
 
 
Yep.

Thanks for reporting back, and glad you got it solved.

Hey Carl,
 
Full names in the forum please - first and last.
 
The first items I'd check are here:
http://support.precisionmanuals.com/kb/a112/important-and-nearly-foolproof-steps-to-running-your-pmdg-product-in-prepar3d-v3.aspx
 
My bet is #1, but #2 could be possible, especially if you didn't know there was an update that allows it to install into 3.1 natively and are trying to shoehorn it in with a migration tool. Speaking of, if you have a migration tool installed, this can interfere with the NGX even without using it directly on the NGX, as those tools are built to play games with the registry to make things believe that they're being installed in different versions of a sim, while telling it to install in the new sim directory. If that sounds confusing, keep in mind that computers are pretty simple machines: without specific and clear instructions, they're pretty worthless and bad things happen.

SimBrief.com
 
Just want the file? SimRoutes.com (Click on Generate Route)
 
 
So handy, in fact that we have a function in the 777 and 747 that automatically exports the FMC's route to an FSX plan file that ASN will automatically import. See Tutorial #1.5 for the 777 for how it all interacts. Not sure if the NGX will get this feature at some point.

Disregard. Figured it out.
 
The texture.cfg was corrupted somehow. Fixed it by copying my FSX texture.cfg over into my FSX:SE install. If you try this, make sure to back up the file first - FSX doesn't rebuild it automatically if you delete it.

This is correct. You can see it a little bit in the images on the product pages:
http://precisionmanuals.com/pages/product/FSX/773ER.html
 
The best image to see it is the last image in the second row.

You'd be surprised at what's right under your nose if you pay attention to the TAKEOFF REF page.
 
...particularly line 4L...  :wink:

If this were true, you'd see the same thing each time, honestly. The yaw damper will kick off if the IRS switches are turned OFF.
 
Full names - first and last - in the forum, please.

It was actually due to the nature of the question. It's all taken care of.

Submit a ticket using the link in my signature. If you haven't created an account at our support site, you will need to do so. From there, we'll have a couple things you can try.

Make sure to check the "Show All Variants" box.

If the plane levels off, you need to hit ALT INT before it's going to act on any change to the MCP.
 
Say you set 10000, but your CRZ is FL350. If you don't get your further climb instruction and the plane levels off at 10000, once you get instructed to climb higher, you roll the selected altitude up to whatever they assigned, and hit ALT INT (in the 777, this is the center of the altitude wheel).

I use ASN, and ASN is the only engine at the moment to provide weather radar in our products. It doesn't work over WideFS, but that's because it doesn't need to - it works via SimConnect (and has instructions for enabling this).
 
As far as your 'stretched' comment goes, you have an i7, and FSX does a terrible job of spreading its load across those cores. The result is that the other cores are free to process other things, like running a weather engine. Additionally, it isn't so much the weather engine taking up processing power - it's the sim trying to drive the resultant graphics. I doubt you'd see much of a performance hit if you ran it locally. I used to run everything networked and then consolidated because it just wasn't worth it to me.

This isn't the FO. This is the GPWS. Instead of this SIMULATION section, look under EQUIPMENT.

I don't think that should be necessary. Unfortunately, there were some interesting decisions made about how FSX:SE would identify itself to the registry, so when FSX gets uninstalled after FSX:SE is installed, the registry paths are removed. Submit a ticket at the link in my signature (if you don't already have an account on that site, you will have to create one), explaining that you have an FSX:SE registry error.

You need the latest version of the 777. Go to your account on our website, click view previous orders, find your order, and download from your existing order link.
 
While that's downloading uninstall the version(s) of the 777 you have currently installed. Once the new installer(s) are downloaded, install. Done.

Glad to hear you have it solved.

Romain did a great job answering the rest, but I wanted to address a few things.
 
 
 
 
This isn't quite correct.
 
The general flow of things is to set up everything except the runways until they're assigned. Keep in mind that in some cases, this might prevent you from entering the SID or STAR. For the departure, it's easy enough to just wait and select the runway when it's assigned (at the latest, as part of the taxi clearance), but you can take a guess by listening to the ATIS, especially if the airport only has one runway. It's a common misconception that the active runway is always the one with favorable wind - BWI as an example, only lands on the 33s, using 28 for departure; or lands on 10, using the 15s for departure.
 
Using BWI as an example, you wouldn't have to choose the runway at all if you were flying the SWANN departure as an example. Just select the departure and transition and hold off on the runway until it's assigned. Once it's assigned, add it in. It doesn't have to all be done at once. Same goes for the STAR. It's best to add the STAR in while sitting at the gate, but if it does not require a runway (the EXEC light will light up without a runway chosen if this is the case), then do not add one in. If it does, take your best guess, but keep in mind that it may change.
 
The base thing to keep in mind when learning about this plane, and all of its automation, is that there's a reason there's still a person up front. Automation is great, and to a large degree, we can hand over a big portion of the flight over to the automation, but there are situations where information may be delayed, and you need to just use your best judgment.
 
 
 
 
A SID (Standard Instrument Departure) is a departure. The Midway and Cicero are both SIDs, even though they're not as "pilot nav" as you're expecting (they're both heavily vectored, which is more "ATC nav"). Putting the Midway or Cicero into the FMC really doesn't do too much, but should be done, as it enters some initial guidance information (initial heading up through a certain altitude, and so on).
 
While this doesn't go too deep into the chart symbology, this might help you understand SIDs/STARs:


 
 
 
 
You might not have much interest in flying on the other side of the pond, but I'd definitely recommend flying the tutorial as it was written, even if it's just once, to see how it all fits together. Continue on to the second tutorial for some more advanced concepts (and a little more hand flying), and then head off around the world wherever you'd like.
 
 
 
 
This one's really nit-picky, but this one gets my hackles up...
 
It's an ILS approach. The landing is a separate concept. What you described (following a path to the airport, kicking off the AP, and then landing manually), could also be an RNAV approach instead of an ILS, though you couldn't autoland on an RNAV (at least legally, as of right now).
 
 
 
 
As Romain also mentioned - and I have a feeling it is your user name - but full names are required to be in your post content here in the forum. I know it might seem redundant, but since most people don't use their names as user names, we check for compliance by glancing at the bottom of posts. In order to keep things consistent and simple, that's where it needs to be.

George,
 
I'll look into the missing orders thing right now, but while I do that, confirm if you've been trying to contact us at:
https://www.precisionmanuals.com/ProductCart/pc/contact.asp ; or http://support.precisionmanuals.com/Main/ The first one is not the support site. That's a generic contact form that the developer of our product cart system made. As noted from the main site, support is via the second one. Since you haven't been getting tickets, I'm guessing you've been using the first option.
 
Either way, I'm off to look into it.
 
 
 
EDIT:
 
George,
 
Looks like your name is associated with two accounts with us (two different email addresses). I sent you an email from a new opened ticket with both email addresses on it. Just respond to that email with whatever email address you want us to merge it into and we'll take care of it.