MyLMU Telemetry runs entirely in your browser. A few setup choices make a big difference for smooth loading and comfortable analysis.
Desktop vs mobile
Telemetry works on phones and tablets, but desktop is the recommended experience:
| Desktop | Mobile / tablet | |
|---|---|---|
| Layout | Full Track Map, Pit Wall, traces, and Setup side by side | Simplified layout; some panels hidden or stacked |
| Shortcuts | Full keyboard controls (Space, F, M, etc.) | Touch-first controls; fewer shortcuts |
| Analysis depth | All Pit Wall views, sector tools, and custom channels | Core replay and key stats; not every desktop panel |
If something looks missing on a small screen, open the same file on a desktop browser — you are usually seeing a mobile layout, not missing data.
Screen size and fullscreen
- Use a comfortably sized browser window. Very narrow windows squeeze the map, replay bar, and charts together.
- On Track Map, press
For use the fullscreen control to give the map more room — see Fullscreen and cinema mode. - Pit Wall remembers panel widths per browser; drag the divider between map and charts if either side feels too small.
If the viewer is slow or hard to open
Try these steps before assuming the file is broken:
| Step | Why it helps |
|---|---|
| Close other browser tabs | Telemetry loads large datasets into browser memory |
| Quit or minimize heavy apps — games, stream overlays, capture software, other 3D apps | Frees CPU and GPU for 3D replay and charts |
Switch to 2D map (M on Track Map) | Much lighter than 3D WebGL — see 2D map |
| Close unused overlay panels on Track Map | Each open modal adds render work |
| Open the file in a fresh tab | Clears a stuck viewer session |
| Use a current desktop browser (Chrome, Edge, Firefox, Safari) | Best WebGL and memory support |
Symptoms like long initial load, replay stutter, or a black 3D view often improve after reducing browser and system load.
Large files
Long races can produce 50 MB+ .duckdb files. Those are supported (Pro has higher upload limits) but need more memory and may stutter in 3D until you switch to 2D. See Large file performance.
3D-specific issues
Black screen, WebGL errors, or cinema mode stuck? See 3D view issues.