tjeuten

Glad you could make it work Kevin.

Ok so got the confirmation from Ryan that this is indeed the issue, and that they are looking into fixing it and will then probably release new installers in the near future. Disclaimer: the workaround I posted above is at your own risk, so only use it if you more or less know what you're doing. Once PMDG fixes the issue, you should remove the symbolic link you created (which can be done from the Windows file explorer)...

Hi Fareed, thanks for posting. Yes this were my findings yesterday too, I've got a PMDG ticket open with this issue, and noticed my findings to Ryan from PMDG but he hasn't replied yet, so I wasn't sure I could post the workaround here, but I guess it doesn't harm. What I did was create a symbolic link from "My Documents\Flight Simulator X - Steam Edition Files" to my "My Documents\Flight Simulator Files". I did that by using following command in a command prompt (run as admin) on the My Documents folders: mklink /D "Flight Simulator X - Steam Edition Files" "D:\Users\msoup\Documents\Flight Simulator X Files" (replace "D:\users\msoup" by your own path to your user profile where your documents are stored) So now the T7 generates the WX.PLN file in the correct folder, through the symbolic link, and ASN picks it up correctly. No need to redirect ASN. ps: Symbolic link is NOT the same as a shortcut. Creating it as a shortcut won't work. Mathieu

Peter, could you check that, when you load/activate a route in the 777 FMC, a file called WX.PLN is generated (or updated) in your "Flight Simulator X Files" folder, located under your "my documents" folder ? Cause that is the issue on my side, that WX.PLN file is never generated.

Peter, I've got only one PMDG\WX folder, and that is located at C:\Games\Steam\steamapps\common\FSX\PMDG\WX, so basically at the location where it is supposed to be, under the FSX root install

Thanks for the info Philippe, but I already checked that part of the FMC multiple times and it is configured just like your screenshot, so I'm afraid it's not related to that on my system.

Kyle, correct, but that was before I fresh installed my Windows system (complete reformat) with Windows 10 in August 2015. I have only had a single install (FSX:SE) since then, and as said, the WX.PLN generation worked great until my last flight with the "old" T7 somewhere in December 2015.

Mike, thank you for your post, but like I said, my problem lies in the generation of the WX.PLN file. I have a single install system, only FSX Steam. NOT a dual install. I have a "My Documents/Flight Simulator X Files" folder. NOT a "My Documents/Flight Simulator X - Steam Edition Files" folder. Prior to the new PMDG installers, WX.PLN file was generated fine in My Documents/Flight Simulator X Files folder. After new installers, no WX.PLN file is generated any longer ANYWHERE. I have scanned my whole computer with a Windows search (all disks) to be make sure it's not being generated at any other location, but it is not. As it is working for you with the new installers, there must be a condition on my system that prevents the generation of the WX.PLN file. The only problem is I cannot figure out what. Apart from uninstalling and reinstalling the T7 with those new installers, I have made no significant changes to my system in the last few weeks... I am using an admin account to run FSX. I have checked the My Documents/Flight Simulator X Files if it is read-only. It is not... So I'm out of clues really... One thing that could help me is if a PMDG dev told me how the FMC looks for the folder to save the file in. I suppose it is a registry key ? If so, which one ? Then I could check if that setting is correct...

That in PMDG SETUP -> SIMULATION the option was set to "CREATE FILE AND LOAD TO FSX"... so if I'm not mistaken that setting is supposed to create a WX.PLN file in the "Flight Simulator X Files" folder and load it into the internal FSX flight planner for ASN to pick it up when you load and activate the route (.rte file) in the PMDG 777 FMC. It did just that prior to the new installers. It doesn't do that anymore since the new ones, at least not on my system... Uninstalled the T7 completely today by using the uninstallers, and deleting the PMDG 777 related folders in SIMOBJECTS\AIRCRAFT and also in the PMDG folder. Redownloaded the latest installers from the PMDG website (the ones from today actually). Reinstalled. Still the same issue though... No WX.PLN file is ever generated. Is there any logging I can activate and send the files to PMDG afterwards ? Mathieu

Thanks, but like I said, 99% sure it has nothing to do with ASN. It's on the PMDG side. It stopped working the day I installed the T7 with the new installers. I submitted a ticket to PMDG, I'll see where that leads us. I'll post any findings back here, don't worry. Thanks for all the help.

Yes I did but I don't think it's related to the ASN version, as it stopped working before I installed SP4 of ASN. If I load a flight plan into the FSX memory by using Aivlasoft EFB, ASN is correctly picking up the flight plan and creates the .wx file accordingly in the PMDG\WX folder. As I see it, the issue is that the PMDG option to create a WX.PLN file and load it into the sims memory is not working any longer, so I really think it's on the PMDG side rather than the ASN side.

Yes, I know it's only 10 secs of extra work, but I'm just curious to know why it worked before using the new installers, and why it stopped working afterwards. I just loaded a route in the T7 FMC (and have the option set to "create wx.pln file and load to FSX"). I activated the route. I scanned my whole computer (all drives) to find a WX.PLN file dated from today. I didn't find any...

I just uninstalled the T7 from my system, and reinstalled it, rebooted, reconfigured the FMC settings to the correct settings for the uplink to work etc... No WX.PLN file is created when I activate my route or request the wind data. So nothing is loaded into the FSX flight planner, and as a result the ASN flight plan stays empty and no .wx file is generated in the PMDG\WX folder... :(

Never had to do this in the past, as ASN is supposed to pick up the flight plan once activated in the FMC, and then create the file in the WX folder itself. It always worked for me like that in the past. afirm, triple checked

Have a look at this PDF you can download from Smartcockpit: http://www.smartcockpit.com/aircraft-ressources/B777-Instrument_Approach_(Using_VNAV).html Basically, the correct procedure is, while on final, to set the MCP to the missed approach altitude once you have descended through 300ft below the missed approach altitude. I'm not sure about the "quick" and "slow" knob turning behaviours, but I use the above procedure and it works every time. Hope it helps. Mathieu

Hi, before I re-installed the T7 with the new installers released recently, my ASN weather auto-integration and uplink was working without any issues. However, since the new installers, this does no longer work. I've checked and redouble checked my settings according to this guideline post and they are set accordingly: http://www.avsim.com/topic/447135-brief-workflow-tutorial-pmdg-777-sp1-company-datalink-function-with-pfpx-active-sky-next-asn/ The problem is that when loading a route (.rte) into the T7 FMC, it doesn't seem to load the flight plan into FSX memory, nor does it create a WX.PLN file in the "Flight Simulator X Files" folders. So ASN is not loading the flightplan into it's memory either... Anyone else having this issue ? Is it maybe a small bug that was introduced with the new installers ? I'm using: FSX SE Active Sky Next PFPX for the flight planning and .rte file generation. ps: upgraded today to ASN SP4, but that didn't change anything. It stopped working right after using the new PMDG installers so I don't think ASN is to blame... Thanks. Mathieu

For me, the 200 LRF base package installed fine, but the 300ER installer complained about FSX and FSX:SE being installed in COEXISTENCE... which is not the case, I only have FSX:SE on my machine. I could not continue install of the 300ER. I have filed a support ticket with PMDG. I'm sure they will fix it soon. Thank you PMDG for this New Year gift. Regards, Mathieu UPDATE: Forget I said anything, just saw the "coexisting" topic in the forum... I must have downloaded the packages while they were updating them (I donwloaded at 0856Z), downloaded the correct 200 package but still the faulty 300... Redownloaded the 300 and works fine now.

Ow it's down under. Indeed I checked it on Google Maps and it seems to check out... Thanks for that Tanmay, your first post and already answering a question :-) Welcome

Hey guys, been wondering about it for a while now, have googled but didn't find. Does anybody know what airport is represented in one of those stock Windows 10 lockscreen ? I mean that screen where you see that doubledecker plane wing and and island group where you can distinguish an airport. It's not Sint-Maarten that's for sure, but I guess it's somewhere in the Carribean too ? Anybody please enlighten me :-) Thanks

I found a fix for the CTD when using the AP assignments. Open the following file in a notepad editor (I use notepad++) Modules\linda\aircrafts\A2A_Piper_PA28_180_Cherokee\actions.lua Find the functions of the Mode switch and the APDisconnect switch, and in both functions, comment the "com.write" line by placing "--" before. See below. Save the file and reload the lua engine or restart FSX. Problem should be gone. I suspect this "com.write" command tries to write to a com port for connected hardware devices like VRInsight or something alike, which I don't have. I'm only using a Saitek X52 Pro and Saitek Rudder Panels. Hope this helps function A2A_ApDisconnectSwitch () --com.write(dev, "A/T__", 8) ipc.writeLvar("ApDisconnectSwitch", 1) _sleep(200) ipc.writeLvar("ApDisconnectSwitch", 0) DspShow ("AP", "disc", "AP ", "disconn") end --- function A2A_ApMode () --com.write(dev, "A/T__", 8) ipc.writeLvar("ApModeYokeSwitch", 1) _sleep(200) ipc.writeLvar("ApModeYokeSwitch", 0) DspShow ("Mode", " ", "AP Mode", " ") -- AP Mode ipc.sleep(100) ApMode = ipc.readLvar("ApMode") if ApMode == 1 then ApModetxt = "ST" elseif ApMode == 2 then ApModetxt = "HD" elseif ApMode == 3 then ApModetxt = "TRKv" elseif ApMode == 4 then ApModetxt = "TRK^" else ApModetxt = "" end DspShow ("Mode", ApModetxt, "AP Mode", ApModetxt) end

I crossed... works so far without any issues :-) Windows 10, FSX-SE

Hello, just recently reinstalled my rig into windows 10 and decided to take the plunge into FSX Steam on it. Installed the latest version of Linda (2.6.3), as I had previously always used v1.xx on my Win7 install. One thing I noticed it that whenever I press and release the configured "Shift" button on my joystick, it now makes a beeping sound, which it didn't do before with Linda v1.xxx Is there any way to disable this ? Thank you. Mathieu

+1 for LINDA

Don't think it says it explicitely, but setting on the standy frequency is available as stated in the manual, so I assume swapping should be too... But setting on standby doesn't work either

Hey, according to the manual, using voice we should be able to command "set xxx.xx on standby comm 1" and then later "swap comm 1", as in the NGX. However I cannot seem to do so, the FO doesn't understand "standby", and neither does he understand "swap comm1". The only thing that seems to work is "set xxx.xx on comm1", which sets comm1 directly without using the standy frequency. Is this a bug or is this due to my system (works perfectly with the NGX) ? Thanks