SlimeTora v1.5.3 - oh no, this was a critical issue
HaritoraX 2 users must choose the new "HaritoraX 2" tracker model to fix critical issues.
The third bugfix release for v1.5.x is now out! This release is a critical one for HaritoraX 2 users - this fixes high acceleration at idle (& general inaccurate acceleration) which may have caused faster drifting and sliding for HaritoraX 2 users, and mag data for the leg trackers.
I apologize heavily for this critical issue only being fixed now. This happened due to hardware changes in the HaritoraX 2, where the accelerometer has been calibrated better which lead to internal math (relating to gravity/acceleration) being wrong. This may have caused faster drift times and sliding only for HaritoraX 2 users. This also technically should've been a minor release, but this fix is more important lol.
The v1.5.x updates will hopefully be the final releases before the upcoming SlimeTora v2! It's been in the works for quite a while and there is still a lot more to be done. With the completely new UI frontend and backend, I hope v2 will be worth the wait! Join the Discord to see sneak peeks: https://discord.gg/XdfnKD9QVM
Changelogs
- Add dedicated HaritoraX 2 option to fix critical issues:
- Fix high acceleration on idle
- Fix general inaccurate acceleration
- Fix leg trackers' mag data incorrect
- Allow rfcomm serial ports for Linux (#26)
- Language updates
- General improvements & package updates
Known issues
- Bluetooth issues
- e.g. unable to find trackers at all, some disconnections
- This seems to be affecting a certain percentage of users and I'm unsure why this is the case - it seems to stem from a problem with the Bluetooth NPM package being used so it seems to be out of my control.
- SlimeTora v2 will hopefully fix issues for these people, but there are some ways and builds to hopefully minimize these on my Discord and v1.5.1: https://discord.gg/XdfnKD9QVM
- macOS builds are unnecessarily large
- Battery information jumps to incorrect percentages/voltage randomly
- Unfortunately this is an issue I can't fix.. because it's literally an issue with the trackers reporting those random values themselves
- This has been slightly mitigated with v1.2.0, which uses a "stable average" of the battery percentage and voltage instead
- Running "auto-detection" more than once without restarting breaks tracker settings auto-detection (device/ports detection still works)
- (?) Auto-detection still does not work for HaritoraX Wired (1.1b/1.1/1.0) users
Full Changelog: 1.5.2...v1.5.3