On ‎9‎/‎21‎/‎2018 at 11:00 AM, reimorei said:

Hi! regarding the flight plans, is there anyway to convert the FSX .pln plans for export to the RXP GNS 530 as it´s much easier to create them on FSX?

Not that I am aware of.  However if you would consider reversing your thought process there is a method to provide your desired result.

Plan flight with an .FPL friendly planning tool------>>>   Import the .FPL file into the GNS  ---->  save the imported .FPL plan from the GNS to Flight Simulator .PLN format

Once that has been done, you can then load the .PLN into the simulator with "Flight", "Flight Planner", "Load".

.FPL friendly flight planning tools include programs like Littlenavmap, and web sites like Skyvector, iFlightplanner, and FltPlan.com.  Personally I find these easier to use to create plans than the simulator flight planner.

Go back to the topics listing here in this Reality XP GNS support forum and look for the pinned topic "Planning and importing Garmin .flt files into RXP v2 GNS".  Read there how to easily create flight plans at three different web sites.  Each site provides a function to save the plans to your system as Garmin GNS .FPL files.  The GNS can import these files once they are saved and moved to the appropriate file location defined in the RXP GNS user guide.  They must be in the defined location for the GNS to see them.

Then there is a setting in the Reality XP GNS that can activate a feature to save a GNS flight plan to simulator .PLN format.  You enter the GNS Settings menu with a shift + right-click on the top of the GNS bezel.  Scroll down the Settings window until you find the Advanced section.  Click the Advanced bullet point to open it, then scroll to find and select "Auto-Save Active Plan (.PLN)".  Once that is selected, a .PLN file is written each time you activate a flight plan in GNS.  It works for any flight plan in the GNS catalog, whether entered manually or imported.  As mentioned above, once saved, the .PLN file can be loaded by the simulator: Flight, Flight Planner, Load.

One last tidbit here.  When you make changes in the Reality XP Settings (shift + right-click on upper bezel) the Settings there are aircraft specific.  So when you move from one aircraft to another you need to make sure you have dialed in the settings you want for that aircraft.

Hope that is helpful.

Edited September 22, 20187 yr by fppilot

2 hours ago, fppilot said:

So when you move from one aircraft to another you need to make sure you have dialed in the settings you want for that aircraft.

And to further help in this process:

1. Load the other aircraft, add a GTN / GNS V2, open the settings panel.
2. Open file explorer and browse to the one aircraft folder you want to copy settings from.
3. Drag and drop the one aircraft RealityXP.GNS.ini file (or RealityXP.GTN.ini for the GTN) onto the opened other settings panel.

5 hours ago, RXP said:

And to further help in this process: 

Uhhh!  That assumes you want and can use all the same settings across those aircraft.   i.e. that the ident = ##### setting(s) is/are the same in all of the different aircrafts panel.cfg files (to match the popleft/popright variables of the .ini file), and that the avionics of each aircraft interface same way with the GNS or GTN...  Is that not true?

Edited September 22, 20187 yr by fppilot

This import only the device settings (GPS, A/P, HSI, VOR, etc..., DB, TAWS mode, TCAS etc..., pilot side, nav/com set, etc....) not the 'window'/'panel' settings!

15 hours ago, RXP said:

This import only the device settings (GPS, A/P, HSI, VOR, etc..., DB, TAWS mode, TCAS etc..., pilot side, nav/com set, etc....) not the 'window'/'panel' settings!

Jean-Luc,
I fully understand that.  What I was pointing out is this. 

If you have aircraft (a) with Ident=15531 in it's panel.cfg file for the gauge's popup [Window##] section, and if you have aircraft (b) with Ident=14432 in it's [Window##] section, then if you copy a RealityXP.GTN.ini file with popright = 15531 from aircraft (a) to aircraft (b),
the ident = 14432 for (b) will not match the value of popright = 15531 for (b).

You never in that example did a thing to either panel.cfg file, but you would have a mismatch in the dependent values and the popup window would not work.

 

Edited September 23, 20187 yr by fppilot

38 minutes ago, fppilot said:

in it's [Window##] section,

Like I've said, drag and drop only copies device settings, not any 'presentation' settings. In other words, it only copies [GNS_530_1] settings, not [GNS_530_1.WINDOW] nor [GNS_530_1.PANEL] !

8 hours ago, RXP said:

Like I've said, drag and drop only copies device settings, not any 'presentation' settings. In other words, it only copies [GNS_530_1] settings, not [GNS_530_1.WINDOW] nor [GNS_530_1.PANEL] !

My Bad. Had to read more closely. I misread. Believed you were saying to drag and drop the entire RealityXP.GTN.ini file from one aircraft's computer subfolder to another.  I had no idea that a RealityXP.GTN.ini file could be dragged from its computer folder to the gauge's open settings window in the sim.  My apology.  And I learned something by reading more closely.

That is a nice feature that I had overlooked in the documentation.

 

Edited September 24, 20187 yr by fppilot