Skip to content
Paweł Kotiuk edited this page Jan 10, 2023 · 10 revisions

General Help

Adding a New Game Controller Mapping under AntiMicroX
Mouse Settings
Automatically Loading Profiles

Button Assignment Help

Advanced Slot Explanation
Advanced Assignments
Set Selection

Workarounds and fixes for common problems🔧

Fix problems with opening uinput device file

In some cases you can get error:

Could not open uinput device file
Please check that you have permission to write to the device

This is usually caused by lack of udev rule for AntiMicroX.

There may be 3 reasons of this:

  • Device settings are not applied yet. (I recommend restarting PC after installation)
  • You are using version older than 3.1.7 - in this case just update AntiMicroX to the latest version.
  • You installed Flatpak or AppImage version - in case of these packages udev rule can't be added by package and you have to do it by yourself (instruction below).

Adding missing udev rule

You just have do download missing file describing uinput rule

cd /usr/lib/udev/rules.d/
sudo wget https://raw.githubusercontent.com/AntiMicroX/antimicrox/master/other/60-antimicrox-uinput.rules

...and reboot your PC.

Now everything should work fine.

My gamepad/joystick/device is not detected
In this case, you should first check whether this controller is detected by other, similar apps.
On Linux 🐧 you can check qjoypad or jstest-gtx, but the recommended one is sdl2-jstest and controllermap (from sdl2).
On Windows you can use system utilities, Steam, or an application called SDL2 Gamepad Tool (recommended one).
If these apps detect your controller correctly, you can open a bug report for AntiMicroX.

Methods for Disabling Joystick Reading in Linux

Misc

Test Edge Cases

Development guides

Collecting logs
Translating antimicrox 🇬🇧🇵🇱🇩🇪
Coding guidelines
Release checklist