RXP Integration with third party aircraft (A2A, Carenado, etc...)

On 1/4/2020 at 10:11 PM, somiller said:

Indeed, I should have mentioned that in some cases the buttons do require a double click.

Hi,

This is a limitation of the 'binding' used in the non-Reality XP GTN: it uses a simvar to pass information through.

This means the aircraft vendor adds a piece of code which writes a value to the simvar upon button press, then, the gauge reads the simvar and triggers an action depending on the value. Each button+action combination get a unique value for this.

The problem is when you manage to press 2 or more buttons in a row since the last time the gauge has read the value, the gauge will only read the last value set the next time it reads the simvar. In other words: you loose all button clicks but the last one.

This is even more pronounced with knobs which you can turn really fast in a row.

On the other hand, the genuine Reality XP GTN (and GNS V2) are using a 'command' system, which converts any action on the 3D model into an event. This system also queues all events and you never loose any. it is more robust, more versatile, and simpler to implement for 3D modelers.

The XML scripts is a simple 'bridge' which reads the other simvar, and convert the value into a RXP GTN event. It it by definition also limited to the inherent flaws of the 'simvar' approach.