Downloaded and installed/rebooted/ uninstalled/reinstalled several times now. Forget about the RXP gauge linkage, the Garmin  6.50 trainer itself doesn't display anything but a black screen. This is on Win 10, the installer was run as administrator, no A/V active. The launcher installation worked fine but that was that. This has never happened before.

17 minutes ago, jabloomf1230 said:

Forget about the RXP gauge linkage, the Garmin  6.50 trainer itself doesn't display anything but a black screen

Hi, do you mean the trainer when running standalone is not displaying, but it is displaying fine in FltSim with our gauge?

Besides, you never should run anything as admin but admin programs, otherwise, like I've said a lot of time in this forum, you are certain to break programs designed for Vista+ like our programs, and like the Trainer!

I usually don't run as admin. I just tried it to see what would happen. Here's an update. I installed  the GTN trainer standalone on my second Win10 PC and it works fine, so I'm baffled.

The only difference is that my primary PC runs at 4k resolution and the 2nd PC runs at 2k.

Edited September 6, 20187 yr by jabloomf1230

Their latest release notes mention something about: "improved support for high-resolution displays"
https://securemanifest.garmin.com/avtrainer/release_notes_2.3.0.0.html

However, how does this run with our gauge instead?

It does work with the RXP gauge, both in XP11 and P3d 4.3, so I'm all set. But why the standalone version doesn't work at 4K is curious. I do have any question, though. The 6.50 GTN trainer installer will delete all gfp files in the FPLN subfolder. Fortunately, I saved a copy of my folder, since I did a clean install of the standalone GTN trainer. Other users might want to preserve their GFP files and do the same.  Also, is the registry location for the FPLN folder location the same in 2.5.4?

I'm glad it is working fine with our gauge then!

The reasons it doesn't run standalone could be multiple, probably their handling of 'high-res displays' has a bug, nevertheless, we are 'controlling' the graphics pipeline so that we shall be immune to any such problem.

As for the FPLN subfolder, yes it is still located in the trainer-created folder, in this case:

"C:\ProgramData\Garmin\Trainers\Databases\FPLN"

To avoid 'deletion', I'd suggest to use the shortcut method though:

1. Create a folder "Documents\GTN Flight Plans" where to copy the flight plan files and user waypoints file.
2. Open "C:\ProgramData\Garmin\Trainers\Databases\", right-click the empty area to the right, select "new | shortcut"
3. Name the shortcut "FPLN" and select the browse button
4. Browse to select the "Documents\GTN Flight Plans" folder and press OK.

Thanks. We'll have to watch and see whether Garmin reproduces the problem with the standalone trainer.

@jabloomf1230
Hi Jay
Regarding the GTN flight plans folder. I also store my GNS flight plans .fpl in the same folder as the GTN flight plans; ...\Documents\Garmin Flight Plans using the shortcut method. Works like a charm.

Edited September 6, 20187 yr by Bills511