v1.3.0

SlimeTora v1.3.0 - manage those dongles & trackers!

The next release of SlimeTora is now out! This is another large update adding many new features & bugfixes like managing GX(6/2) dongles (pairing/unpairing & changing 2.4GHz channels), turning off all/individual trackers, and finally support for Bluetooth (LE) on Linux!

Important notice for SlimeTora users

With this release, SlimeTora is now 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

• Add management of GX(6/2) dongles in-app
  • Manage pairing of trackers
    • Removes the need for HaritoraConfigurator/VR Manager to be used when using for first time, or re-pairing trackers after they unpair
  • Change communication channel for COM port
    • Also prevents selecting channels already being used
• Add turning off individual/all trackers
  • Currently only supports HaritoraX Wireless w/ GX(6/2) dongles
  • Bluetooth supports requires sniffing BLE packets which I don't have the hardware for
• Add tracker heartbeat setting to GUI
  • Was previously a hidden config setting
  • Supported on both HaritoraX Wired and HaritoraX Wireless
  • Recommended to not touch
• Add full support for BLE on linux
  • Done via haritorax-interpreter v3.1.0 w/ inclusion of node-ble package
• Add warning on startup if using max logging mode (currently 3)
• Add extra failsafes and timeouts to tracker data/connection
• Redid SlimeVR check logic
  • User is now warned if SlimeVR server wasn't found after four seconds through a pop-up message
  • This is a non-blocking message that replaces the previous behaviour of blocking the connection if SlimeVR is not found
  • This can be skipped by closing the message, especially if in rare cases the trackers have actually connected to SlimeVR server even though the program doesn't see it
• Enable logging by default
• Update onboarding images for SlimeVR server v0.13.0
• Update credits
• Numerous updates to errors and logging
• ACTUALLY fix "connection failed" for wireless BT trackers, even if connection is fine
• Fix HaritoraX Wired auto-detection(?)
  • Unknown if fixed, haritorax-interpreter v3.1.0 fixes BTSPP detection on Windows but I cannot test this
• Fix GX dongle per-tracker settings
  • Fully stable now, removing the "not recommended" messages
• Fix rare cases of trackers showing up as "null" or "DONGLE"
• Fix trackers not showing up until tracker buttons are pressed
  • Sometimes, the trackers wouldn't show up on SlimeTora until at least one button is pressed on every tracker that is on
• Remove hiding menubar/devtools
• Remove "Skip SlimeVR Check" debugging setting
• Package updates
• Other bug fixes and optimizations

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.2.2...v1.3.0