mfrantz

I think that the bluriness you refer to is related to the "Mipmap VC Panels" setting on the display options. If you turn off VC mipmapping the bluriness will go away, but then lines & text on the displays will show somehow "broken" Personally, I prefer it with mipmapping on.

This is an issue we have identified and is fixed for the next update. See this post for details: forum.avsim.net/topic/446916-pref-init-uplink-fsgrwcrash/

Are you using any weather add-on application?

The flight number uplink is automatically performed when you do a ROUTE REQUEST. If the flight plan you request includes a specific flight number (this will happen if you save a route from the FMC while the flight number field is set in the ROUTE page) you will automatically get the "FLT NUMBER UPLINK" message and the flight number field will be set. There is no action required, other than clearing the message with the CLR key.

BTW, while troubleshooting this with an evaluation version of FSGRW I noticed that FSGRW has an option to create a .WX file for the PMDG 777. However, the format of this file is incorrect and loading the data will result in an INVALID UPLINK message. If any FSGRW user wants to pass this to their forum, the problem is that the 777 requires 10 wind/speed/altitude fileds at predefined altitudes placed in two lines of 5 entries each. The FSGRW creates 11 entries instead placed in two lines of 6 and 5 entries. This is not accepted by the 777.

Clive, This is not the cause. I can't recall now if there is a reason for omitting the destination airport in the PLN file. I'll look into it and if there was no particular reason we will add it in the next update. Found and fixed. Had to do with length of METAR forecasts that FSGRW and other addons are injecting in FSX. When these are unusually long you may get CTDs when using a weather addon that does not create a WX file and therefore the 777 will have to grab forecasts directly from FSX METARs. Can happen after accepting PERF INIT when the automatic preflight uplink option is set, or when requesting wind data, descent forecasts and alternate wx (especially with alternate wx requests it may happen even if you are using ASN). Will have this fully fixed in the next update.

Looking at it. Will let you know when we have news.

Check this post: http://forum.avsim.net/topic/446888-taxi-cam-problem/ "For those with this problem try changing the fsx.cfg line wideviewaspect=false to wideviewaspect=true. Hope it helps"

If you turn it off, then you have to manually load the flight plan into ASN (from the ASN flight plan tab) to be able to get weather forecast data.

Not sure if this is your problem, but be aware that the WX.PLN file is created whenever you move to a CDU page that contains a weather related REQUEST prompt. This is done to make sure that an updated flight plan file is already created before you request any weather related forecast. This means that setting the "FSX PLN FILE FOR WXR" option and creating or loading a flight plan in the FMC is not enough. You should go to the LEGS DATA or the DES FORECAST or the ALTN CDU page and then the WX.PLN will be created.

The Auto Alternates option does not update the alternates weather forecast. It updates the list of the closest company preferred alternates (displayed in ALTN page 2/2). You can update the weather forecast for the 4 alternates displayed in ALTN page 1/2 anytime from the WXR REQUEST prompt at L6

This is not true. This option does not control the creation of the XXXXYYYY.wx file that contains the wind forecasts. It controls the creation of an FSX format flight plan file, named WX.PLN. The 777 will use FSX weather only if no XXXXYYYY.WX file is found for the XXXX-YYYY route. If a .WX file exists it will always be used to provide forecasts. The difference between the "Create WX.PLN file and load to FSX" and "Create WX.PLN FILE" is that in the first case the wx.pln file is created and automatically loaded to FSX in order to trigger an automatic loading to ASN, while in the second case the file is not loaded to FSX, therefore you should manually load it yourself into ASN from the ASN flight plan tab. This is all explained in detail in the provided supplement document.

Yes you are right, I only noticed the screenshot itself.

A clean install was indeed not required. However, as it was mentioned several times, panel states and saved flights created with the original release version will not work with SP1 and they will create all sorts of problems.

A small mistake here. Based on the screenshot of MENU > PMDG SETUP > OPTIONS > SIMULATION you provided, SP1 will only create an FSX flight plan (.pln) file but will not load it into FSX. You have to set the option in L3 to "create and load in FSX".

The changes in clouds happen each time ASN loads a flight plan. This is an ASN issue not a 777 issue. Normally the clouds you see out of your window shouldn't depend on the flight plan in ASN. Actually even if the flight plan doesn't change and you reload the exact same flight plan file in ASN clouds will change. I can't tell why this happens, probably ASN has a reason for doing this but we can do nothing about it. You can see it regardless of the 777 data uplink settings. If you go to the ASN flight plan tab and just load a flight plan you will see that the cloud positions change. You are seing this when the alternate airports list is updated, when one or more of the 4 alternates, or their order changes and this triggers the creation/loading of an updated flight plan for ASN. You can avoid this by turning off the 777 option to automatically update the alternates list. Or, obviously, by turning off the automatic loading of the flight plan to FSX. You can always manually load an updated flight plan into ASN whenever required.

If you don't load a flight plan into ASN then no WX file is created. If the 777 finds no WX file it will get weather forecasts directly from FSX. Since weather add-ons like ASN set the FSX weather only in an area 50-100 NM around the aircraft position and clear the FSX weather in the remaining world you will get wind forecasts only for a few waypoints ahead of you and in most cases you will not be able to get any descent forecasts if the destination airport is outside this range. So, what you are getting is partial weather data for a limited area around your current position.

They are not intended to have any transparency. Check you FSX settings, there is a setting for 2D panel transparency, it should be set to 0.

If you have set the PMDG option to automatically create an FSX flight plan and load it into FX and also set the ASN option to automatically load FSX flight plans, then whenever you go to a CDU page that contains a weather related REQUEST prompt an updated FSX flight plan will be automatically created and loaded both into FSX and ASN. This will result in ASN creating an updated WX file. However, the update of the FSX flight plan and WX file will only happen if the flight plan has been changed since the last time it was created.

Depending on the datalink options selected in aircraft options, a route request (during preflight), or a winds request (at any time) may automatically trigger additional requests once the original request is accepted. In this case the EICAS FMC message will be displayed, until all requests are handled. Press the CDU FMC COMM key to check if any uplink is pending, then go to the relevant CDU page to accept or reject the data.

Valentin & Adam: Once you load a flight plan into FSGRW a file named XXXXYYYY.WXR should be created in the [FSX]/PMDG/WX folder, where XXXX & YYYY are the ICAO codes of the origin and destination airports. Please contact PMDG support and attach this file to the ticket. Describe the problem and mention that I asked you to attach the file. Calvin: Are you sure the crash happens when you try to accept the PERF INIT uplink, and not when accepting the winds data uplink? If so can you please post a screenshot of the PERF INIT page just before you press ACCEPT?

The 777 cannot change the weather. Obviously the weather changes come from ASN. I really don't know if this ASN behavior could be triggered by loading an updated the FP into ASN. Like maybe ASN adjusts the weather settings to fit the FP route? You mentioned this happens whenever the alternate airports are updated. Do you have the automatic alternate list update turned on? If so try turning it off and see if this still happens. Please, tell me what are the datalink options you have selected in the PMDG simulation options menu and the PMDG aircraft options menu and I will try to reproduce this.

The nose gear must be down and locked and the beacon light switch must be on for the camera lights to operate.

The 737NGX way (rotation) is provided as an option in SP1

PMDG_INTERFACE.dll is included for a reason. The most important thing you will notice if you disable PMDG_INTERFACE.dll is that you will have problems when loading 777 saved flights. The flights will load but the corresponding panel state file will be ignored and all the switches/systems etc. will be in their default state and not in the state they were saved.