fppilot

Good results?

Totally false! Absolutely! Check out the Reality XP support forums here on Avsim. Then do a Google search for F1 GTN support......

Commodore 128. Wow. Remember this one? It was what I first flew FS with. It was based on a Motorola CPU. I recall doubling the memory by piggybacking the 8 ram chips, placing a spot of solder to join each of 7 pins in the stacks, and bending up the last pins and soldering them together with segments of wire. I was the 2nd owner of an original IBM-PC in the state of Oklahoma. The Oklahoma City Computerland franchise owner was the first. Was at his store's front door when he opened on a Monday morning, the day after the IBM announcement was in the Sunday Paper.

Try Alt-Tab a time or two and see if you have a dialog box waiting for a response but hiding behind other boxes. I have had that happen before during software installations.

I use what you are using. Windows 10 Defender and Malware Bytes Premium. I have real time time scanning on for both. I have used this combination since Fall of 2015 when I built this current system. It has been perfect. I will use the same combination with my new system come this Fall. When I fly I reboot and close every start up program except Defender before I load the simulator.

That's just where I am at. Can double that for about $10 more per month, but have so far not found the need.

By the way Tom. See you have just passed your 10 year anniversary here! Happy Anniversary. Join us more often here. There is great user-to-user communication here. Some better, some not so much. But overall its flaps-down the premier simulation site. And RXP support here has been great over the past few years. Don't be a stranger... LOL

It does indeed seem obvious does it not? Consider that the GTN has the features and capabilities to handle more complex flight plans. The GNS had the ability to handle most of those on-the-fly (procedures) but not during the initial flight planning process, or when storing flight plans. Sometimes developers get so enamored with their enhancements in new models that they ignore backward compatibility. Still, consider that to import your stored GNS plans into the GTNs, you would be lacking the same route enhancements that I have learned to avoid during the import process because of Garmin's screening of GTN plans that include transitions, approaches, and runways. I got very adapt at entering flight plans quickly into RXP GNS gauges, and have amazed two pilots with GNS installations that I take ride alongs with. But speed with manually entering GTN plans is just flat-out faster. I can enter them much faster than I can plan the flights at flight planning sites. And much faster than attempting importing them. I, like you, wish that major real-world flight planning sites would provide GTN flight plan exports like the exports they provide for GNS, but the filtering that the Garmin's put the plans through, especially when containing transitions, offsets any advantage hoped to be gained with importing. Lesson well learned.

Tom. Perhaps I was not clear. But the very first part of my reply was this: "The GTN devices are very different in ability and the file formats for importing flight plans is totally different. Create a flight plan somewhere and export it to GNS (.fpl format). Then create it in a source that provides GTN export (.gfp format). Open each with a text editor and you will immediately see the difference." But Bert's response perhaps reveals a way to accomplish it. Through a setting you can set your RXP GNS to save a flight plan as a .pln file just upon activating the flight plan in the GNS. On page 12 of the current RXP GNS User's Guide you will find: ==================== Auto-Save Active Route Select if the device saves the active route to a file when it changes. The file will be saved to: “My Documents\Flight Simulator Files\Reality XP GNS# Route.pln” ==================== So you can load a flight plan in the GNS and if that option is set when you activate the flight plan the GNS will save it as a .pln file. Then perhaps you can load the.pln file into Little Navmap. Then from there save it as a .gfp file for the GTN. Then try to import it. It still takes manipulation similar to what you wish to avoid. I am not aware of anything that will do it for you. That manipulation still may take longer than just entering the flight plan from scratch into the GTN. Did you open.flt and .gfp files and look at both? I have vast experience with trying to create a similar method with flight plans from both Skyvector.com and Fltplan.com. I tried such a process with an Excel spreadsheet to build the string you see below in yellow from the string you see in red text The red text string came from either Fltplan.com or Skyvector, Would copy and paste the text string of the flight plan from those sources, parse the line into Excel to separate into cells, then from there I had to paste the text string into notepad, then save it as a .gfp file. Then I had to keep my fingers crossed when importing into the GTN. The Garmin filters are strict. Click for larger image.

Tom, The GTN devices are very different in ability and the file format for importing flight plans is totally different. Create a flight plan somewhere and export it to GNS (.fpl format). Then create it in a source that provides GTN export (.gfp format). Open each with a text editor and you will immediately see the difference. If you scan the topics here under the RXP GTN Forum you will find a number of posts and replies I have made about my experiences with flight plan imports. One important difference is that the GNS series you have experience with does not have the capabilities to use airways. The GTN does. It makes it much easier to enter flight plans into the GTN. Instead of intersection or VOR --to-- intersection or VOR, with the GTN you are able to pick your entry point onto an airway, then from that point in the flight plan tell the GTN to load an airway. It only shows you airways containing that entry point. Then you pick your exit point from that airway, and repeat the process down the line. No need to enter each point along the airway like is required by the GNS. The GTN format allows you to add in route enhancements like departure runway, departure procedure, transition to airway, arrival, approach, and even approach runway. As beautiful as that sounds, all of it has to be precisely right or the GTN chokes on it during the import. I spent hours attempting to perfect my ability make the import process "dance" like I wished. I finally found it easier, and much quicker, to just create the flight plans in the gauge itself. I did build a catalog of my often used flight plans in .gfp format for importing, but I found I had to keep them very basic to avoid import hiccups. I will send you a Private Message here with something I wrote last week about it.

The price point and finding a seller who accepts returns are the key. I sold a 560ti to a happy customer when I bought the 970 new in 2015. I will be selling the 970 soon. I keep my GPU and my overall system as well very clean. Use a micro vacuum tools kit and a lot of care. Just totally cleaned my Corsair H100i Cooler a couple of weeks ago when under the right light I saw how much dust had built up in it's radiator fins. That despite filters and my frequent cleaning of the system, enclosed in a Mastercase Pro 5 case.

I picked up a used GTX 1080 TI Turbo 8 gb for $300 US to replace my GTX 970 4 gb and am thrilled with in for the meantime as I await more hotfixes for P3Dv5 and or MSFFS 2020. Am still hanging out with FSX and lots of addons.

+1

The Add-On Manager issue may be related to FSDT installations. Just one thought. A Google search for FSX and ntdll.dll immediately brought up this topic, which started back in 2016 before the RXP GTN was even available. I saw links to the issue from as far back as 2012. It appears solutions vary a good bit from user to user. I'd try the most simple first...

That is just flat our wrong. Did you intend to instead say updated databases must come from Garmin? That is correct. That is much different from saying "units can definitely not be updated by anyone other than Garmin". I have not had to send my units to Garmin to get them updated.