Troubleshooting
This page covers problems inside Studio: avatars, presets, capture, and playback. If pairing, connection, or calibration itself is failing, see Control Center - Troubleshooting. If the device seems physically at fault, see Hardware - Troubleshooting.
Installer blocked by Windows Defender SmartScreen#
This is expected on first install. Click More info, confirm the publisher is Deep Divers Ltd, then click Run anyway. See Studio - Install.
Device not available when creating an avatar#
The device list only shows devices already paired, connected, and (for haptics) calibrated in Control Center. Complete that first, then return to Studio. See Control Center - Overview.
Avatar doesn't move, or mocap looks wrong#
- Confirm the device is enabled in the Device Manager panel. An enabled device shows a blue outline; a disabled one is greyed out.
- Recalibrate. 6-axis calibration (the default) is required after every Studio restart, and again whenever the avatar stops tracking correctly.
- Redo the calibration I-pose cleanly: full height, hands straight by your sides, feet hip-width apart and flat.
- If you're testing 9-axis mode, move away from ferromagnets and large metal objects, and note that manual 9-axis calibration is still test-mode only and not meant for production capture. See Studio - Data Capturing.
No haptic sensation during preset playback or simulation#
- Confirm the device is enabled in the Device Manager panel (blue outline).
- Confirm haptic calibration was completed in Control Center - Calibration. Studio doesn't calibrate haptics itself.
- Check the preset's or effect's target device version matches your connected device's version. A mismatch between, for example, a TESLASUIT 4.5.6 preset and an XR5 device will not play correctly.
- Check global haptic power in Control Center isn't set too low.
- Remember Simulation-tab brush strokes can't be recorded. If you're expecting recorded output from simulation, that's expected behaviour, not a bug: build a preset instead.
PPG data missing or looks wrong after capture#
- Confirm the avatar was created with the Biometry (PPG) system selected before recording. PPG isn't added retroactively to an existing capture.
- Confirm biometry calibration was completed in Control Center - Calibration before the recording, not after.
- Confirm sensor placement: the TESLASUIT sensor sits on the outer right shoulder, where the deltoid ends (upper-right sleeve of the jacket).
.fbx export option is missing or greyed out#
FBX export is only available for the Motion Processed data type. Other data types (PPG raw, raw sensor streams, and so on) export only as .csv. See Studio - Data Capturing.
Studio is slow or unresponsive with a large recording#
Long, multi-stream recordings are heavy to load and visualise, especially on minimum-spec hardware. Check your setup against Studio - Requirements and consider trimming the recording or working with fewer Timeline components at once (the Timeline supports at most 20; the Chart Viewer at most 30).
Not a Studio issue?#
- Device won't pair, connect, or update at all → Control Center - Troubleshooting
- Calibration itself fails, or no sensation even outside Studio → Hardware - Troubleshooting
When to contact support#
Contact support@teslasuit.io with:
- Your Software Bundle version.
- Your device's firmware version (see Control Center - Device Report).
- The affected preset, effect, or scene file, if relevant.
Note
Attach the log files too. Copy the whole logs folder from %ProgramData%\Teslasuit\logs and include it with your message.
