Skip to content

v1.2.0-beta1

Pre-release
Pre-release
Compare
Choose a tag to compare
@JovannMC JovannMC released this 07 Jul 21:29
· 175 commits to main since this release
94d2e6e

SlimeTora v1.2.0-beta1 - bugs, bugs, and more bugs!

This is the only beta expected to happen for v1.2.0, the full release will be out when SlimeVR Server v0.13.0 releases in an unspecified date. More additions are expected by then, including the finished Italian translation and submitting of the Haritora firmware constant to SlimeVR server.

Hey look, the first beta that is public on the GitHub instead of being exclusive on Discord!

The first beta for SlimeTora v1.2.0 is now out, this one includes changes to the backend of both SlimeTora and haritorax-interpreter which should hopefully improve performance (but at least, the code is now readable!). Many bugfixes are also included in this update, check it out!

This update also includes a (partial) translation of the program into Italian! Thank you to @francescatanuki in advance - the full translation will be ready by full release.

Changelogs

  • Optimize the hell out of the code for both SlimeTora and haritorax-interpreter
    • Well at least if it doesn't help as much, the code is actually readable now!
  • Use fs/promises for some I/O operations to improve performance (hopefully)
    • Was originally gonna do this for all operations, but ofc we're talking async (and my) code so it is currently only for the log files.
  • Add Italian translation and update credits
  • Minor logging updates
    • SEVERE logging level added, severe errors happen when:
      • Connection to trackers fail via BT or COM (leading to the "connection failed" error dialog)
      • Decoding IMU packet fails
    • Severe errors will always be shown, no matter the logging mode set in-app.
  • Update and optimize packages
  • Do more cleanup of memory when closing the app
  • Fix bug with external links opening in the app instead of browser
  • Fix "connection failed" error not showing up if the program fails to start the connection
    • This uh, apparently never worked when introduced with v1.1.0 lol.
    • With this, error handling in the program can now be easily handled in the future as I mostly fixed and rewrote how it works.
  • Fix bug with HaritoraX Wireless trackers (connected via GX(6/2) dongles) not immediately reporting its battery data when first connected
    • The dongles actually immediately report the (last known) battery information of the trackers (even if not connected), so uh now you can see it almost immediately lol.
  • Fix bug with HaritoraX Wireless trackers (connected via Bluetooth (LE)) where magnetometer and battery data would not show
    • I accidentally introduced this bug with v1.1.0 when I released haritorax-interpreter v2.0.0 by not checking the results of a "search and replace", oops.
  • Fix bug with HaritoraX Wireless trackers (connected via Bluetooth (LE)) where magnetometer and battery data don't show immediately
    • You now don't have to wait for the trackers to report their battery and magnetometer data, the program now requests the data from the trackers!
    • This uses an artificial 6 second delay before requesting the trackers, to make sure the trackers have fully initialized before requesting data
  • Fix bug where disabling settings while being in an active connection causing breakage by either:
    • giving you the funny "no connection to stop" error by accident (you didn't use inspect element)
    • only stopping one type of connection, then break the app when starting the connection again (without restarting the app) lol
  • Fix bug where incorrect tracker settings will be applied when the trackers are connected
    • Previously, you would sometimes have to press the save button again (while connection is active) for the tracker settings to actually apply
    • Thank you to arubedo. on Discord for reporting this!
  • Fix debug parameter accidentally being left in for i18next

Known issues

  • 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 themsleves.
  • Sometimes you get a "deinit" JS error when closing SlimeTora
    • Fixed with next release

Full Changelog: 1.1.0...v1.2.0-beta1