I'm currently using vector to play some games that require joysticks.
If I calibrate / configure a joystick, both "js#" and "event#" files in "/dev/input" are generated.
Strangely, the games do not pick up new mappings / configurations if the associated "event#" files exist.
However, if I run calibration / configuration, delete the new "event#" files (leaving only the "js#" files), the mappings are picked up by the game correctly.
To summarize, the joystick "/dev/input/event#" files are causing conflicts with the "/dev/input/js#" files.
While I can write a script to just delete the related event files, the generated event files are not created at the same time as the js# files. They seem to generate about 0.1 second after the js# files are created. Not a huge deal but I have to use a quick loop to wait for the generation. It would be preferable if I could stop the generation of the event# files compeltely.
By posting, I'm primarily trying to gain an understanding of the event file creation process. Can anyone explain the event file creation process? Which process or resource creates the joystick event# files and why would they conflict with the related js# files? Am I able to prevent the event# files from being created?