You may be able to use some parts of it on the GenX, but as its going to be recognised as a different device, you cant just use the config file I did. You may need to start over and define each axis, button and switch manually. Took me a week for the one I have.
I would suggest starting actually with a fixed wing aircraft so you can see visually on the control surfaces for the basic axis.
Rem out all the auto assigned stuff and leave 1 axis available:-
<axis n="1"> <---------- CHANGE THE NUMBER UNTIL THE CORRECT STICK MOVEMENT IS MOVING THE CORRECT SURFACE
THIS ONE WOULD BE THE TWIST GRIP. Shown here to work up to 3 engines off 1 grip. If your set has 2 twist grips, you can set Engine 0 off the first and the other 2 engines from the second. ( 3 engines as the Merlin has 3 to work with )
Buttons and switches can be hunted down by using and obvious input you can see easily, like landing lights, then you change the property to the command you actually want on that switch:-
Comments
Gone for their PUMA X A-Style - 5th generation USB Joystick - twin throttle, comes with a Airbus style cyclic grip
I have the configs for the Gen IV.
https://drive.google.com/file/d/1zgAKZyR5i4fLK-jVDxeo7jxD3ms4XML3/view?usp=drive_link
You may be able to use some parts of it on the GenX, but as its going to be recognised as a different device, you cant just use the config file I did. You may need to start over and define each axis, button and switch manually. Took me a week for the one I have.
I would suggest starting actually with a fixed wing aircraft so you can see visually on the control surfaces for the basic axis.
Rem out all the auto assigned stuff and leave 1 axis available:-
<axis n="1"> <---------- CHANGE THE NUMBER UNTIL THE CORRECT STICK MOVEMENT IS MOVING THE CORRECT SURFACE
<desc type="string">Elevator</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/flight/elevator</property>
<factor type="double">-1</factor> <----- CHANGE THIS TO REVERSE THE MOVEMENT IF NEEDED
<offset type="double">0</offset>
<power type="double">1.8</power><---- CHANGE THIS FOR SENSITIVITY
</binding>
</axis>
Once you have the correct axis assigned, add the next ones.
<axis>
<desc type="string">Aileron</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/flight/aileron</property>
<factor type="double">1</factor>
<offset type="double">0</offset>
<power type="double">1.8</power>
</binding>
</axis>
<axis n="2">
<desc type="string">Throttle All Engines</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/engines/throttle-all</property> <-- This is the COLLECTIVE for Heli use
<factor type="double">-1</factor>
<offset type="double">0</offset>
<power type="double">1</power>
</binding>
</axis>
<axis n="4">
<desc type="string">Rudder</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/flight/rudder</property>
<factor type="double">1</factor>
<offset type="double">0</offset>
<power type="double">1</power>
</binding>
</axis>
THIS ONE WOULD BE THE TWIST GRIP. Shown here to work up to 3 engines off 1 grip. If your set has 2 twist grips, you can set Engine 0 off the first and the other 2 engines from the second. ( 3 engines as the Merlin has 3 to work with )
<axis n="3">
<desc type="string">Heli Engine power</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/engines/engine/power</property>
<factor type="double">-1.1</factor>
<offset type="double">0</offset>
<setting type="double">-0.8207370043</setting>
<power type="double">1.1</power>
</binding>
<binding n="1">
<command type="string">property-scale</command>
<property type="string">/controls/engines/engine[1]/power</property>
<factor type="double">-1.1</factor>
<offset type="double">0</offset>
<setting type="double">-0.8207370043</setting>
<power type="double">1.1</power>
</binding>
<binding n="2">
<command type="string">property-scale</command>
<property type="string">/controls/engines/engine[2]/power</property>
<factor type="double">-1.1</factor>
<offset type="double">0</offset>
<setting type="double">-0.8207370043</setting>
<power type="double">1.1</power>
</binding>
<low>
<binding n="0" type="string">
</binding>
<binding n="0">
<offset type="double">1</offset>
</binding>
</low>
</axis>
Buttons and switches can be hunted down by using and obvious input you can see easily, like landing lights, then you change the property to the command you actually want on that switch:-
<button n="27">
<desc type="string">Custom</desc>
<repeatable type="string">false</repeatable>
<binding>
<command type="string">property-toggle</command>
<property type="string">controls/switches/landing-lights-switch</property>
</binding>
<binding>
<command type="string">property-toggle</command>
<property type="string">controls/switches/landing-light</property>
</binding>
<mod-up>
<binding type="string">
</binding>
</mod-up>
</button>
Hi Stuart
Many thanks for your detailed reply and your config file.
PS the link you left on FG Forum is broken now
https://forum.flightgear.org/viewtopic.php?f=24&t=12363&p=371316&hilit=puma#p371316
Cheers
Craig
It is but I posted a fresh link in my reply here
Have you finished the config file yet Olly ? The Bossman over at Helisimmer would like a look at it if you have.