GIMX 1.00
Posted: Sat Feb 23, 2013 6:02 pm
GIMX was deeply modified for this release. Expect a few bugs!
Save your configs before upgrading to this version.
In case of critical issues, just downgrade to version 0.51.
Please report issues through the googlecode page: link.
Note for Raspbian users: my Raspberry Pi is broken... so there sadly is no package yet.
Windows users have to move the config directory to C:\Users\<username>\AppData\Roaming\emuclient\config.
Linux users have to move the ~/.sixemugui directory to ~/.gimx-bluetooth, and the ~/.sixemugui-serial to ~/.gimx-serial.
Known issues
Fixed issues.
Downloads.
Enhancements
Save your configs before upgrading to this version.
In case of critical issues, just downgrade to version 0.51.
Please report issues through the googlecode page: link.
Note for Raspbian users: my Raspberry Pi is broken... so there sadly is no package yet.
Windows users have to move the config directory to C:\Users\<username>\AppData\Roaming\emuclient\config.
Linux users have to move the ~/.sixemugui directory to ~/.gimx-bluetooth, and the ~/.sixemugui-serial to ~/.gimx-serial.
Known issues
Fixed issues.
Downloads.
Enhancements
- issue 192: Macro activation
This allows to specify which macro file should be read for each config file.
It also gives the possibility to change the macros without restarting emuclient.
More about this in the wiki. - issue 197: [Linux] Get input events directly from evdev
More about this in this blog post. - issue 199: Mouse driving mode
This allows to precisely control a stick with a mouse, which is very useful for driving vehicles. - issue 205: [Linux] Sort the config files alphabetically in gimx-serial and gimx-bluetooth
- issue 206: [gimx-serial] Do not display serial ports not supporting raw transmission and 500kb/s
This will hide RS232 serial ports in windows. This kind of serial port is not compatible with GIMX.
- issue 98: [Windows] Some mouse buttons are not working
This adds support for the horizontal wheel buttons. It may work or not work depending on the mouse.
If it doesn't work for your mouse, you should try to assign a keyboard button using the manufacturer's software. - issue 194: Wrong device id for events generated by macros
- issue 198: [gimx-fpsconfig] Bindings not correctly updated
- issue 201: Wrong default parameters for joystick axes
- issue 202: [Windows] Empty device name with "multiple mice and keyboards" enabled
- issue 207: [Linux] Use xdg-open instead of gnome-open
- issue 208: [Windows] Config files should not be stored in C:\Program Files
Config files are now stored in C:\Users\<username>\AppData\Roaming. This is more compliant with Windows programming rules. - issue 209: Wrong button states with controller type joystick or 360Pad