TIMMYG StudiosTroubleshooting
Symptom-first fixes for tRadar: No such export, /tradar doing nothing, a blank HUD, an empty layout picker, a missing plate reader or remote, and blank windows.
Most of these are load order, an access setting, or a feature that ships off. tRadar has no database, so a database error belongs to another resource.
No such export, or tRadar fails to start
No such export naming a tLib function, or SCRIPT ERROR @tRadar/... at startup: tLib started after tRadar, or is older than v1.0.
-
Put tLib first.
cfgensure tLib ensure tRadar -
Check the version — tRadar declares
tlib_min_version '1.0'. -
Restart the server, not
refresh+restart tRadar— the load order is what changed.
F5 does nothing
Run /tradar_deploy in chat; it is the command the key is bound to.
- The command works, the key does not. Something else has claimed F5. Settings → Key Bindings → FiveM → tRadar: Radar: deploy, then remote, and rebind.
- Neither works. It is a refusal — see the next section.
F5 never stows: a third press closes the remote and leaves the radar up. Stowing is the remote's STOW key, or Stow Radar in /tradar. With Config.remoteEnabled = false the second press stows.
/tradar does nothing
One of three access checks, answered by the server.
| Chat message | Setting |
|---|---|
| "You don't have permission to use this." | Config.access |
| "The unit is dash-mounted — get in a vehicle first." | Config.requireVehicle |
| "This vehicle is not fitted with a radar unit." | Config.vehicleClasses |
No message at all means mode = "job" on a framework outside the six resolved, or "item" on an inventory outside the nine. tradar_diag prints what was detected.
Access is re-checked on every /tradar, so a grant needs no reconnect.
Other things that are missing
| Symptom | Cause | Fix |
|---|---|---|
| HUD blank, nothing drawn | You installed the source zip, which has no built files | Install the release zip |
| Layout picker empty, or a skin missing | The skin's device class, not its folder name | data-radar-device-class on the root element must be radar, plate or remote |
| No plate reader | It ships off | Config.plateReaderEnabled = true, restart, then place the window with the HUD editor |
| No remote | It is drawn only in keypad mode | F5 with the radar already up. Place it with Reposition Remote in /tradar |
| A key on a custom skin is dead | data-hud-btn names an action the engine does not answer | Check the action list. Exact strings: lock:front:fast, not lockFrontFast |
Plates read but never show a flag
Nothing is answering the read. Any or all of:
- CAD bridge:
Config.integrations.cad.enabled = true. No API key to set, see CAD and ALPR. - The BOLO tab of
/tradar, which needsConfig.plateReaderEnabled. - Your own handler on
tradar:plateRead, answering withsetPlateFlag.
No flag means nothing answered, which is not the same as clean. tRadar never prints CLEAR.
The bridge is on and still nothing? Run tradar_diag; the CAD page maps each line of its integration section to what to change. Commonly provider names a CAD that is not running, which turns the bridge off rather than falling through, or the NPC filter is doing its job. Fixed when asked climbs.
Every plate reads NO ANSWER? The CAD is being asked and is not answering. A few are normal — SonoranCAD allows 30 requests a minute for a whole community. If it is every read, check timed out: a slow CAD wants a higher timeoutMs, a throttled one wants the NPC filter left on.
Every window is blank but the unit is powered
| What the glass shows | Cause | Fix |
|---|---|---|
| HOLD where XMIT should be | Stationary mode above Config.stationaryMaxSpeed | Stop, or press MODE |
| TEST lit red | A latched self-test failure, only possible where Config.selfTestFailChance was raised | Press TEST. A faulted unit stays off the air until a check passes |
| RFI lit amber, patrol speed still shown | Interference inhibiting the target windows | Move, or wait Config.rfiHoldMs after the source stops |
RFI ships on; its default source is another tRadar on the same band within Config.rfiRange. The patrol window keeps running under it and a locked window survives, so a glass blank apart from patrol speed is almost always this. The CHX-800 carries no RFI legend, so there that pattern is the only tell.
Targets read but the numbers look wrong
Usually tRadar working as designed.
Patrol-speed shadowing. Ships on at Config.patrolShadowPull = 0.2; 0 disables it.
Correct, and not configurable — a crossing vehicle reads low, as a real gun does.
Correct. A reading smearing more than Config.accuracyMph across the sample is refused. A hard turn refuses everything at once.
Correct. Config.rangeFactorMax ships at 2.0; set it to 1.0 and nothing out-reaches a car.
Config.coneAngle is a half-angle: antennas quoted 12–15 degrees wide are 6–7.5 here.
Config.forkHz names a fork that does not match the band. The published Ka fork is cut for 35.5 GHz, which at a 34.7 GHz head reads 66 in perfect calibration. Set it to nil.
Calibration tolerance. Config.calibrationHighMph and Config.calibrationLowMph draw a fixed offset at every power-up; both ship at 0.
Still stuck
Get in touch with the exact console error as text, your tLib and tRadar versions, the relevant lines of config.lua, and what you did.
tRadar
Still stuck? Support can answer it directly.
Was this page helpful?