v1.3.1

SlimeTora v1.3.1 - manage those dongles & trackers!

The first bugfix release for v1.3.x is now out! This release contains updates & fixes mostly relating to translations of the program; fixed the pairing window not translating correctly (found by @pikepikeid), more parts of the program can be translated, and fix the "SlimeVR not found" message popping up when the connection was stopped.

Important notice for SlimeTora users

Since release v1.3.0, SlimeTora has now been placed in maintenance-only mode until further notice. This does NOT mean that SlimeTora will stop working, however updates will be much slower and new features may not be added. The TL;DR of why this is happening is due to me (JovannMC) receiving a full set (10) of GorbitSlime trackers within the next few weeks, and I am sending off my HaritoraX Wireless trackers to another person. There is more information in my Discord server's "JovannMC update #3" announcement. If anyone would like to take over as a maintainer/create a fork, go ahead! FOSS FTW!

Thank you so much to the Haritora/Slime community for helping the project reach to where it is today ❤️.

Changelogs

• Allow more parts of the program to be translated
  • This includes update dialogs & window titles
• Make English the fallback language
  • If translation isn't found, falls back to english instead of the translation key
• General translation updates
  • New "UwU" language
  • Clarify some parts of the GX(6/2) pairing (treat it as a beta!)
  • Replace references "HaritoraConfigurator" with general term ("the official software")
• Fix pairing window not translating correctly
  • Thanks to @pikepikeid for finding this quickly!
• Fix connection buttons being in wrong "disabled" state in rare cases
• Fix "SlimeVR not found" message being sent even if connection is stopped after

Known issues

• On SlimeVR server v0.13.0, you cannot pass the "IMU Calibration" setup wizard step
  • SlimeVR server v0.13.1 will exclude Haritora trackers for this calibration step as it isn't needed for these trackers
  • Either skip the setup wizard and perform the steps manually via the navbar, or use 0.12.1 (not recommended) until 0.13.1 releases
• 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)
• Running "auto-detection" on HaritoraX Wired (1.1b/1.1/1.0) trackers doesn't work
  • Potentially fixed with v1.3.0, needs testing

Full Changelog: 1.3.0...v1.3.1