Full Body Tracking Charging and Pre-Session Checklist

A useful full body tracking charging checklist answers a simple question before straps go on: is every tracker in the set ready to start? Give each unit a numbered parking spot, charge it according to the instructions for that exact hardware, then confirm the whole set rather than checking one device and assuming the rest match.

Battery life and charging speed vary by device, condition, power source, and use. This checklist does not promise a runtime or tell you that one light color means the same thing on every tracker. It gives you an observable start gate: the expected tracker count is present, charging is finished or disconnected as directed, each unit powers on, and every available status can be checked before you move to the complete full body tracking setup workflow.

Use a numbered charging map

A multi-tracker routine becomes easier when each unit has a fixed identity before it reaches your body. Number the trackers or their parking spots in a way that matches your existing setup notes. The number is not a body-role assignment. It is a quick way to notice that a parking spot is empty, a cable was skipped, or a device still needs attention.

At the end of a session, return the complete set to the same area. At the next start, inspect that area before touching the straps. Record only what you can observe from the hardware or its companion software. Depending on the tracker, that may be a displayed percentage, a documented indicator, or a confirmed power-on state. If the device does not expose a precise percentage, do not invent one.

Keep the maker’s charging and handling instructions with the charge station, especially if your set mixes hardware. Official SlimeVR charging rules apply to official SlimeVR trackers. Vive, FBTKit, DIY, and other third-party units may have different ports, indicators, and requirements. A shared shelf does not make their instructions interchangeable.

Confirm the whole set before straps go on

Start with the planned count. Disconnect charging and power on each tracker in the order required by its documentation. Watch one unit long enough to identify its normal response, then move to the next. This is slower than tapping the first switch and grabbing the straps, but it removes the most common uncertainty in a large set: which unit was never checked?

If your software reports tracker status, compare the list with the numbered parking spots. The point is not to diagnose a connection problem on this page. It is to confirm that the physical set and the visible software set agree before wearing. A device that is physically present but absent from the expected list has not passed the start gate.

For the prebuilt tracker workflow described by SlimeVR Quick Setup, powered-on trackers are placed on a flat surface for sensor calibration before wearing. Follow that device and software sequence where it applies. After the power state is known, use the pre-calibration tracker wear order instead of mixing charging checks into body placement.

Use one start gate, not a runtime guess

A reported percentage or indicator is a current observation, not a guaranteed session length. Do not average the set, estimate how long a low unit will last, or use the highest status as proof that every tracker is ready. The weakest or uncertain unit determines whether the planned set passes this checkpoint.

This gate prevents charging from becoming a vague explanation for every later symptom. Once the set passes, preserve that result and move forward. If another step fails, diagnose that step with its own evidence.

Hand off after the power state is known

Charging readiness ends before the detailed fit and movement work begins. Put the trackers on in your saved order, then use the tracker strap fit and placement guide if a strap or contact point needs attention. Do not keep reconnecting chargers while changing fit variables, because that makes the start record harder to interpret.

Clear and check the movement area with the small-space FBT room guide. Then complete the beginner calibration sequence. Those pages own room layout and calibration details. This page only hands them a complete set whose available power state was checked first.

Route an incomplete set without widening the checklist

If a powered tracker does not appear where your workflow lists devices, use the focused guide for a tracker missing from the VR device list. That page can isolate detection and connection evidence. Repeating the charging map is useful only when the power state itself remains uncertain.

If the symptom does not fit the charging gate, use the general FBT symptom router. If all trackers passed the start gate but a calibration result is suddenly unusable, go to the bad calibration reset guide. These handoffs keep one uncertain tracker from turning a short charging check into random changes across the whole setup.

Plan a repeatable charge station

Build the station around the kit you actually own: one numbered spot per unit, a place for the device-specific instructions, and enough room to see whether every expected piece has returned. If you are reviewing FBTKit, use the current FBTKit product page for charge-station planning as the authority for current included parts and options. This article does not repeat volatile or unverified battery, cable, price, or stock claims.

The station does not need a special dock or a decorative display. It needs to make absence obvious. A compact tray can work if each tracker has a visible position and the cables are not mistaken for proof that charging was completed. The final evidence is the pre-wear start gate, not the appearance of the shelf.

Copy this card for the next session

• All numbered parking spots are filled.
• Each tracker was charged using its own documented method.
• Charging is finished or disconnected as the device instructions require.
• Every tracker received an individual power-on check.
• The physical count matches the available hardware or software status list.
• No runtime was guessed from another tracker, another model, or an undocumented light.
• The set passed before straps, room checks, and calibration began.

Write the date and any uncertain unit number on the card. That small record helps you resume at the failed checkpoint instead of restarting the entire setup from memory.

FAQ

When should a charging check happen before an FBT session?

Return the set to its charging area after use, then run the observable start gate before straps go on. Check every expected unit again rather than treating the previous session’s routine as proof that the set is ready now.

How can you confirm every tracker is ready without quoting battery life?

Count the complete set and use the documented status available from each device or its software. Record the observed state only. Do not convert it into a promised number of session hours.

Should tracker straps stay attached while the devices charge?

Follow the instructions for the exact tracker and strap system you own. The checklist does not assume that attached or removed straps are correct for every product; it only requires a repeatable parking spot and a complete-set check.

What belongs on a tracker charging status card?

List the expected tracker numbers, the observed charging or power state for each unit, the check date, and any unit that did not pass. Keep runtime estimates and undocumented indicator meanings off the card.

What should you do if one tracker is not ready at the start gate?

Stop before wearing the set and isolate that unit’s observable state. Repeat its product-specific charging check or use the focused detection route if it powers on but does not appear in the expected software list.

Official sources

• SlimeVR Docs: Quick Setup
• SlimeVR Docs: Safety Guides

Sources and the current FBTKit product listing were checked on August 10, 2026. Official SlimeVR handling instructions apply to the hardware named by that documentation and are not treated as specifications for FBTKit, Vive, DIY, or other third-party trackers. No battery duration, charging-speed, electrical, or certification claim is made here.