RE: The latest version (v1.478) can not find usb controller - 2

Hi,

finally I have got to work my transmitter working as well. Unfortunately the controllermap doesn't recognize when I move with the sticks. But anyway at least I obtained the guid of the transmitter. Which is in my case:

03000000f70600000300000010010000
 

.

I have installed joystick package

sudo apt-get install joystick
 

I have found out that the transmitter is mapped to /dev/input/js0 so I have ran

jstest /dev/input/js0
 

Here I found out, wich axis are used for pitch, yaw, throttle and roll and used these values to set in SDL_GAMECONTROLLERCONFIG. In my case it was pitch:1, yaw:5, throttle: 2 and roll:0. So the value of SDL_GAMECONTROLLERCONFIG in my case is:

"03000000f70600000300000010010000,WAILLY PPM,platform:Linux,leftx:a5,lefty:a2,rightx:a0,righty:a1,"
 

I think that it doesn't matter, how it's mapped, but important is that the right axis are mentioned there. The right mapping is done in sim anyway. Then just set the env variable before running neXt sim through the command:

export SDL_GAMECONTROLLERCONFIG="03000000f70600000300000010010000,WAILLY PPM,platform:Linux,leftx:a5,lefty:a2,rightx:a0,righty:a1,"
 

. You can place it in .bashrc file as Klaus did or you can run it in terminal from which then you run the sim.

Hi

How can we map more than 4 analog axes? Controllermap can handle only 4. If a switch should be used for autorotation it has to be mapped to a RCx channel not to a button.
Thats because next can only use RCx channels for that purpose.

Regards
Dieter

Zitat von Klaus-Eiperle im Beitrag #16

---

here is the solution for ubuntu and a real flight controller:

...
===

$ ./controllermap 0

After some trial and error with the interface, I was able to get all of
my switches and the reset button mapped properly and I was able to get
all four stick axes mapped. I was unable to map the dial on the
Interlink to anything but I don't think that matters at this point (at
least I don't use it with neXt...)

...
===

---

Zitat von Klaus-Eiperle im Beitrag #20

---

Unfortunately I have no experiences with Linux and I don't test on Linux anything.

---

SAILI Simulator --- XTR5.5+G2+FMS Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14:1.1/0003:0B9B:4012.001A/input/input31

is not recognized by 1.497.

I have tried
~/Downloads/sdltest/sdl-jstest/build $ ./sdl2-jstest -l
Found 1 joystick(s)

Joystick Name: ' SAILI Simulator --- XTR5.5+G2+FMS Controller'
Joystick GUID: 030000009b0b00001240000011010000
Joystick Number: 0
Number of Axes: 4
Number of Buttons: 4
Number of Hats: 0
Number of Balls: 0
GameController:
not a gamepad

STEAM (big picture mode) the controller is recognized, but does not "work" as a button-type game controller, obviously not set up to use analog inputs.

Unity does not seem to be too concerned about this?

Starting game from console it complains about:

Preloaded 'ScreenSelector.so'
Unable to preload the following plugins:
ScreenSelector.so
Player data archive not found at `/home/user/Downloads/cgm-rc-heli-simulator-linux-x86-64bit-1497/Linux x86+64bit/neXt_Data/data.unity3d`, using local filesystem

After installing "apt-get install joystick" i ran:

~/Downloads/sdltest/sdl-jstest/build $ jstest /dev/input/js0
Driver version is 2.1.0.
Joystick ( SAILI Simulator --- XTR5.5+G2+FMS Controller) has 4 axes (X, Y, Rz, Throttle)
and 4 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn).
Testing ... (interrupt to exit)
Axes: 0: 14863 1: 0 2: 0 3: 0 Buttons: 0:on 1:off 2:off 3:off

Correctly recognized 4 axes and a button. 0=thr, 1= elev, 2=ruddr, 3=ailerons,

Zitat von reginar im Beitrag #23

---

Starting game from console it complains about:

Preloaded 'ScreenSelector.so'
Unable to preload the following plugins:
ScreenSelector.so
Player data archive not found at `/home/user/Downloads/cgm-rc-heli-simulator-linux-x86-64bit-1497/Linux x86+64bit/neXt_Data/data.unity3d`, using local filesystem

---