Per aircraft joystick configuration

[wlbragg]

Is there a way to program joystick configurations on a per aircraft basis. What I am looking for specifically is to be able to configure a joystick (Thrustmaster T.16000M) (left-right twist) to be rudder in a fixed wing aircraft and say a collective in a helicopter. What would be the best way to handle this if FG joystick handler is not capable of doing it on a per aircraft basis?

[wlbragg]

Another question I have that is not totally related to joystick configuration other than it is concerning my new TFRP Rudder Peddles, is normal that the rudder on a helicopter works better in hover than when traveling forward?
In the AirCrane, the ruder left or right, using any control device, doesn't seem to be very strong. You get some amount on the ground and some when hovering or slowly hovering backwards. But as soon as you are traveling forward even at a very low speed, the rudder control appears to be almost ineffective. Is this right?
I haven't compared the AirCrane to any other heli in this regard.

[Thorsten]

But as soon as you are traveling forward even at a very low speed, the rudder control appears to be almost ineffective. Is this right?

Plausible at least - the helicopter is usually aerodynamically shaped, so if you have forward velocity there would be a force acting to minimize beta - which is not there in hover. This beta-nulling force you fight with the rudder.

[wlbragg]

if you have forward velocity there would be a force acting to minimize beta - which is not there in hover

Makes sense and fits what I am experiencing. After more time using the joystick/foot peddle combination I think I am getting the hang of it. What a difference it makes to have better control hardware. An easily controllable rudder make a world of difference in realism. Not to mention it makes flying more enjoyable and rewarding.

Joystick API needs extended to save per aircraft configurations.

[Alant]

Hiding in the forum at https://forum.flightgear.org/viewtopic.php?f=24&t=12363&start=30#p166591 is this code snipet which makes special joystick flap control for the F14b.
Hope this helps.
Alan

Code: Select all

<button n="5">
   <desc>Step towards landing configuration</desc>
   <repeatable type="bool">false</repeatable>
   <binding>
      <command>nasal</command>
      <script><![CDATA[
         # Step towards landing configuration:
         var popupTip = "";
         var path = getprop("/sim/model/path");
         var jsbtailhook = getprop("fdm/jsbsim/systems/hook/tailhook-cmd-norm");
         var tailhook = getprop("/controls/gear/tailhook");
         if (path == "Aircraft/f-14b/Models/f-14b.xml") {
            var flaps = getprop("/controls/flight/flapscommand");
            f14.lowerFlaps();
            if (getprop("/controls/flight/DLC-engaged") == 0) {
               f14.toggleDLC();
               popupTip = "DLC ENGAGED";
               setprop("/controls/flight/DLC", 0);
            }
         } else {
            var flaps = getprop("/controls/flight/flaps");
         }

[wlbragg]

Interesting, I get it. I figured it would take something like that. Even something as simple as executing a nasal command, say autostart, is potentially tied to the aircraft unless taken into account.

Example developers need to consider (especially me)...

Code: Select all

<nasal>
  <c172p>
    Nasal/autostart.nas
  </c172p>
</nasal>


or for AirCrane

Code: Select all

<nasal>
  <aircrane>
    Nasal/autostart.nas
  </aircrane>
</nasal>


Requires special handling in js config to look for either
c172p.start();
or
aircrane.start();
If autostart.nas was configured instead to be

Code: Select all

<nasal>
  <autostart>
    Nasal/autostart.nas
  </autostart>
  <aircrane>
   ...
  </aircrane>
</nasal>


Then js config call to autostart.start() just works for both.

[LesterBoffo]

If this is a YAsim aircraft you can "model" the side area of a fuselage, (say the tail cone of the rotor mast...) by adding cy="x.xx" entries for each segment of the fuselage you want to change. Works the same for fixed wing aircraft.

Code: Select all

 <!-- Tail -->
  <fuselage ax="-3.892" ay="0" az="-0.09"
  bx="-8.562" by="0" bz="0.297"
  width="0.9" taper="0.63"
  midpoint="0" cx="0.5"
  cz="0.125"
  idrag="0.07"/>