evdev-joystick.tar.xz in Stella

polish.potato

I am not having a clue how to use this file to use it for my paddles on my raspberry pi 3. I currently have a 4.3 for the Retropie. I am getting clipped on the left of the screen. Everything is fine besides that. Where do I put the file? I've read how to extract it but I don't have the slightest clue what to do.

Any help will be appreciated. Thanks.

reply

ducky

First uncompress the archive with:

tar xf evdev-joystick.tar.xz

You should then have a folder with a README.TXT file. That should walk you through the rest of the setup.

polish.potato

I did that but I quite don't understand the instructions. I am unfamiliar with how to do this. I'm a noob when it comes to this stuff.

polish.potato

The text is as follows:

EVDEV-JOYSTICK

This program is based on G25manage, located at:
https://github.com/VDrift/vdrift/tree/master/tools/G25manage

It is developed by Stephen Anthony, and released under the GPL/v2.

evdev-joystick is used to set the deadzone for Linux 'evdev' joystick devices.
Currently, other than G25manage there is no other standalone program available
to perform such calibration. This program was originally developed for Stella
(stella.sf.net), an Atari 2600 emulator, and as such much of this document
refers to Stella. The program itself can be used to calibrate any joystick
for any application, though, and is not specific to Stella.

Short Explanation (Stella users with Stelladaptor, 2600-daptor, etc.)

Decompress the archive
Build the application by typing 'make'
Install it by typing 'sudo make install'
Unplug your 'daptor device, re-plug them, and play a game.

Long Explanation (For the curious, or if something doesn't work, etc.)

Decompress the archive
Build the application by typing 'make'
Type './evdev-joystick --l'. For me, it produces output as follows:

/dev/input/by-id/usb-Microsoft_Inc._Controller_101F9B0-event-joystick
/dev/input/by-id/usb-Microchip_Technology_Inc._2600-daptor_II-event-joystick
/dev/input/by-id/usb-RetroUSB.com_SNES_RetroPort-event-joystick

Make note of the name of the device. For 2600-daptor II users, this
would be:

/dev/input/by-id/usb-Microchip_Technology_Inc._2600-daptor_II-event-joystick

Check the current deadzone (known as 'flatness') by typing:
'evdev-joystick --s <NAME_OF_DEVICE>'
Again, for me, this will output the following:

Absolute axis 0x00 (0) (X Axis) (min: 0, max: 4095, flatness: 128 (=0.00%), fuzz: 15)
Absolute axis 0x01 (1) (Y Axis) (min: 0, max: 4095, flatness: 128 (=0.00%), fuzz: 15)
Absolute axis 0x02 (2) (Z Axis) (min: 0, max: 15, flatness: 0 (=0.00%), fuzz: 0)

Notice that the flatness/deadzone for axes 0 & 1 is 128.
Now, we change the deadzone by typing 'evdev-joystick --s <NAME_OF_DEVICE> --d 0'
Now check the current deadzone again by typing:
'evdev-joystick --s <NAME_OF_DEVICE>'

Absolute axis 0x00 (0) (X Axis) (min: 0, max: 4095, flatness: 0 (=0.00%), fuzz: 15)
Absolute axis 0x01 (1) (Y Axis) (min: 0, max: 4095, flatness: 0 (=0.00%), fuzz: 15)
Absolute axis 0x02 (2) (Z Axis) (min: 0, max: 15, flatness: 0 (=0.00%), fuzz: 0)

Note that the 'flatness' has changed to 0? If so, then the program is
working as intended.
Note that there are other options to the program. You can change the
'fuzz' value, change attributes for only certain axis, etc. See the
options by typing 'evdev-joystick'.
Once you're certain that the application is working, type 'sudo make install'
to install it.

RULES File

Included in the archive is a udev .rules file that will automatically run
evdev-joystick with the correct parameters for a Stelladaptor, 2600-daptor,
and 2600-daptor II. If you have another joystick you wish to modify,
simply add the proper entry to the .rules file. Note that it is necessary
to add all joysticks (where you want to change the deadzone) to this file,
since the settings are lost when the device is unplugged and plugged in again.
When using a .rules file, the system will automatically re-run evdev-joystick
and set your deadzone values again.

polish.potato

NOW... I just want to know where to place it in the card and where to write the command. Do I quit emulationstation and write the command? I don't want to mess anything up.

edmaul69

@polish-potato so out of curiosity what do you mean by your getting clipped?

polish.potato

On the side of the screen. I am using 2600-daptor 2. Tell me am I crazy? It seems to be on the side left of the screen

polish.potato

Contacted 2600-daptors manufacturer and he said:

The problem is a "deadspot" on the left side of the screen. When you reach that spot, the player will stop moving, though if you keep turning the paddle, the player will resume moving again after a bit.

I don't have raspberry pi handy, so I can't give you step by step instructions. Basically you download and uncompressed the files to get them on the memory card. It includes a "readme" file with instructions on how to then install it.

Tom

So yes, it is a problem! Can someone tell me what to do please?

polish.potato

Hi I am back with questions.

How do I do these steps? Help would be much appreciated.
2) Build the application by typing 'make'
3) Install it by typing 'sudo make install'

Thanks guys.

mediamogul

@polish-potato

Assuming you're following directions that told you to do this, navigate from the command line using cd to whichever directory contains the source you want to build. From there you should be able to type 'make'. Once completed, you can then type 'make install'.

polish.potato

I did all that when it was being compiled it gave me an error. I opened the folder like you said and typed make but when it loaded everything it gave me three errors. I'll try to dl again and try again. It'll Probably be the same thing.

I don't know if I am imagining things but the paddles don't seem to be sticking on this version maybe it's my imagination.

mediamogul

@polish-potato said in evdev-joystick.tar.xz in Stella:

I don't know if I am imagining things but the paddles don't seem to be sticking on this version maybe it's my imagination.

The issue with paddles sticking to the sides was actually solved in version 4.7. From there on, each game has a set movement range based on an internal database and can be adjusted on a game-by-game basis from the 'Game Properties...' menu.

polish.potato

Thanks that's all I needed to hear.