Bell UH-1

[IAHM-COL]

If that was all we had to do....

We have to stop the joystick from operating the actual throttle as well.

Not what I've said

My idea is:
1Let the joystick/kboard operate the throttle
Connect throttle to a new inverted parameter; that is inversed throtle; aka collective

[bomber]

So no hotas collective ?

[bomber]

so the only way I've managed to get my joystick working is by copying the joystick file into the -set.xml

Code: Select all

    <input include="keyboard-T4T.xml">
      <joysticks>
         <js>
   
          <name>Saitek X52</name>
          <name>Saitek X52 Flight Controller USB</name>
          <name>Saitek X52 Flight Controller</name>
          <name>Saitek X52 Flight Control Stick </name>
          <name>Saitek X52 Flight Stick (USB)</name>
          <name>Saitek X52 Flight Control System</name>
          <name>Saitek Saitek X52</name>
          <name>Saitek Saitek X52 Flight Stick (USB)</name>
          <name>Saitek Saitek X52 Flight Control Stick</name>
          <name>Saitek Saitek X52 Flight Control System</name>

         <axis>   <!-- 0/0/0 -->
           <desc>Aileron</desc>
           <number>
            <unix>0</unix>
            <mac>0</mac>
            <windows>0</windows>
           </number>
           <binding>
            <command>property-scale</command>
            <property>/controls/flight/aileron</property>
           </binding>
         </axis>

         <axis>  <!-- 1/1/1 -->
           <desc>Elevator</desc>
           <number>
            <unix>1</unix>
            <mac>1</mac>
            <windows>1</windows>
           </number>
           <binding>
            <command>property-scale</command>
            <property>/controls/flight/elevator</property>
            <factor type="double">-1.0</factor>
           </binding>
         </axis>

         <axis>  <!-- 2/2/2 -->
           <desc>Throttle</desc>
           <number>
            <unix>2</unix>
            <mac>2</mac>
            <windows>2</windows>
           </number>
            <binding>
               <command>property-scale</command>
               <property>fdm/jsbsim/fcs/collective-cmd-norm</property>
            </binding>
         </axis>   
   .      
   .      
   .
   .
   .
   .
   .
            </js>
      </joysticks>   
      </input>
         

What I can tell you is that with a joystick it's harder to fly... I've got to work the trim out

Simon

[bomber]

Trims almost worked out....

Can I take it you don't think it's a good solution to have a plane specific joystick.

[IAHM-COL]

not exactly.

If its a workable solution, where you can add modifiers that apply to joystick, and work well regardless of what joystick setting any user has (such as your original intention) -- I think that would work

But if ever user has to modify the set-xml to add their own joystick spec
That's less scalable solution.

I had not even tried how my joystick behaves with your specification

[bomber]

I think with just the two of us, scalability isn't going to be too high a hurdle

[IAHM-COL]

LOL
You made me laugh.
The way you put it, right.

However, the idea of posting on FGMEMBERS-NONGPL is, at least theoretically, to expand the user-base

I'll test the Joystick set tomorrow and let you know
IH

[IAHM-COL]

so the only way I've managed to get my joystick working is by copying the joystick file into the -set.xml

Code: Select all

    <input include="keyboard-T4T.xml">
      <joysticks>
         <js>
   ETC
            </js>
      </joysticks>   
      </input>
         

I dont know if you've pasted the whole js spec here, but it works for me on all axis, except collective. I have no control on it whatsoevr.

[bomber]

No the js code was just an example of where and how I placed the saitek js code that I pulled out of the folder data/input/joystick/saitek

You need to add it all, so as to keep your present joystick configurations but modify axis 2 as below.

<axis> <!-- 2/2/2 -->
<desc>Throttle</desc>
<number>
<unix>2</unix>
<mac>2</mac>
<windows>2</windows>
</number>
<binding>
<command>property-scale</command>
<property>fdm/jsbsim/fcs/collective-cmd-norm</property>
</binding>
</axis>

[IAHM-COL]

Hi @bomber

This strategy did not work for me
I did:

1. Try using all the SaitekX52 spec. No collective on the joy. [stick]
2. Try using all of my joystick spec. No collective on the Joy. [stick]