Releases: dmadison/Prismatik-iRacing
Releases · dmadison/Prismatik-iRacing
Version 0.2.4
cfg.ini
is now titledconfig.ini
. Internal structure is the same.
Bugfix:
- The configuration file is now correctly applied for both source and executable versions.
Back-end changes:
- Added
release_assembler
andversion_updater
scripts to help with preparing releases. - Preset and configuration files are now supported in both the program directory (default) and the parent directory. This is determined at startup.
Repository changes:
- LOTS of changes to the structure of the repository in-order to facilitate bundled
.exe
releases. - Added
build_instructions.md
readme file - Expanded description in
README.md
- Added a non-affiliation disclaimer
Version 0.2.3
Back-end Changes:
- There is no more 'preset applied' flag, which means multiple presets can be loaded and applied while the plugin is running.
Version 0.2.2
User-facing changes:
- Presets now have their own configuration files within the plugin. Set the User Settings variable of 'preset' to select them.
Version 0.2.1
User-facing changes:
- There is now a dedicated markdown file for 'Presets', which provides some preset configurations for visualizing data like the shift light and lap times.
Bugfixes:
- Multi-colored mapping for the symmetric pattern now works correctly.
- All patterns correctly work if one color is set.
get_color
function returns the only possible option if only one color is in the array.- Missing option exception is caught for all boolean values in the config.
Version 0.2.0
User-facing changes:
- Added a
ShiftLightBlink
method if you only want the LEDs to blink at the shift point. - Added a multi-color mode that maps colors to LED position rather than input percentage.
- Added a bidirectional pattern, which allows you to map data around a center point. Useful for things like acceleration or delta time.
- Added an icon!
Back-end Changes:
- Debug print statement now includes the raw output from iRacing as well as the scaled float value, which is useful for debugging range issues.
- The settings
apiVar
for iRacing has been refactored toapi_var
to fit Python conventions - Fixed out of range bug when color smoothing is disabled.
- 'cclockwise' is now 'counter-clockwise'. User-facing option hasn't changed.
- Small performance improvements.
Version 0.1.0
User-facing changes:
- The default mapping value is now 'ShiftLight', a custom function based off of RPM and the non-deprecated shift light range information. You can still use
ShiftIndicatorPct
to use the deprecated version. - Users can now select non percentage-based data for mapping, and they can select a
min
andmax
value for the mapped variable. This means you can now display data such as temperature, speed, or RPM so long as you know the range you want to display. - Blink rate: you can now configure the blinking speed of the ambilight for when the mapped value goes over its max range. Setting this value to 0 or 'off' will disable blinking.
- Each config value is parsed separately, so an error in one value won't break all of your settings.
Back-end changes:
led_index
is nownum_leds
and is indexed at 1 rather than 0. More useful to keep the number around in that form.- The low pass filter is now its own class, just in-case you want to map multiple variables simultaneously.
- Orphan functions now live in a
utils
file and are imported as they are needed. This makes it easier to share simple functions between classes. - Shift light range points are calculated on connection rather than continuously, which should yield a small performance boost.
- Framerate delay now takes into account execution time, which give a slight framerate boost (taking into account the frame cap).
Version 0.0.2
These are mostly behind-the-scenes changes to clean up the code and making things a bit more workable going forward. User-facing changes include:
- Prismatik settings are now correctly labeled "Prismatik" rather than "Lightpack", as the plugin is device-agnostic.
- Added the ability to set an "off" color separate than [0, 0, 0].
- Framerate is limited to a max of 60 fps, which is the iRacing API update rate.
Version 0.0.1
Initial release!