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)
• 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 the LD_LIBRARY_PATH environment variable for security and modifying the bluetooth.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

Full Changelog: 1.2.1...v1.2.2

v1.2.1

SlimeTora v1.2.1 - here, let me do it for you!

The first bugfix release for SlimeTora is now out! This is a hotfix that fixes COM ports not being detected by the program if on Windows and handle more types of errors with new error messages.

Changelogs

• Fix COM ports not showing up for Windows users due to incorrect filtering
  • uhhh.. my bad lol. me when i break slimetora for windows users only (aka 99.99% of people). time to switch to linux guys!
  • Thank you to the_flyingangel on Discord for reporting it so quickly!
• Handle more errors with new error messages
  • Error message when failing to write data to trackers (e.g. heartbeat, tracker settings)
  • Error message when an unexpected error happens

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 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)
• (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 the LD_LIBRARY_PATH environment variable for security and modifying the bluetooth.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.
• Starting a connection via Bluetooth may show a "connection failed" error, even though trackers are working fine

Full Changelog: 1.2.0...v1.2.1

v1.2.0

SlimeTora v1.2.0 - here, let me do it for you!

The next release of SlimeTora is now out! This is the largest update released since the rewrite (due to the 3 betas all being huge), coming in with many new features and bugfixes. The main highlights of this release include the new onboarding process (with auto-detection!), update checking, and many bugfixes!

Like v1.1.0, this update was supposed to be a smaller one but ended up being even bigger than I could imagine, very sorry about the wait! With this, SlimeTora shouldn't need any more major updates and an official video tutorial will finally be worked on!

Oh yeah, Linux builds that I post here now actually work (thanks to the new GitHub Actions workflow that's been set up) - no more issues with the prebuilt binaries because I used either OS to build it manually!

Changelogs

• New onboarding process when setting up SlimeTora for the first time
  • The new onboarding setup will guide you through the basics of how to set up the app and SlimeVR Server
  • "Automatic setup" allows you to make use of the new auto-detection feature, allowing you to let the program set up the program for you!
  • Auto-detection automatically detects the tracker model, connection mode (and COM ports if applicable), and even import your tracker settings!
  • You can always re-open the onboarding setup through the "Open onboarding" button (or deleting your config.json)
• New "Update checking" settings
  • Update checker for the app (on startup)
  • Update channel used when checking for updates (stable/beta)
  • Updater for app translations (on startup)
    • No need to wait for new releases to get the new translations if more are added!
• New "compact view" option
  • This makes the "tracker information" cards compact, allowing you to see more of your trackers without scrolling
  • This removes the "rotation" and "acceleration" data to give it its compact size
• Logging overhaul
  • Three logging levels, INFO (for general logging), WARN (for warnings that may not impact general use), and ERROR (for errors that impact general use)
  • "ERROR" logs will always be shown, no matter the logging mode set in-app
  • "All data" now logs raw, unprocessed data coming from the trackers (via haritorax-interpreter)
  • Logging messages are grouped into its own categories (e.g. connection, settings, updater, etc)
• Language/translation updates
  • Add Italian translation (TBC by @francescatanuki)
  • Language files are now loaded asynchronously
  • Warn console about missing translation key/values and use default (en.json)
  • Translations can use inline HTML for formatting (e.g. <strong>Start connection</strong>)
• Update credits page
• Add support for battery voltage (and charge status in logs) to HaritoraX Wireless trackers connected via Bluetooth (LE)
• Add "support page" button to debugging section
• Do more cleanup of memory when closing the app
• Properly handle invalid mag statuses being received
• Truncate device names if too long
• Remove need to restart connection for certain settings
• Add a failsafe if no data is received by the app from trackers
• Gracefully handle/fix many runtime errors
  • Most of these don't affect the end-user but this is just so I stop getting screamed at :p
• 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
  • 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 upon connection!
• 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
• Fix SlimeVR Server rapidly hiding/showing ping
  • ..fixed by sending some "funny" signal strength information to SlimeVR server
  • You may also notice another "funny" thing - your trackers may seem to be.. toasty :)
    • (Hint: enable "Developer Mode" under "Appearance")
• 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 "accelerometer" always being enabled on startup, even if manually disabled by the user
  • Thank you to hioshim on Discord for reporting this!
• 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 correct tracker settings to be actually applied
  • Thank you to arubedo. on Discord for reporting this!
• Fix bug with external links opening in the app instead of browser
• Fix debug parameter accidentally being left in for i18next
• Fix battery info not showing immediately upon connection if multiple are connected as the connection starts
• Fix "status" not translating when switching between languages
• Fix "{trackerName}" sometimes appearing in the per-tracker settings window
• Fix voltage being shown in mV instead of V
• Fix "waiting for SlimeVR server" delay if skipping SlimeVR checks is on
• Fix "deinit" JS errors when exiting SlimeTora
• Fix "invalid settings" warning when receiving an empty sensor auto correction list
• Fix per-tracker settings not applying properly
• Fix null errors on tracker connection
• Fix "error" logs being undefined sometimes
• Fix multiple development issues
• Package updates
• Other bugfixes & optimizations

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 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)
• (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 the LD_LIBRARY_PATH environment variable for security and modifying the bluetooth.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.

Full Changelog: 1.1.0...v1.2.0

v1.2.0-beta3

SlimeTora v1.2.0-beta3 - i should update? what's that!

This is one of the last betas to expected to happen for v1.2.0, the full release will be out when SlimeVR server v0.13.0 releases in an unspecified date.

The third beta for SlimeTora v1.2.0 is now out, this contains even more large changes to the program including a full onboarding process which guides you how to set up SlimeTora & SlimeVR, settings for update checking, compact view, and many more changes & bug fixes!

Changelogs

• All new onboarding process to set up SlimeTora
  • The new onboarding setup will guide you through the basics of how to set up the app and SlimeVR Server
  • Auto-detection has been moved here and should now support the HaritoraX Wired trackers
• New "Update checking" settings
  • Update checker for the app (on startup)
  • Update channel used when checking for updates (stable/beta)
  • Updater for app translations (on startup)
    • No need to wait for new releases to get the new translations if more are added!
• New "compact view" option
  • This makes the "tracker information" cards compact, allowing you to see more of your trackers without scrolling
  • This removes the "rotation" and "acceleration" data to give it its compact size
• Overhaul for logging
  • Three logging levels, INFO (for general logging), WARN (for warnings that may not impact general use), and ERROR (for errors that impact general use)
  • Remove "SEVERE" (replaced with now-called "ERROR")
  • "All data" now logs raw data coming from the trackers (via haritorax-interpreter)
  • Logging messages are grouped into its own categories (e.g. connection, settings, etc)
• Translation handling updates
  • Warn console about missing translation key/values and use default (en.json)
  • Translations can use inline HTML for formatting
• Truncate device names if too long
• Remove need to restart connection for certain settings
• Add a failsafe if no data is received by the app from trackers
• Fix "invalid settings" warning when receiving an empty sensor auto correction list
• Fix per-tracker settings not applying properly
• Fix null errors on tracker connection
• Fix "error" logs being undefined sometimes
• Package updates
• Other bugfixes & optimizations

Known issues

• Battery and mag info for HaritoraX Wireless trackers (connected via BT) not displaying
  • Fixed with the v1.2.0 betas, check releases.
• Detection of being unable to access trackers unreliable
  • Fixed with the v1.2.0 betas, check 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 themselves.
  • This has been slightly mitigated with v1.2.0-beta2, which uses a "stable average" of the battery percentage and voltage instead.
• (v1.2.0-beta3) Running "auto-detection" more than once without restarting breaks tracker settings detection

Full Changelog: v1.2.0-beta2...v1.2.0-beta3

v1.2.0-beta2

SlimeTora v1.2.0-beta2 - auto-detection? how about you auto-detect deez nu-

This is one of the last betas to expected to happen for v1.2.0, the full release will be out when SlimeVR server v0.13.0 releases in an unspecified date.

The second beta for SlimeTora v1.2.0 is now out, this one includes even more changes to the backend and a new settings auto-detection feature, making SlimeTora even easier to set up for the first time! This release also should hopefully fix a major issue with v1.2.0-beta1 where trackers would stop sending data to the SlimeVR server.

Changelogs

• (?) (v1.2.0-beta1) Fix some trackers failing to send data to SlimeVR server randomly
  • This issue is a weird one, it seems to be fixed with my testing but I am not sure if it is completely fixed as it was an extremely random issue that could occur - race conditions?
• Add early support for settings auto-detection
  • This makes the process of setting up SlimeTora even easier! The program will now try to automatically detect the tracker model, connection mode (including COM ports), and even your tracker settings to apply them for you!
  • Make sure HaritoraConfigurator is closed and it is recommended to have your trackers turned on during this process
  • This is very early and bugs are expected, currently only supporting the "HaritoraX Wireless" and its supported connection modes
• More optimizations to SlimeTora and haritorax-interpreter
• Language files are now loaded asynchronously
  • The language files are now bundled with the program instead of being copied at runtime, so this should prevent the issues I was having during testing
• Add support for battery voltage to HaritoraX Wireless trackers connected via Bluetooth (LE)
• Handle invalid mag statuses being received
• Remove artificial delay with HaritoraX Wireless BT trackers upon connection
• Fix SlimeVR Server rapidly hiding/showing ping
  • ..fixed by sending some "funny" signal strength information to SlimeVR server
  • You may also notice another "funny" thing - your trackers may seem to be.. toasty :)
• Fix battery info not showing immediately upon connection if multiple are connected as the connection starts
• Fix "status" not translating when switching between languages
• Fix "{trackerName}" sometimes appearing in the per-tracker settings window
• Fix voltage being shown in mV instead of V
• Fix "waiting for SlimeVR server" delay if skipping SlimeVR checks is on
• Fix "deinit" JS errors when exiting SlimeTora
• Fix issues with development
• Gracefully handle/fix many runtime errors
  • Most of these don't affect the end-user but this is just so I stop getting screamed at :p
• Minor logging updates/fixes
  • Also fixes some errors not appearing in logs (cause I'm dumb)

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 themselves.
  • This has been slightly mitigated with v1.2.0-beta2, which uses a "stable average" of the battery percentage and voltage instead.
• "Auto-detect settings" assumes anyone with "HaritoraX Wireless" and "GX6" uses elbows, thus enabling "Bluetooth" even if the user does not have/use elbows
• (?) Program may not launch correctly - actions in the app stop working until a restart
  • Seems to be some sort of asynchronous issue again with the languages (which I have no idea why happens, because this issue should literally not exist)

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

v1.2.0-beta1

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
  • Thank you to @francescatanuki!
• 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

v1.1.0

SlimeTora v1.1.0 - got wires?

After many delays, SlimeTora v1.1.0 is finally released, with HaritoraX Wired (1.1b/1.1/1.0) support and many more featues and QOL changes! This became a bigger update than I thought and there were many issues during development, sorry about that 😅!

Thank you to the community for helping test the beta builds and the massive support for the program, there's a lot of changes (and a long changelog) with this one.

Changelogs

• Support HaritoraX Wired (1.1b/1.1/1.0) w/ haritorax-interpreter v2.0.0
  • All these trackers are now supported, including the hip and elbow extensions
  • Settings of trackers can be changed in-app (impossible to set per-tracker however)
• Redone SlimeVR forwarding backend w/ @slimevr/tracker-emulation
  • Per-tracker battery information is now supported!
  • You can now see more clearly which trackers disconnect in SlimeVR server instead of relying on TPS/SlimeTora's display
  • Note: when setting up SlimeTora for the first time in this build and beyond, you will get pop-ups for "New tracker detected" in SlimeVR server for each tracker (you only need to accept it once)
  • The MAC address is now randomized and is stored in your config.json to keep the same one every session (helps improve SlimeVR's memory of your tracker assignments)
  • Special thanks to @TheDevMinerTV for working with me to build the package for this project and anyone else to use!
• Basic button bindings
  • Supported on both wireless and wired models for any buttons on trackers
  • 1 press = yaw reset, 2 presses = full reset, 3 presses = mounting reset, 4 presses = (un)pause tracking
• Separate "tracker" and "program" settings w/ new settings
  • You can now select between enabling the wireless or wired models of the trackers
• Add more control over debug logging
  • There is now 3 modes to the program's logs - minimal data, extra data, all data
• Add a Searching for SlimeVR message to differentiate between searching for the SlimeVR server and searching for trackers
• Show an error message if the connection (COM/BT) fails for any reason (including a dialog box that reminds you of basic steps like having HaritoraConfigurator closed).. hopefully lol
• Rename references to "GX" to "COM" when possible (or GX(6/2 / COM)
• Fix Windows' light mode setting causing parts of the program to be unreadable
  • i forgot who discovered this on the Discord, thanks to that person!
• Fix special characters in path causing program to not load (sanitize the URL)
  • Thank you @desokyun on Discord for discovering this issue!
• Fix a rare issue relating to the GPU process which leads to the program crashing on startup (disabling chromium sandbox, should be fine as we don't have external content)
  • Thank you @greenie_rio on Discord for discovering this issue!
• Fix some JS errors if an invalid device was started (somehow..?)
• Fix loading of program on Linux and serialport types
  • Thanks to @TheDevMinerTV for finding these!
• Fix 0v showing in renderer when it is not supposed to
• Fix some disconnection issues with BT
• Fix bug with less than 3 COM ports selected
• Fix security issue with translating text with i18n
• Other bug fixes and optimizations
• Credit and translations updates thanks to @pikepikeid and @reino7777 on Discord

Known issues

• Battery and mag info for HaritoraX Wireless trackers (connected via BT) not displaying
  • Fixed with next release (v1.2.0)
• 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.
• Detection of being unable to access trackers unreliable

Full Changelog: 1.0.0...v1.1.0

v1.0.0

SlimeTora v1.0.0 - the rewrite!

After many months of work, the SlimeTora rewrite is complete. SlimeTora v1.0.0 is now out, thank you to the community for helping to make this happen! Support for other trackers such as the HaritoraX 1.1b/1.1/1.0 is coming soon!

Check out the new wiki page for the program's documentation! https://github.com/OCSYT/SlimeTora/wiki

Special thanks to the many people from the Shiftall and SlimeVR Discord servers for the help and testing of the many alphas on the rewrite fork. Another thanks to @pikepikeid for the Japanese translation of the program, ありがとうございます！(*´∀`)

We can't wait to see what you do with the program.
-BracketProto (@OCSYT) & JovannMC (@JovannMC)

Changelogs

• Entire frontend and backend rewrite (with Bulma and haritorax-interpreter)
  • The program now has a new UI, the code is cleaner and more maintainable, and should hopefully improve stability/performance.
• Package app files with asar
  • No need to extract thousands of files anymore 😅
• Bluetooth and GX(6/2) support (with all at the same time supported)
  • Welcome elbow tracker users!
• Set tracker settings per-tracker
  • Currently in beta and needs more testing
• Localization support
  • You can help translate the program! Clone the repo and make a new file under /src/static/languages/ with a two-letter language identifier (ending with .json, e.g. jp.json)!
• Linux support
  • This was done as SlimeVR is supported on Linux, and the first time HaritoraX trackers work on Linux!
  • ..however this is not tested at all. Please let me know if there are issues.
• Tracker visualization
• Magnetometer statuses
• Censor tracker serial numbers
• Many new ways to debug the program
• New SlimeTora logo
• ..and many more improvements coming soon!

Known issues

• Battery information is slightly inaccurate on first connection
  • Fixes after the tracker reports the battery information by itself
• Battery data sent to SlimeVR server isn't per-tracker
  • Cannot really fix this, instead the program sends the lowest battery data from all the trackers to the server

Full Changelog: 0.1.3...v1.0.0

0.1.3

SlimeTora 0.1.3

A program made to connect Haritora X wireless trackers to Slime VR server

How to use

• Install the slime vr server https://docs.slimevr.dev/server/index.html
• Extract the zip file and run "SlimeTora.exe"
• Turn on your trackers and press "Connect to Trackers"
• Assign your trackers in Slime VR and enjoy! :)
  (make sure to go through the usual calibration steps)
• Make sure you connect all trackers before assigning roles in Slime VR

0.1.2

SlimeTora 0.1.2

A program made to connect Haritora X wireless trackers to Slime VR server

How to use

• Install the slime vr server https://docs.slimevr.dev/server/index.html
• Extract the zip file and run "SlimeTora.exe"
• Turn on your trackers and press "Connect to Trackers"
• Assign your trackers in Slime VR and enjoy! :)
  (make sure to go through the usual calibration steps)
• Make sure you connect all trackers before assigning roles in Slime VR