Install Fail

[RXP 2,338]

19 hours ago, DavidP said:

one wonders how the original RXP GNS's were integrated into the VC with full button functionality etc.

At the time, there was 2+1 parts involved:

1) Using shared L:vars to communicate minimum GNS state to the 3D cockpit (knob rotation angle, is the GNS powered or not)

2) Mapping the actual 2D GNS gauge button/knobs clickspots to 3D polygons to make it interactive with mouse clicks.

3) The last one usually is positioning the GNS gauge on the VC panel with coordinates which will make only the screen appear in the middle of the 3D bezel.

 

GNS V2 has a much simpler integration paradigm:

1) It has a complete set of new L:vars. They are also the same set of variables as the ones in our X-Plane version which makes it easier for 3rd party aircraft vendors like Carenado! When I say "complete set of vars", you can look up the list in the User's Manual!

2) Just use the "Use GPS Commands" and you're done with it!

3) Just use the 'nobezel' option and you only have the screen to deal with!

 

NB: the vars are only needed if you want to sync the 2D popup gauge knob rotation with the 3D model knob rotation, or, if you want to query the state of the GNS for 'failure' purposes.

Otherwise, you don't even need variables because our GNS V2 overrides internal simulator variables, which from a 3rd party gauge point of view, is totally transparent a process. For example a gauge reads the following variables: "GPS WP BEARING" or "HSI DISTANCE". When our GNS is the "Master" device - see settings panel -, the gauge reads our GNS data instead of FSim data!

Tip: you can check the link between the GNS and the panel is properly working on the GNS POST page. Select the "Connect GPS to HSI" and "Master Device" GNS option, and see your panel HSI needles properly indicating the expected readouts.

Tip: change your master device between GNS #1 and GNS #2 to make it drive the other gauges, and to make it drive the A/P too!