Common Issues

So something isn't working and you find yourself stuck, this page is here to give answers to common issues. If nothing here answers your question, please feel free to ask in the #support-forum on the SlimeVR Discord. Make sure you mention all of the steps you have tried from here when asking for help.

Please specify upload_port while updating firmware / trying to upload firmware fails

This error indicates there is interference between your computer and the tracker. Check the following:

  1. Make sure your USB cable from the tracker is plugged firmly into your PC.
  2. Make sure that your USB cable is a data and charging cable (it is suggested you try other cables or devices with the cable).
  3. Make sure that your drivers are up to date.
  4. You may have a counterfeit CH340 module on your DIY tracker. Try running FakeCH340DriverFixer for compatible drivers.

Additionally, this can be caused by software hogging COM ports (VSCode and Cura can be the cause of this).

The SlimeVR Server won't start

  • If there's a port error, make sure you don't have other instances of the server running and/or restart your PC.
  • This may also be caused by Java not being installed or issues with your Java installation. The installer linked in the Installing the server page should handle this.

The Wi-Fi Settings window outputs ERROR

Try resetting your tracker, this may fix the issues immediately. If this doesn't work, your COM port may be being hogged, which can be tested by going through the firmware update process in VSCode (as it has more verbose error messages). If this is the case, close any application that might be hogging the ports (VSCode and Cura are often the cause). If the issue persists, try connecting the tracker to a different USB port.

The Wi-Fi Settings window outputs symbols and nothing else

There are two common causes that you should check:

  • Make sure that you have the right driver installed.
  • Check that your PIO firmware upload worked. If you have multiple firmware versions open in VSCode you will have to set the correct one to default to upload.

My tracker keeps flashing

This is intended behavior, the number of flashes lets you know the current status of your tracker. Check the top of the the setup page for more info.

My tracker never connects to Wi-Fi / are not appearing on the SlimeVR Server

The two common issues that cause this error are:

  • Make sure you are connecting to a 2.4GHz network, 5GHz networks are not supported.
  • Check your SSID for special characters. At the time of writing SlimeVR only supports network SSIDs that contain alphanumerical characters.
  • Make sure you are using WiFi channels 1-11. Avoid using channels 12-14 because connection issues may occur.

If all of this is correct, you can check your gateway's list of connected devices to see if all your trackers are connecting. If a tracker is not connecting even after using the same firmware upload with hardcoded Wi-Fi details there are two additional steps you can check:

  • Check if your Wi-Fi has reached its maximum allowed Wi-Fi connections. You can test this by disconnecting devices and then trying to connect your trackers again.
  • If you hard coded your Wi-Fi settings in platformio.ini try connecting your trackers via USB and pushing new Wi-Fi details. You may find this either fixes your connection or provides you with additional details on why the connection is failing.

My aux tracker isn't working

In order to make sure your aux tracker is set up, you need to specify it in your defines.h uploaded to the primary tracker's firmware. Check the bottom of the section mentioning defining the pins on the configuring the SlimeVR firmware page. Alternatively, you should ensure that you have correctly soldered VCC to AD0 on your aux tracker IMU.

Sensor was reset error

Check your INT wire, there is either a bad connection or you have it connected to the flash pin. If you are building your tracker on a breadboard, your connections may be not firm enough and cause this error.

The trackers are connected to my Wi-Fi but don't turn up on SlimeVR

Check that you do not have two copies of the SlimeVR server running, as only one of them will show trackers connected.

If only one server is running, this is most likely a firewall issue, go to SlimeVR Server folder and run firewall.bat as administrator to add the firewall rules to Windows Defender Firewall.

If you are still having trouble, try manually adding the SlimeVR Server to your firewall.

  1. Go to Settings > Network & Internet then click on the text link Window Firewall (you may have to scroll down).
  2. In the firewall window, click the link Allow an app through firewall.
  3. Click the Allow another app... button, and then Browse... in the opened Add an app window. If your options are greyed out in the Allowed apps window, click the Change Settings button to allow changes.
  4. In the File name text box, type *.* and press enter before navigating to slimevr.jar in your SlimeVR server folder and select it (if you cannot see files in this folder, try typing *.* and pressing enter again to show all files).
  5. Click the Add button to add the file to your firewall settings.
  6. Finally, make sure both public and private checkboxes are selected in the Allowed apps window before clicking OK to save the changes.

If adding SlimeVR to your firewall has not worked, you can try to diagnose the issue further with the following steps:

  1. Try completely disabling Windows Defender Firewall on your computer temporarily to test if the trackers will connect.
    • If the trackers only show up on SlimeVR when Windows Defender Firewall is disabled, then you have a problem with your firewall.
  2. Try pinging the tracker from your computer to see if it can be reached by opening Command Prompt (CMD) and run the command ping <IP>, where <IP> is your tracker's IP (ex. ping 192.168.0.1). You can find the tracker's IP using the "Serial console" under the "Settings" tab of the SlimeVR GUI.
    • If the command outputs something like Reply from 192.168.XXX.XXX: Destination host unreachable., then you likely have a problem with either your router or your firewall.
    • If the command outputs something like Reply from 192.168.XXX.XXX: bytes=32 time<1ms TTL=63, then you likely have a problem with either your network adapter or your network settings. You may need to enable broadcast packets (or something similar) on your router, as SlimeVR trackers broadcast to 255.255.255.255 to discover your SlimeVR Server.
  3. Try hosting a Wi-Fi hotspot either from your computer or your phone and connect your trackers to it to see if they will show up on SlimeVR using it.
    • If the trackers don't show up on SlimeVR, then you likely have a problem with either your trackers or your computer. It may be worth trying disabling your Windows Defender Firewall as per the first step, but using this Wi-Fi hotspot instead.
    • If the trackers show up on SlimeVR, then you likely have a problem with either your router or the network adapter you connect to your router with.

If none of these steps have helped you, you can find information about getting further help at the top of this page.

The trackers are connected to the SlimeVR server but aren't showing up

This is usually the result of an issue with the IMU. Plug in your Wemos D1 Mini and check through the serial console under settings in the SlimeVR server. You may see an error like one of the following:

[ERR] I2C: Can't find I2C device on provided addresses, scanning for all I2C devices and returning
[ERR] I2C: No I2C devices found
[ERR] I2C: Can't find I2C device on provided addresses, scanning for all I2C devices and returning
[DBG] I2C (@ D2(4) : D1(5)): I2C device found at address 0x68  !
[ERROR] [ErroneousSensor:0] IMU of type MPU6500 failed to initialize

The most common reasons for errors with the IMU are the following:

  1. You accidentally set the IMU wrong (i.e. set as MPU6050 when you have an BNO085)
  2. You accidentally selected the wrong board type (i.e. set as BOARD_SLIMEVR instead of BOARD_WEMOSD1MINI)
  3. The wiring is wrong (e.g. accidentally swapping around D1/D2 and SDA/SCL)
  4. There's an issue with the soldering (e.g. not enough solder, cold joint, or bridging between SDA and SCL)
  5. You're using a breadboard (Without soldering connections, the IMU often won't be able to communicate with the microcontroller)
  6. There's an issue with the IMU itself (e.g. burned trace while soldering, or the chip is downright DOA)

The trackers are connected to the SlimeVR server but aren't turning up on Steam

My trackers are bound to the wrong body part in SteamVR

  • If this is a problem in VRChat, try reducing the IK Calibration range to something smaller (e.g. 0.2).
  • If this happens in SteamVR, make sure your trackers are assigned to the right body parts in SlimeVR.

Your trackers are drifting more than expected

Make sure that when you turn on your tracker, it's lying on a flat surface. The sensors need to calibrate for 10-20 seconds in a stable environment.

My feet sink into the floor / I'm sliding a lot

This will be due to either your physical or bone length setup. Try:

  • Making sure "Skating correction" and "Floor clip" are enabled in the SlimeVR Settings > Tracking settings (doesn't work for Quest Standalone for now).
  • Running through the Automatic Body Proportions Calibration again.
  • Changing your IRL tracker mounting.
  • Adjusting your bone lengths manually by following the step shown here.

Trackers are moving in the wrong direction when I move

  • Use the experimental Automatic mounting calibration.
  • Make sure your mounting orientations for your trackers in the server are correct. (you might have to lie about them for certain setups)
  • You may have specified a wrong IMU_ROTATION value in your defines.h file. Take note of which trackers are the issue and refer to the configuring the SlimeVR firmware page to get the board's rotation right.
  • If it’s only off by a few degrees, shift your trackers inwards or outwards a bit, then full reset.

My avatar floats above the ground

  • Make sure your floor level is correct using OVRAdvancedSettings' fix floor function.
  • Increase your User Real Height in VRChat or any equivalent setting in other games.

My legs don't bend

  • Make sure you have upper leg trackers above your knees and assigned as "upper leg" trackers as well as lower leg trackers below your knees assigned as "lower leg" trackers.
  • Make sure your lower legs trackers are on your lower legs and not your feet.

My legs cross when sitting down

  • Use the experimental Automatic mounting calibration.
  • Try mounting your upper leg trackers more inwards.
  • Try mounting your upper leg trackers higher on your thighs or lower on your upper legs depending on your build.
  • Calibrate with your legs straight and a normal hip width (24-32) in your body proportions.
  • Use fast reset to correct leg crossing: assigning a keybind for resetting.

One of my leg is higher than the other

Shift your upper leg trackers a bit; try out other mountings for your upper leg trackers

AutoBone / Automatic body proportions calibration isn't working

If AutoBone isn't working properly for you, you can find a list of common issues and debugging information in the "Common Issues / Debugging" section of the body proportions configuration page.

SlimeVR is stuck at "Connecting to the server"

  • Update your SlimeVR Server with the installer

The SlimeVR window is stuck as a tiny window

  • Update your SlimeVR Server with the installer

WebView2 is missing / SlimeVR GUI crashes immediately / "panicked at ... WebView2Error"

It's possible that you don't have the required WebView2 component installed, you can download the WebView2 installer from https://developer.microsoft.com/en-us/microsoft-edge/webview2/consumer/. To ensure that WebView2 installs properly, run the WebView2 installer as an administrator (right click, then click "Run as administrator") and make sure the installer is running from the C: drive on your computer. If it's still not working, try putting the installer in the root of the C: drive (ex. C:\MicrosoftEdgeWebview2Setup.exe) and running it from there.

No serial device appears / "Looking for trackers" / "Connection to serial lost, Reconnecting..."

If you are having trouble with your tracker(s) not being detected for the "Connect trackers" step, not showing up in the serial console, not showing up in the web firmware tool, or not being detected in VSCode, then make sure you check the following:

  • If you are using official trackers, ensure that they are turned on and the blue light is blinking. If the blue light is not blinking, there may be other issues.
    • For most DIY trackers, they should be turned off as a safety precaution as the ESP should be powered by USB directly.
  • If you are using DIY trackers, ensure you are plugging in the microcontroller module (the ESP, like Wemos D1 Mini which usually has Micro USB), not the charging module (TP4056, which usually has USB C).
  • Ensure that your cable is a data cable. Some cables are charging only and therefore cannot be used to connect to serial.
  • Ensure that the appropriate drivers are installed. For official trackers and most DIY trackers, you'll need CH340/CH341 drivers. Some other DIY trackers need FT232 drivers.

You can easily determine the type of chip you have using Device Manager. Open Device Manager, and under one of the categories (usually "Ports (COM & LPT)" or "Other devices") you'll find one of the following:

  • CH340: "USB-SERIAL CH340"
  • FT232: "USB Serial Converter"

References

Created and updated by calliepepper, edited by emojikage, spazzwan, butterscotch.v