You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem can be reproduced with a generic USB Joystick controller (I don't have any other controllers to test) and with either the 32-bit or 64-bit version of the software. I ran into it while trying to use x360ce with a Steam game that had a semicolon in its name. x360ce refused to work in this particular directory, but worked fine in others, and it took me a long time to find out why...
Steps to reproduce:
Create any directory with a semicolon (;) in its name or rename an existing directory to include this character.
Place the x360ce executable in said directory.
Run x360ce, allow it to create any necessary files.
The "General" tab for the controller is marked with red, the visual cues are grayed out. The controller seems to be completely unrecognized. My controller is a generic gamepad that is normally recognized as "USB Joystick", and in the tab labeled "USB Joystick" I can see that all the input from the controller is being received correctly, but the "General" tab is useless.
I have not verified whether it is just a front-end problem or if it actually prevents the software from working in-game (I tried to run the game and input wasn't working, but that might have been for other reasons, such as the game simply not supporting this way of input). However, the problem is easily reproducible, so I guess it's not that hard to find out.
Perhaps other special characters need to be taken into account as well?
The text was updated successfully, but these errors were encountered:
The problem can be reproduced with a generic USB Joystick controller (I don't have any other controllers to test) and with either the 32-bit or 64-bit version of the software. I ran into it while trying to use x360ce with a Steam game that had a semicolon in its name. x360ce refused to work in this particular directory, but worked fine in others, and it took me a long time to find out why...
Steps to reproduce:
I have not verified whether it is just a front-end problem or if it actually prevents the software from working in-game (I tried to run the game and input wasn't working, but that might have been for other reasons, such as the game simply not supporting this way of input). However, the problem is easily reproducible, so I guess it's not that hard to find out.
Perhaps other special characters need to be taken into account as well?
The text was updated successfully, but these errors were encountered: