Resolved 9106 PMDG export issue

Daveo

Community Manager
Staff member
Which Firewall/AV are you using?
 

bobsk8

Member
I reinstalled Active Sky. The only thing I cannot get to work now, is the flilght plan loading into PMDG either the 777 or 737, and I have tried selecting them in the PMDG path settings export path settings. I have my sim on the F drive, and am using that community folder and the WX folder for either aircraft. I use the default AV in Windows 10. F:\MSFS\Community\pmdg-aircraft-77w\Config\WX It worked perfectly before the update?
 

Attachments

Last edited:

damian

Developer
Staff member
Can you confirm that the appropriate .wx file is being generated by ASFS in that selected location? Or no? We cannot duplicate an issue on this end.
 

bobsk8

Member
Older version, 9019 from my backup drive, the correct WX file is sent to PMDG 737 or 777, which ever I point to. Update 9019 to latest version, and no file is sent to PMDG. Uninstall latest version, reinstall 9019 and file is sent to PMDG. I did this 5 times, with same result each time..
 
Last edited:

damian

Developer
Staff member
Thanks for confirming. Interesting. I cannot duplicate this. Would you be willing to open a ticket so I can troubleshoot with you directly and provide some test/extra logging builds to ID and resolve this ASAP? Thanks.
 

bobsk8

Member
Thanks for confirming. Interesting. I cannot duplicate this. Would you be willing to open a ticket so I can troubleshoot with you directly and provide some test/extra logging builds to ID and resolve this ASAP? Thanks.
I will open a ticket today. I also noticed that other users are having problems with the latest update, to the point where the older 9109 which I went back to, is had been added to your download page. So there must be something not right with this latest update. I am just going to stay with 9109 because everything works properly.
 

bobsk8

Member
That fixed it, not only that but the WX is showing in both the 737 and 777. Congratulations. I guess I should not update this now.:):):)
 

damian

Developer
Staff member
That fixed it, not only that but the WX is showing in both the 737 and 777. Congratulations. I guess I should not update this now.:):):)
You should always update. And report when you find issues, so we can address. The issue here was likely the incorrect path you had specified, but the "fix" identified this and found the correct path regardless.
 

bobsk8

Member
You should always update. And report when you find issues, so we can address. The issue here was likely the incorrect path you had specified, but the "fix" identified this and found the correct path regardless.
No it wasn't the path, I checked the path a half dozen times, and when I installed the older version that worked, the path was exactly the same. In fact I even posted the path in one of my posts above on this thread. (post #3)
I just checked the path now in the new version that is working, and it is exactly the same.

F:\MSFS\Community\pmdg-aircraft-77w\Config\WX

I think I will just stay with this version.
 
Last edited:

bobsk8

Member
OK, I read something where someone suggested that the path for the WX file for PMDG 737 and 777 should have the WX directory inside the Work directory and not inside the Config as mine is.. THis is the way PMDG set up my directories when I installed both the 737 and 777

F:\MSFS\Community\pmdg-aircraft-77w\Config\WX ,


I posted on the PMDG forum tonight to see why my install says Config, and you think it should be Work....
 

damian

Developer
Staff member
As previously mentioned:
Can you confirm that the appropriate .wx file is being generated by ASFS in that selected location? Or no? We cannot duplicate an issue on this end.
If the file is being generated by ASFS, but pointed at a folder that PMDG isn't reading, this explains everything. In my tests, even with the wrong folder set as your configuration, it was writing out the file. But it isn't being read from this location, so....

There have been many updates/enhancements to this functionality since the earlier ASFS builds so I'm not sure exactly why it worked before but it's not surprising. In any case, wrong folder = wrong results, until we now have added fail-safe for wrong location.
 
Top