Linux Joystick Mapper Activity
Status: Beta
Brought to you by:
alexandrehardy
Activity for Linux Joystick Mapper
-
Alexandre Hardy modified a wiki page
Home
-
Home
-
Linux Joystick Mapper released /joymap-0.5.7.tar.gz
-
Fix instance with shift
-
Update documents for controller instance
-
Add instance with shift
-
Fix blocker code
-
Handle multiple controllers better
-
-
Cleanup joymap_blocker
-
Always write the PID file to make kill always work
-
Add a library to limit joystick access to only joymap devices
-
Make skipping axes optional
-
-
Fix removal of device due to incorrect vendor and product
-
-
Only report declared axes
-
Fix multiple devices with same vendor and product id
-
Don't register code device if there is no code
-
Add kill command line argument
-
Home
-
-
More documentation fixes
-
Fix handling of shift in flags, when it is on its own
-
Increase number of axes to accomodate second hat
-
Add a link to the UI project by Rens
-
Documentation fixes
-
Home
-
-
Fix auto calibrate
-
Fix man page
-
Hi James, This bug should be fixed in joymap-0.5.0. joymap-0.5.0 also adds a few other options; * Ability to specify a joystick by event device number instead of vendor and product. * Daemonize option, to run the program in the background. * Handles removal and insertion of devices at runtime (no need to have the devices plugged in before you start). * You can now provide a search path for configuration files in the JOYMAP_PATH environment variable so config files don't have to use absolute paths...
-
-
Hi! joymap-0.5.0 now supports use f the "id" keyword for mapping the joysticks. The Id corresponds to the event device associated with the device. For example, if event6 is listed as a handler for the device in /proc/bus/input/devices, then you can specify id=6 in the mapping file. If you specify the id, then you should not specify the vendor and product id. joymap-0.5.0 supports plugging in and out of devices, but if you use the id, then you may find a new event kernel device has been allocated...
-
-
Update document
-
Honour the event id
-
Tabs to spaces
-
Calibrate calues based on input reporting on axes values, if requested
-
Update documentation
-
Update makefile to cleanup correctly
-
Support loading files relative to map file, and based on path
-
Fix tabbing
-
Move config away from loadmap to single handler
-
Handle locking of devices correctly
-
Replace tabs with spaces
-
Handle devices plugged in after launch, and display input events for programming
-
Fix shift button
-
Change max events for modern kernels
-
Fix mouse wheel events
-
Fix button/key releases for axis mapping
-
Fixes, because I wasn't testing :-(
-
Adjust mouse speed for new assumptions about axes
-
Add min, max, deadzone and also the trinary flag
-
Move install_event_handlers back again. No idea why I moved it in the first place
-
Recompile program.pdf
-
Pull in osxjoymap changes
-
Added comment about timing
-
Update README
-
Fix mouse button presses
-
Reduce the number of axes on the Code joystick
-
Don't die if we can't grab the device
-
Remove trailing whitespace
-
Fix error messages reported by Wall
-
Correct setup for joystick code device
-
Catch more errors
-
Add cmdline matching for config
-
Safeguard opens...
-
Change tabs to spaces
-
First pass at adding configuration
-
More configuration
-
Update makekeys.sh
-
Alexandre Hardy committed [2cb6ab] on Git
Added dynamic calibration of outputted events
-
Alexandre Hardy committed [a80092] on Git
Add 8-bit to 16 bit event mapping
-
Added sync events to each event sent.
-
Alexandre Hardy committed [696312] on Git
Initial creation of project
-
Hi! The original joymap code was actually designed for my own use, and thus has some shortcomings when it comes to duplicate devices. The original design goals: 1. Consistently identify devices in a HOTAS setup (joystick, throttle and rudder pedals) even after reboots and hotplug events. 2. Allow programmability of targets. That is a very broad statement, and was never written down. But the point was to identify devices by their vendor and product id so that the software tolerates reboots and hotplug...
-
Hi! The original joymap code was actually designed for my own use, and thus has some shortcomings when it comes to duplicate devices. The original design goals: Consistently identify devices in a HOTAS setup (joystick, throttle and rudder pedals) even after reboots and hotplug events. Allow programmability of targets. That is a very broad statement, and was never written down. But the point was to identify devices by their vendor and product id so that the software tolerates reboots and hotplug events...
-
Norbert Harrer posted a comment on a wiki page
Hi. Awesome tool. I am struggling a bit with how to differentiate two identical controllers. In /proc/bus/input/devices: I: Bus=0006 Vendor=0002 Product=0001 Version=0100 N: Name="Multisystem joystick" P: Phys=input0 S: Sysfs=/devices/virtual/input/input2 U: Uniq= H: Handlers=event2 js0 B: PROP=0 B: EV=b B: KEY=1 0 0 0 0 0 0 0 0 0 B: ABS=3 I: Bus=0006 Vendor=0002 Product=0001 Version=0100 N: Name="Multisystem joystick" P: Phys=input1 S: Sysfs=/devices/virtual/input/input3 U: Uniq= H: Handlers=event3...
-
Anthony S modified a comment on a wiki page
Hi Stephen thanks for that, my gamepad's HAT is also being mapped to axis 16 and 17, and it too has three values -1, 0 and 1. I assumed that the 3 and 4 axis values reported by jstest were correct, but then I added your code and saw in stderr that they were in fact 16 and 17. In any case I didn't need to remap the values I used the following in my map for things to work correctly for me. How come you're re-mapping the values to 0, 128 and 255? axis vendor=0x2dc8 product=0x2865 src=17 target=kbd minus="up"...
-
Hi Stephen thanks for that, my gamepad's HAT is also being mapped to axis 16 and 17, and it too has three values -1, 0 and 1. I assumed that the 3 and 4 axis reported by jstest was correct, but then I added your code and saw in stderr that they were in fact 16 and 17. In any case I didn't need to remap the values I used the following in my map for things to work correctly for me. How come you're re-mapping the values to 0, 128 and 255? axis vendor=0x2dc8 product=0x2865 src=17 target=kbd minus="up"...
-
Stephen Anderson posted a comment on a wiki page
Good to hear. I mapped the values to 0, 128, 255 to replicate function of other axis. From memory the direct mapping was not working for me.
-
Hi Stephen thanks for that, my gamepad's HAT is also being mapped to axis 16 and 17, and it too has three maps to three values -1, 0 and 1. I assumed that the 3 and 4 axis reported by jstest was correct, but then I added your code and saw in stderr that they were in fact 16 and 17. In any case I didn't need to remap the values I used the following in my map for things to work correctly for me. How come you're re-mapping the values to 0, 128 and 255? axis vendor=0x2dc8 product=0x2865 src=17 target=kbd...
-
Anthony S, regarding the HAT not working. Did you notice anyone having trouble with getting HAT buttons working ? Hope it may assist.
-
Just wanted to share my post on reddit on how to setup Linux Joystick Mapper with DOSBox on RetroPie 4.7.2 https://www.reddit.com/user/ajscilingo/comments/kmn5nw/configuring_dosbox_to_work_with_linux_joystick/ Hope this helps someone looking to use this project with DOSBox on RetroPie... Edit Still haven't managed to get the HAT working on my controller but maybe someone can add on to this?
-
Just wanted to share my post on reddit on how to setup Linux Joystick Mapper with DOSBox on RetroPie 4.7.2 https://www.reddit.com/user/ajscilingo/comments/kmn5nw/configuring_dosbox_to_work_with_linux_joystick/ Hope this helps someone looking to use this project with DOSBox on RetroPie.
-
Shawn posted a comment on a wiki page
I am trying to get this to work with a Hotas Warthog. I am having problems just mapping the axis through... I want to use this tool to combine some saitek rudder pedals with the warthog so I can have one virtual stick I could use in space sims like freespace 2 open. But when I just try to map the axis straitfowardly like: axis vendor=0x044f product=0x0402 src=0 target=joyaxis axis=0 axis vendor=0x044f product=0x0402 src=1 target=joyaxis axis=1 axis vendor=0x06a3 product=0x0763 src=2 target=joyaxis...
-
I am trying to get this to work with a Hotas Warthog. I am having problems just mapping the axis through... I want to use this tool to combine some saitek rudder pedals with the warthog so I can have one virtual stick I could use in space sims like freespace 2 open. But when I just try to map the axis straitfowardly like: axis vendor=0x044f product=0x0402 src=0 target=joyaxis axis=0 axis vendor=0x044f product=0x0402 src=1 target=joyaxis axis=1 axis vendor=0x06a3 product=0x0763 src=2 target=joyaxis...
-
Francis Serrano posted a comment on a wiki page
Thank you so much for this driver Mr. Hardy! This script is incredible for mapping to my PS3 Controller into the PiFBA Emulator on RetroPie in my old Raspberry Pi Model B rev.1.2. It works finely with one player, but I want ask you how can I configure the map file for map my keyboard to the two same PS3 Controllers. The provider ID and product ID are the same, only change his Handlers (js0,js1,event0, etc). I tried adding id=0, id=1 and device=0,device=1 to the map file but not working. Thank you...
-
DaveHkent posted a comment on a wiki page
Thanks, I will try the shift button first. The game I have been working with is Worms, where you use the mouse to pan round the screen to decide who to shoot then it is all keyboard from there. Using shift and the ABXY buttons to pan is no big deal. I might try the code too then post the results of both here for others to find.
-
Hi Dave, The "shift" button can be used to change behaviour based on whether that button is pressed or not. However, that only applies to buttons and not to axes. You can achieve that effect by writing a "script". Use the "code" directive (to specify the program to execute) as well as "script" directives (to tell joymap how it should present your joysticks to the program) and then you can implement the switch between buttons an axes in code. Perhaps something like: if (js1.b[2]) { a[0] = 128; } else...
-
I have just discovered this project while setting up a number of dos games for RetroPie, and it looks very good. Is it possible in any way for the axis buttons to behave like the cursor keys (that bit I have working), but behave differently, e.g. like a mouse when another button is held down? I have a basic SNES style controller and for one game this would kill off the need for the wireless mouse.
-
jonas posted a comment on a wiki page
i know its a bit outdated, but here is my map for Worms Reinforcements (1996) for "Dragonrise inc, generic usb joystick", similar PS2 gamepad. Thanks to all of you!
-
TZF modified a comment on a wiki page
hi Alexandre, thanks for this amazing piece of software, It really saved me a lot of pain and time in setting up my joystick for emulating mouse under DosBox. I attach here three different map files (tested) to use with the excellent Logitech Wireless Game pad F710 https://tinyurl.com/y7oymfz4 They are well commented, should be a breeze to customize them for your own use. Please note that they will likely work with Logitech Wireless Game pad F710 only ================================================================...
-
hi Alexandre, thanks for this amazing piece of software, It really saved me a lot of pain and time in setting up my joystick for emulating mouse under DosBox. For whoever might find them useful, I prepared and tested three different map files to use with the excellent Logitech Wireless Game pad F710 https://tinyurl.com/y7oymfz4 Attaching all three map files here, hope you'll find them useful. They are well commented, should be a breeze to customize them for your own use. Please note that they will...
-
hi Alexandre, thanks for this amazing piece of software, It really saved me a lot of pain and time in setting up my joystick for emulating mouse under DosBox. I have prepared and tested three different map files to use with the excellent Logitech Wireless Game pad F710 https://tinyurl.com/y7oymfz4 Attaching all three map files here, hope you'll find them useful. They are well commented, should be a breeze to customize them for your own use. Please note that they will likely work with Logitech Wireless...
-
hi Alexandre, thanks for this amazing piece of software, It really saved me a lot of pain and time in setting up my joystick for emulating mouse under DosBox. I have prepared and tested three different map files to use with the excellent Logitech Wireless Game pad F710 https://tinyurl.com/y7oymfz4 Attaching all three map files here, hope you'll find them useful. They are well commented, should be a breeze to customize them for your own use. Please note that they will likely work with Logitech Wireless...
-
Third attachment: mouse.map - configured to simulate mouse only (both left and right sticks are used as mouse)
-
Third attachment: mouse.map - configured to simulate mouse only (both left and right joystick are used as mouse)
-
Second attachment: joy-mouse.map - configured to emulate a mouse (right analogue stick) and joystick/keyboard (left stick). This is optimal for games using both keyboard / mouse
1 >