Skip to content

v1.5.2

Choose a tag to compare

View all tags
@JovannMC JovannMC released this 18 Jul 07:34
· 11 commits to main since this release
v1.5.2
2401176
This commit was signed with the committer’s verified signature.
JovannMC Maya
SSH Key Fingerprint: xpaVt25n2vJ+o6zXOStvT2zcPGxyZonkhovOh7qk3XE
Verified
Learn about vigilant mode.

SlimeTora v1.5.2 - this should've been a minor version bump update

The second bugfix release for v1.5.x is now out! This release adds switching communication modes, highlights the dongle ports (and warns if it wasn't detected as one), and many more bugs introduced by v1.5.0 - this should've been a minor (feature) version bump lmao.

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 switching communication mode - BT<->GX(6/2)
  • Highlight detected GX(6/2) dongle ports
  • Warn if non-dongle ports selected
  • Fix HaritoraX Wired (1.0/1.1/1.1b) additional trackers not connecting (hip/elbows)
    • Thank you to @ltsmithneko on Discord for the report!
  • Fix Linux not launching due to upstream (Electron) w/o --gtk-version=3
  • Fix "unknown data" spam for HaritoraX 2 on Bluetooth
  • Fix write errors when opening tracker management page
  • Language updates
    • Clarify HaritoraX 2 tracker assignment
    • Change "override settings" to "Manage tracker"
  • 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.1...v1.5.2

Assets 8
Loading