If you use it, expect a few bugs. In case of critical issues, just downgrade to version 0.25.
Please report issues through the googlecode page: link.
About the 360 support with the diy usb adapter: this is considered as experimental, and it works in Linux only.
It requires to load a specific firmware (not compatible with the ps3) into the usb adapter.
- issue 129: Event scheduling for macros The goal of this is to make macro execution as accurate as possible. A macro beeing executed can now be canceled by pressing the macro key again. Important note: to make a macro loop, use KEYDOWN instead of KEY. Using KEY instead of KEYDOWN will cancel the macro as it schedules KEYDOWN + DELAY + KEYUP. Using KEYDOWN as a last command generates a key press event that is processed after the end of the macro.
- issue 136: Make gimx-fpsconfig capable of editing configs produced by gimx-config The goal of gimx-fpsconfig is to provide a simple config editor for FPS games. It is not as complete as gimx-config as it can't configure the following parts: - stick intensities - multiple controls for a same action - joystick controls - multiple mice and keyboards - multiple profiles Editing an "advanced" config with gimx-fpsconfig could result in deleted parts. Gimx-fpsconfig is now able to deal with advanced configs: it won't delete advanced parts. In case multiple controls are defined for the same action, it will only edit the first one.
- issue 140: improvements for config examples The goal is to preserve user's configs in case gimx is upgraded or config files are downloaded. Config examples are now saved into the example/ directory.
- issue 143: web updater It's now possible to check for updates through GUIs, and it's also possible to configure gimx-bluetooth or gimx-serial so that they check for updates at startup. This will hopefully make people to upgrade as soon as a new release is available.
- issue 144: config web updater The goal of this is to make it easier to get new configs from gimx-bluetooth or gimx-serial directly.
- issue 145: remove mouse and keyboard names This is done if 'Multiple mice and keyboards' is unchecked. In case 'Multiple mice and keyboards' is checked, the user is asked to identify the mouse and the keyboard by pressing buttons.
- issue 149: Easier calibration keys ctrl+F1 to enter the calibration mode F2 ... F12 to toggle between calibration steps ctrl+F1 to leave the calibration mode This allows to navigate through the calibration steps with a single hand.
- issue 150: GPP support GIMX can work with the [url=http://www.gamepadproxy.com/]gamepadproxy[/url] in Linux or Windows! The GPP is compatible with both the ps3 and the 360.
- issue 151: better accuracy for calibration tests Calibration tests generate specific mouse movements to help the user to configure the x/y ratios and the exponents. Precision of the generated mouse movements is improved.
- issue 154: emuclient command-line option to automate macro execution Adding "--keygen <key>" at the end of the emuclient command line allows to automatically start a macros when emuclient starts. If this argument is present, emuclient ignores all events from all devices. There are only two ways to stop emuclient: either add "KEYDOWN ESCAPE" at the end of the macro, or use --nograb This allows to automate the execution one or several emuclient processes.
- issue 139: gimx-fpsconfig fails to load mouse calibration values This problem occurs with v0.25 in case gimx-fpsconfig is started from gimx-bluetooth or gimx-serial (File > Edit fps config).
- issue 142: button stuck using switch delay In case the control was deactivated before the switch delay ends, the button was still activated and stucked.
- issue 152: display an error if the file can't be saved The error (file not saved) has to be showed to the user. This also helps the user to see if file permissions are wrong.
- issue 155: bad config ownership (Linux) After a fresh new installation, if the user starts emuclient without editing the config, ~/.emuclient permissions are wrong.