v1.2.2
SlimeTora v1.2.2 - here, let me do it for you!
The second bugfix release for SlimeTora is now out! This release contains numerous bug fixes that I missed between v1.2.0
and v1.2.1
, including incorrect "connection failed" errors and reconnecting trackers being broken until a restart.
Changelogs
- Fix trackers that reconnect to SlimeTora breaking (stops showing up until restarting connection)
- my bad, flawed code lol (simple fix).
- this also led to logs being spammed with "Error processing IMU data from (tracker)" errors, oops.
- Thank you to
the_flyingangel
on Discord for reporting this!
- Fix "connection failed" showing if connecting with HaritoraX Wireless trackers (via BLE), even though they work fine
- Fix tracker info (battery/mag status) not restoring when device list is refreshed
- Device list is refreshed when you change the "compact view", "tracker visualization", and "tracker visualization fps"
- Fix "main window" language select not changing when changing language in onboarding
- Language changes in "main window" when selecting in onboarding, but not the "language select" causing issues if you reopen onboarding (now fixed ofc)
- Fix "Tracker Visualization" not being disabled if "Compact View" is on (and vice versa, incompatible settings)
- Fix tracker info not showing if trackers aren't connected to SlimeVR Server (so, only happens when "Skip SlimeVR Check" is enabled)
- Fix battery readings being affected by constant stopping and starting SlimeTora connections (well, mostly)
- Remove need for "Tracker Visualization FPS" setting needing a restart to apply
Known issues
- On SlimeVR Server
v0.13.0
, you cannot pass the "IMU Calibration" setup wizard step- This has been fixed with a future update,
v1.3.0
(caused by weirdly high acceleration on idle due to IMU noise?) - SlimeVR Server
v0.13.1
will exclude Haritora trackers (as calibration isn't needed) & include a skip button - Either skip the setup wizard and perform the steps manually via the navbar, or use
0.12.1
(not recommended)
- This has been fixed with a future update,
- 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
- (LINUX) Connecting to trackers via "Bluetooth (LE)" always fails
- The Bluetooth package we are using, noble, requires root/sudo to be able to interact with BLE devices - its workarounds (and running as sudo) break Electron due to
setcap
disabling theLD_LIBRARY_PATH
environment variable for security and modifying thebluetooth.conf
for dbus does not work (at least, for me) - Any help on this is appreciated, though haritorax-interpreter may need to use both noble and node-ble (with a minor tweak on the user's side) to work.
- Fixed with a future update,
v1.3.0
- The Bluetooth package we are using, noble, requires root/sudo to be able to interact with BLE devices - its workarounds (and running as sudo) break Electron due to
Full Changelog: 1.2.1...v1.2.2