Hi

 

I know it has been some time but I just wanted to thank @dougfir for continuing pressing this issue until he was able to find a solution. I had the same issue and because of this topic I finally was able to solve the "missing import" button mystery 🤔 .

What I suggest to @RXP is to update their User Guide and have a better explanation of this procedure and how to troubleshoot it.

If the following was part of the troubleshooting from the beginning I would not have wasted at least 2 hours trying to figure out what am I doing wrong, although the fault is in the Fuxxxing Manual  🙄.

 

This is what should have been in the first place in the "where to place your flight plan files".

Quote

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Garmin\Trainers]
"DataPath"="C:\\ProgramData\\Garmin\\Trainers\\"
"BinPath"="C:\\Program Files (x86)\\Garmin\\Trainers\\"
"DBDataPath"="C:\\ProgramData\\Garmin\\Trainers\\Databases\\"
"LauncherDataPath"="C:\\ProgramData\\Garmin\\Trainers\\Launcher\\"
"TXIDataPath"="C:\\ProgramData\\Garmin\\Trainers\\TXI\\"
"GTNDataPath"="C:\\ProgramData\\Garmin\\Trainers\\GTN\\"

Check your registry if values are the same, if not then use your registry folder path instead

You should also state that this is the default expected location, but if you installed your trainer or what ever part you call it into a different folder (like myself) then you should check your registry for the "GTNDataPath" value or "gsn..." one depending on your product.

In my case, it seems that I installed my trainer in "G:\sim\Garmin" folder and all relevant folders were created under it. This means that the User Guide pointing to a folder in "C:\\ProgramData\\Garmin\\Trainers\\GTN\\" is misleading (my database folder is: "G:\sim\Garmin\data\Trainers\Databases\").

I currently see the "[import]" button but I just want to say that it is disappointing that even after figuring out the root cause, presented in this thread, the User Guide has not been updated accordingly to reflect the correct troubleshooting of this issue.
I believe that if you will add a short troubleshooting for all users with this specific issue at hand, they will solve it immediately. Even more, you should write the folder the plugin searches for the "FPLN" location into the "/Documents/rxp{NAME}.log" file even if it is not a debug build, it could have saved lots of headache.

 

Hope something better will come from this thread for the customer sake.

Cheers

 

 

 

 

 

 

 

 

@snagar thank you for your suggestions.

It is true we're not explicitly telling the paths illustrated in the User's Manual are the default ones, and they obviously would not longer be relevant if the user knowingly changes the default during installation. Worth adding in the next update.

I like you idea of at least writing out expected path for the FPLN, like we already do for the checklist file if found, and the trainer path if superseded with the environment variables.