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.

 

 

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.

Thank you very much for the update! looking forward to the next service pack to fix all these tiny bits! But I must say the 77W is AWESOMEEE!! Thanks for all the efforts that you guys have put in!

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. 

 

Have passed this on to the FSGRW forum.

 

Soeren Nielsen

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. 

 

FSGRW V 1.7 Build #23, said to correct this issue, is out now.

 

Soeren Nielsen

Hello,

 

Had the same problem when using the perform init uplink procedure. I did not create the ,wx file in advance, so fsx crashed all the time. Using AS2012.

 

Thanks for the fix.

 

Regards,

 

Nico Dhondt

FSGRW V 1.7 Build #23, said to correct this issue, is out now.

 

Bought the 300ER yesterday. After a 4 hours flight while descending into OMDB I wanted to refresh wind data.. booom CTD. :rolleyes:

 

Problem Event Name: BEX ... Fault Module Name: PMDG_777X.DLL

 

FSGRW V 1.7 Build #23 in use.

Bought the 300ER yesterday. After a 4 hours flight while descending into OMDB I wanted to refresh wind data.. booom CTD. :rolleyes:

 

Problem Event Name: BEX ... Fault Module Name: PMDG_777X.DLL

 

FSGRW V 1.7 Build #23 in use.

The FSGRW V 1.7 Build #023 was never supposed to fix the CTD, but the INVALID UPLINK message, which it did. Post #15 above.

 

The CTD is described in post #14, and, I think, supposed to be fixed in the pending PMDG 777 SP1b.

 

Soeren Nielsen

The FSGRW V 1.7 Build #023 was never supposed to fix the CTD, but the INVALID UPLINK message, which it did. Post #15 above.

 

The CTD is described in post #14, and, I think, supposed to be fixed in the pending PMDG 777 SP1b.

 

Soeren Nielsen

Ah ok thanks Soeren.

Hopefully this bug will be sorted out with tomorrows update.