mfrantz

Arne, Create a CHARTS sub-folder under either the PMDG\EFB\EFB Documents Library\747-8 folder or the PMDG\EFB\EFB Documents Library\Common folder. In the first case the documents in CHARTS will be accessible only in the 747-8, in the second they will be accessible from any PMDG aircraft with an EFB (in the future).

Bob, This option is not uplinking alternate FLIGHT PLANS, but the alternate airports LIST, that meet the preset criteria. This is, if you are talking about the same data link option I think of. There is one more option related to alternates that has to do with weather uplinks. In either case there is no flight plan uplinking functionality for alternate airports.

Yes EFB units are aircraft specific. However, the default EFB units of each aircraft are set to be the same as the FMC units. So, if you load a new livery that has KG units and you are fine with that you don't have to change the EFB preferences. But if you want LBS then you need to change both the FMC options and the EFB preferences from KG to LBS. You have to do this once. The next time you load the same aircraft the units of your choice will be retained

Aaron, The EFB unit preferences are written in the [EFB] section of an .ini file located at [Sim folder]\PMDG\PMDG 747 QOTS II\Aircraft and named after the aircraft registration number (for example N748PM.ini for the house colors passenger 747-8). To be 100% sure, can you confirm you set the EFB units from the EFB SYSTEM>APPLICATION PREFERENCES page and then press the SAVE button? If you can confirm this then please contact support and pass them the above information.

Jeff, During the update the whole W&B system of both the -400 and the -8 was revised to allow for more accurate cg effects/calculations. During this process base data, payload stations locations & numbers etc. were updated and results were verified against various airline companies trim sheets. I can't recall what was it that led to the specific 747-400F MTOW change. Probably done for consistency in selecting similar MTOW options for the various 747-400 variants.

EFB units are not saved to the panel state file, but to the options.ini file and are specific to the airframe. Aaron, are you aware that EFB units are independent from the units you select in the FMC options menu? You could have LBS selected in the FMC and KG in the EFB. EFB units are selected from the EFB itself in the SYETEM>APPLICATION PREFERENCES page. If you set LBS there, the EFB will remain in LBS each time you load the same aircraft, regardless of panel state.

A fix was provided with the 747-400 update at the time the 747-8 expansion was released (2 months ago). If you still see the white box I guess you have not installed this update? Since this is the 747 forum I assume you were talking about the 747. If you were talking about the other PMDG aircraft, the above post also explains how you can manually fix this for them as well.

Keith, I checked this and found it was a bug indeed. No need for a support ticket it is already fixed for the next update.

In the next 747-400/747-8 update the issue will be fixed for the Strobe and Taxi lights. The Logo lights issue will remain for now because it interferes with our custom visual lighting process, but it will be addressed in a future update (same applies for the 777).

Yes, it will be through I micro update, not an SP. We just want to finalize a few more fixes that will go into this micro update. It won't be long.

This problem has been fixed but you have to wait for the next update of the 747-8.

Only rectangular generic buildings will be shown on the airport map. This means practically no buildings at all for add-on sceneries (since developers rarely use generic buildings) an only some buildings for default scenery (only rectangular ones). This is due to limitations of the data included in the AFCAD files. We have plans to improve this situation in the future with the help of add-on developers.

Jack, It must be something more than chocks involved, because it works fine here. Can you reproduce it every time? If you can we need all steps/conditions from the moment you launch P3D.

Paul, See this post: If your issue is not caused by a wrong PC time as in Heins' case, then it is something else going wrong during the communication with the Navigraph server. Unfortunately at this time the CTD is not allowing us to know what the exact issue is but from the next update there will be an error message logged in the EFB SYSTEM page.

Jack, We have heard about his situation from other users a few times. But unfortunately it is not a consistent behavior and we have not been able so far to reproduce it in order to determine the cause and fix it. What we need is someone that can reproduce this issue following specific actions that will result in this behavior every time he performs again the same actions. If we have this information we will be able to fix it.

If it is the FMC can you check on the 747-8i if the EFB>OPT>WT & BAL page also shows zeroes?

Can you post a screenshot of the EFB showing the zeroes?

Are you sure these are the maximum limits, i.e. the values in parentheses? Can you post a screenshot? These values are read directly from the aircraft.cfg and I can't think of any other reason to be shown as 0 except of a corrupted aircraft.cfg file.

Don't worry we do monitor this thread 🙂

No - it's not a bug, since the AFCAD files where never meant to bu used thks way. But gir PMDG it is the best solution, because the airport layout will always be correct for the airport scenery that is used, despite any incuracies with the scenery itself.  Actually there is a bug. There is a DrawSurface parameter in the AFCAD files that is supposed to suppress drawing of taxiways/runways surfaces. However, if set to 0 it is just ignored and the surface is drawn anyway. This has been always the case with FSX and has not changed in P3D. If this parameter was working, scenery developers could use it instead of having to change the type to PATH.

Finn, I have tried to explain the situation the best way I could in this PMDG General forum post: If you read this again carefully you may understand that are may factors involved and why a simple PATH/TAXI replacement is not a "one-fits-them-all" solution, even within the same airport some times. I understand that you have tried this to a few airports and it worked, but this is different from the knowledge of how this exactly things works (e.g. how naming, widths and other factors also come into play). We have this knowledge, simply because we have developed it ourselves, so we we stick with what we know for certain. This does not mean that we are not open to adjustments and improvements, as already mentioned we are working on this, but we won't rush to add a "SHOW PATH AS TAXIWAY" option without considering all the factors and thinking about more consistent solutions. Believe me, if the ND Airport map was unusable with addon sceneries we would have heard about it by now (the hard way through a storm of support and forum posts complaints). We have warned right from the start that there may be some glitches with addon scenery, and there are indeed, but our experience so far tells us that overall the ND Airport map performs reasonably well and in no way it can be described as unusable.

There shouldn't be such a difference. Make sure all the data fields on the EFB are the same as in the FMC.

This is now fixed for the next update. You'll only have to enter user name/password & consents once and then you'll never see these screens again.

This is not true. We never said we will not implement this at all. We said we couldn't have it ready (and correct) at the release date but we will implement it in a future update. The same stands for EFB assumed temperature calculations. Having readily available data, as mentioned, is a problem, but will not prevent implementation.

Regarding the CTD when clicking ALLOW on the Navigraph authentication window see this post: