v1.5.3

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

v1.5.2

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

v1.5.1

SlimeTora v1.5.1 - ...okay so maybe that last release actually lived up to its name, again.

The first bugfix release for v1.5.x is now out! This release contains many bug fixes introduced by v1.5.0, mostly HaritoraX 2 fixes.. oops.

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

• Attempts to mitigate BLE issues
  • haritorax-interpreter switches over to the @stoprocent/noble fork, hopefully more stable
  • god idk why there were issues happening only for certain users, i can only think that i can blame nodejs (native modules) at this point lol - slimetora v2 when
• Fix numerous HaritoraX 2 issues
  • Fix "tracker write" error when changing settings for all trackers
  • Fix tracker & extensions not connecting/disconnecting properly
  • Fix mag status for "regular" trackers
    • Legs/extensions are still inaccurate - will be either fixed in a new update or SlimeTora v2
  • Fix battery information not showing up immediately when connected
  • Fix battery information not showing up for extensions
• Fix trackers not turning off when requested by user
• Fix SlimeVR warning always showing even if disabled
• Fix tracker settings being disabled for all if "wired" and "wireless" are both enabled
• Logging updates
  • Separate "tracker" (connection to SlimeVR w/ @slimevr/tracker-emulation) & "IMU" errors in logging
  • Something else I forgot
• Package & translation updates
• Not release SlimeTora v2

Known issues

• (LINUX) Cannot launch on Linux, terminal shows GTK 2/3 symbols detected. Using GTK2/3 and GTK 4 in the same process is not supported
  • Upstream issue with Electron v36, using --gtk-version=3 resolves this.
• 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.0...v1.5.1

v1.5.0

SlimeTora v1.5.0 - X2 support? X2 the bug- oh wait I already used that one

Wow, has it already been six months since the last SlimeTora v1 release? Wait... WHAT DO YOU MEAN IF I RELEASED IT YESTERDAY LIKE PLANNED IT WOULD'VE BEEN EXACTLY SIX MONTHS LATER? I'M A DAY LATE??

The next release of SlimeTora is now out! This is a huge feature update adding many things such as (hopefully stable) HaritoraX 2 support, turning off your BLE trackers, changes to the onboarding process, millions of bug fixes, and so much more!

This is especially a big one, not only in updates, but hopefully the final release before the upcoming SlimeTora v2! It's been in the works for quite a whilem 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 HaritoraX 2 support
  • Supports serial (GX6/2) & BLE
• Add "manual" setup to onboarding
  • There is now two choices to set up SlimeTora: "Automatic" (AKA auto-detection) and "Manual"
    • This renames "Automatic setup" to "Guided setup"
  • "Manual" asks the user questions about their setup to set up SlimeTora and their trackers
  • This allows for users to continue with the onboarding setup & see how to use SlimeVR without skipping the entire setup (if auto-detection doesn't work)
    • PLEASE HELP ME FIX WIRED AUTO-DETECTION
• Add ability to turn off BLE trackers
  • oops, that's something that was wanted for a while
• Add rand-seed to seed the random tracker MAC address with the tracker name (serial) or ID (BLE)
  • You can still choose to always randomize MAC addresses, useful so you can still make use of multiple tracker sets (with multiple instances of SlimeTora)
  • Deleting your config is required for the new behaviour, however it will not affect your existing trackers - takes effect when deleting config or add new trackers.
• Add changing IP & port to search for SlimeVR server on
  • Thanks @ButterscotchV for reminding me of this not existing for some reason
• Add tracker debounce
  • Sometimes, your clicks may be registered twice so a debounce time has been added to prevent that (100ms default)
• Add tracker button timeout
  • Changes how long until buttons are registered (so you can double, triple, or quadruple button press for other actions)
• Add feature that attempts to fix soft-bricked GX(6/2) trackers
  • Fixes soft-bricked GX(6/2) trackers that are boot-looping by repeatedly sending the command to reset the "power off" flag in the trackers.
  • Partially my fault I had to add this lol, read below to "Fix rare bug..."
• Add debug option to disable "SlimeVR not found" warnings when starting a connection
• Add secret "debug trackers" button
  • Emulates serial/GX(6/2) trackers
  • Present when you have a "debug.txt" file in your SlimeTora directory, containing raw data from the trackers
• Add ability to reconnect to serial ports automatically if they become available again
• Disconnect trackers spamming IMU errors
  • Prevents logs from being filled up by IMU errors
• Move GH actions to an asynchronous matrix for easily editing all build platforms
• Move config out of the build directory in development environment for persistence
• Fix rare bug that could cause users' GX(6/2) trackers to be "soft-bricked" when using the "auto-off" feature
  • my bad.
• Fix tracker assignments not working for assignments above 9 (hex)
  • Fixes the following not being recognized: rightWrist, head, leftFoot, and rightFoot
  • Thanks to toko_takamiya (and their friend) on Discord!
• Fix issue that could cause trackers to rapidly reconnect/flicker (from v1.5.0-beta3)
  • This most commonly happens to users who use the GX(6/2) dongles and blindly enable all serial ports
  • The program would try to open a serial port that is reserved, and would pretty much freak out
  • Fixed by ensuring only the trackers of the serial ports that are having issues disconnect, not ALL trackers
  • Thanks to multiple people on Discord (sorry, I forgot who all reported there was a few!)
• Fix "auto off" being enabled even if disabled in UI
• Fix auto-detection for users without Bluetooth
• Fix handling of systems without any BT adapters a bit more
• Fix device ID and names being swapped when having a custom name
• Fix crash on MacOS development environment trying to load languages from ../
• Fix non-blocking message dialogs... blocking for MacOS users
• Fix BLE devices not being filtered out properly when disconnected
• Logging updates
  • Log incoming packets from @slimevr/tracker-emulation
• Language updates & improvements
  • UwU language is very much improved :3
• Package updates
  • WE'RE FINALLY NOT 5 MAJOR VERSIONS BEHIND IN ELECTRON (because they fixed it)!!!!!
• Other bug fixes & optimizations

Special thanks to @lillithkt for some of these changes in #18!

Known issues

• (v1.5.0) The "SlimeVR not found" warning always appears if not disabled
  • Fixed with upcoming release, v1.5.1.
• (v1.5.0) Battery does not show up for extensions
  • Fixed with upcoming release, v1.5.1 (will show same battery as main tracker ofc)
• (v1.5.0) Mag statuses for HaritoraX 2 inaccurate
• (v1.5.0) IMU / write errors for HaritoraX 2
  • Fixed with upcoming release, v1.5.1
• 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 coming soon): 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.4.0...v1.5.0

v1.5.0-beta4

SlimeTora v1.5.0-beta4 - wait, that last release did actually live up to it's name

The fourth beta for SlimeTora v1.5.0 is now out, this update fixes the broken CSS from last beta and adds numerous backend & development changes, including choosing whether to seed MAC address from name or always randomize.

Changelogs

• Add rand-seed to seed the random tracker MAC address with the tracker name (serial) or ID (BLE)
  • You can still choose to always randomize MAC addresses, useful so you can still make use of multiple tracker sets (with multiple instances of SlimeTora)
• Move GH actions to an asynchronous matrix for easily editing all build platforms
• Move config out of the build directory in development environment for persistence
• Fix broken CSS from last beta build
  • Now always builds CSS when developing/building - oops
• Fix crash on MacOS development environment trying to load languages from ../
• Fix non-blocking message dialogs... blocking for MacOS users
• Package updates & optimizations

Special thanks to @lillithkt for most of these changes in #18!

Known issues

• 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.0-beta3...v1.5.0-beta4

v1.5.0-beta3

SlimeTora v1.5.0-beta3 - x2 support? x2 the bugs!

The third beta for SlimeTora v1.5.0 is now out, this update adds beta support for the HaritoraX 2 (serial & BLE) and adds a "button timeout" option to customize the time until buttons presses are registered.

This is also the first time I built for other platforms too for the betas :p

Changelogs

• Add beta HaritoraX 2 support
  • Serial and BLE support
  • Seems to mostly work (due to being almost the same trackers), however not as tested
• Add tracker button timeout
  • Changes how long until buttons are registered (so you can double, triple, or quadruple button press for other actions)
• Fix handling of systems without any BT adapters a bit more
• Fix device ID and names being swapped when having a custom name
• Optimizations
• Package updates

Known issues

• 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.0-beta1...v1.5.0-beta2

v1.5.0-beta2

SlimeTora v1.5.0-beta2 - acceleration? who needs that?

The second beta for SlimeTora v1.5.0 is now out, this update fixes a major oversight with acceleration not behaving as expected, adds more to the "manual" setup flow, and other bugfixes & language updates.

Sorry that the beta here is Windows (x64) only, can't do much about it because of how the project is structured 😅

THE GITHUB ACTION BUILDS WILL NOT HAVE THE LATEST (BETA) VERSION OF haritorax-interpreter FOUND IN BETAS AND I DO NOT GUARANTEE IT WILL WORK.
You may still attempt the builds if you are not on Windows (x64), but certain bugs "fixed" in betas may still occur.

Changelogs

• Add tracker & more program settings to "manual" setup
  • Adds sensor mode, FPS, sensor auto correction
  • Adds update settings
  • Adds cancel/ok buttons
  • Auto-detect GX(6/2) ports and select by default
  • Fix certain inapplicable questions being asked
  • Other fixes & more
• Fix acceleration
  • Thank you to rosieeeot & dirges on Discord!
• Fix auto-detection for users without Bluetooth
• Language updates
• Other optimizations & fixes

Known issues

• 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.0-beta1...v1.5.0-beta2

v1.5.0-beta1

SlimeTora v1.5.0-beta1 - oops, my bad

Oh hey, it's been a while. Here take a beta!

The first beta for SlimeTora v1.5.0 is now out, this updates the onboarding to be a bit more user-friendly, add/handle a few things better in the program, and fixes a rare issue that could soft-brick GX(6/2) trackers. Uhhh, my bad.

Sorry that the beta here is Windows (x64) only, can't do much about it because of how the project is structured 😅

THE GITHUB ACTION BUILDS WILL NOT HAVE THE LATEST VERSION OF haritorax-interpreter FOUND IN BETAS AND I DO NOT GUARANTEE IT WILL WORK.
You may still attempt the builds if you are not on Windows (x64), but certain bugs "fixed" in betas may still occur.

Changelogs

• Add "manual" setup to onboarding
  • There is now two choices to set up SlimeTora: "Automatic" (AKA auto-detection) and "Manual"
    • This renames "Automatic setup" to "Guided setup"
  • "Manual" asks the user questions about their setup to set up SlimeTora
  • This allows for users to continue with the onboarding setup & see how to use SlimeVR without skipping the entire setup (if auto-detection doesn't work)
    • PLEASE HELP ME FIX WIRED AUTO-DETECTION
• Add changing IP & port to search for SlimeVR server on
  • Thanks @ButterscotchV for reminding me of this not existing for some reason
• Add feature that attempts to fix soft-bricked GX(6/2) trackers
  • Fixes soft-bricked GX(6/2) trackers that are boot-looping by repeatedly sending the command to reset the "power off" flag in the trackers.
  • Partially my fault I had to add this lol, read below
• Reconnect to COM ports if available again
• Disconnect trackers spamming IMU errors
  • Prevents logs from being filled up by IMU errors
• Fix rare bug that could cause users' GX(6/2) trackers to be "soft-bricked" when using the "auto-off" feature
  • my bad.
• Fix "auto off" being enabled even if disabled in UI
• Language updates & improvements
  • "erm, well acktuwally, linux isnt unix based ☝️ 🤓. Linux is just a kernel and a part of the gnu operating system, which is unix like, but not unix based" -@kruemmelbande
  • UwU language is very much improved :3
• Package updates
• Other bug fixes & optimizations

Known issues

• 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)

Full Changelog: 1.4.0...v1.5.0-beta1

v1.4.0

SlimeTora v1.4.0 - the too lazy update

The next release of SlimeTora is now out! This is another feature update adding a couple new features & bugfixes including support for the new tracker part types, autostart / auto power off features, macOS/ARM builds, and (hopefully) finally fixing auto-detection support for HaritoraX Wired!

Important notice #2 for SlimeTora users

You may have seen that since SlimeTora v1.3.0, I put up a notice stating that SlimeTora would be put into maintenance mode. That status is currently suspended until further notice, and SlimeTora is out of the "maintenance-only" status for now.

Changelogs

• Add autostart and auto power off features
  • Automatically start connection when program is launched
  • Automatically power off all trackers when closed
    • Currently still only supported for GX dongle, need a BLE sniffer to figure out how to power off BLE trackers :(
  • for ya lazy folks (me) :p
• Add support for new part assignments
  • With you being able to buy individual trackers, there are 5 new assignments:
    • L/R wrists, L/R feet, & head
  • Hopefully this should just work, lol
• Add support for macOS
  • Woo! For that one person who wants to use SlimeVR and these trackers on macOS, here you go!
  • Very untested, but apparently BT already works! (GX dongle completely untested)
• Add support for ARM systems
  • I uh, have no idea if these work. But here you go, ARM builds for every OS!
• Add "dark red" mag status
  • This is the equivalent of "very bad" in Shiftall's VR Manager
  • Previously both "bad" and "very bad" equivalents were just red in SlimeTora and HaritoraConfigurator
• Update onboarding
  • Add message for unix-like users (excluding macOS)
    • Unix users need extra setup before SlimeTora can work
    • Opens the SlimeTora wiki's unix instructions
  • Adds step 11 - "Relaunching SlimeVR"
    • This describes what to do when you launch SlimeVR again - full reset + mounting reset
    • Links to ZRock35's calibration video (hi :3)
  • Update step 10
    • Clarify that you only need to do body proportions once (and is optional)
    • Tell user if they have issues, retry or use defaults
• Reorganize "Program settings" for new features
• Optimized assignment logic for GX dongles
  • Finally removed the janky assignment logic I made before since we can now request info from the dongles!
  • No more weird delay :p
• Fix HaritoraX Wired/BTSPP detection (finally?)
  • PLEASE WORK PLEASE PLEASE PLEASE
  • Unknown for Linux
• Language updates
  • UwU language has been updated to be more, meow :3 (some strings have been edited manually instead of being generated)
  • Renamed "Translations updates" to "Language updates"
• Very minor CSS update for vertical settings containers
  • gap went from 2rem to 1rem
  • "Tracker information" buttons are now one line in the default window size
• Package updates

Known issues

• 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)

Full Changelog: 1.3.1...v1.4.0

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