Releases: berarma/oversteer
Releases · berarma/oversteer
0.5.3
0.5.2
0.5.1
0.5.0
Changes:
- Fixed swapped pedal axes in the Logitech G920 wheel.
- Removed fake dead zones in the display of the steering wheel and pedals due to errors in some GTK themes.
- Fixed hot-plugging of devices with proper detection of disconnections and connections.
- Fixed warnings in the build/install process by upgrading requirements to Meson 0.50.
- Fixed enabling the screen ffbmeter when loading a profile.
- Added proper desktop environment identification of the app.
- New style for the overlay window with transparency and a title bar to ease relocation.
- The overlay window position will keep its position when in automatic display mode.
- The overlay window position is now saved in profiles.
- Experimental support for the Thrustmaster T300RS wheel.
- And other smaller fixes.
0.4.1
0.4.0 Catching up
This release is motivated mainly by the will to make new features in the new-lg4ff module more easy to test. But there's also other improvements.
- The user interface elements have been rearranged for more clarity and a modernized style.
- User interface controls that correspond to unavailable settings are left disabled.
- Added application icon for the desktop.
- Steering wheel tests integrated into the application. No need for external applications.
- The wheel range can be modified using the buttons in the wheel. The buttons can be configured.
- Added overlay window that shows the wheel range over the game screen.
- Changing compatibility modes is faster now.
The following features are also available when using the new-lg4ff module:
- Combine accelerator and clutch in the same axis. Useful for flight simulators.
- Adjustable conditional effects levels: spring, damper and friction.
- Real-time monitoring of total force effects applied using the wheel leds and/or the overlay window.
- Adjustable global force feedback gain that gets combined with the gain set by applications.
0.3.1
0.3.0
0.2.3 Fix wheel range setting
Wheel range setting wasn't working when the emulation mode was changed at the same time. It seems the driver needs a delay after a emulation mode change before accepting other changes.