Troubleshooting

Two commands answer most of this page. /tDetSources reports, per configured radar entry, whether the resource is running, which mechanism is in use, what was read just now, and whether anything is transmitting; /tDetSources test checks the display half separately.

tdetector_diag, on the server console, prints the version, the tLib version, every Config value in effect and every startup config-check message. Paste that into a support thread instead of your config file — it is pre-redacted. Grant it with add_ace group.admin command.tdetector_diag allow.

No alert ever appears

The commonest report, and usually the radar wiring. tDetector only picks up players whose radar reports itself and has an antenna switched on.

1. Run /tDetSources. Nothing transmitting while your radar is keyed up means the wiring is wrong — go to Integrating any radar.
2. Confirm an antenna is in XMIT mode, not just the unit powered on.
3. Check range and sensitivity. A radar reporting its own reach — tRadar does — is heard at twice its range: a 150 m beam at 300 m, well inside 500. Otherwise it is Config.detectionRange on Highway, 45% on City.
4. Check you are not on Auto while stationary. Auto is City below Config.autoSensitivityAbove (45 MPH), which includes standing still to test.

Remember a detector never hears its own radar, so detection needs a second player.

requires tLib v1.0 or newer — installed tLib is v0.6

Fix — update tLib to 1.0 or newer and restart. Do not downgrade tDetector instead: an outdated tLib loads happily and fails later with a cryptic No such export.

The resource never starts, console names a missing dependency

tDetector declares dependency 'tLib', so the server refuses to start it when tLib is absent.

Fix — install tLib and add ensure tLib. Those two lines need no ordering. Your radar resource has no such declaration, so order that one deliberately.

"No such export", or alerts stopped after an update

You added an export to somebody else's radar and their update overwrote it. It fails silently.

Fix — run /tDetSources; a working entry now reporting its export as not present confirms it. Re-add the export, then move it into a bridge resource.

Alert on screen, no tone

The detector is muted, by the MUTE key or by auto-mute below Config.autoMuteBelow (20 MPH).

Fix — stationary or crawling, auto-mute is working as intended. Set Config.autoMuteBelow = 0 to disable it server-wide, or press MUTE.

No alert tones at all

Fix — check the mappings in /tdetector → Sounds and that the files they name exist under layouts/sounds/. An unassigned slot falls back to BLIP; BOGEY has no fallback and stays silent until you assign one.

The HUD shows no speed, or vanished when I got out

Both are being on foot, and both are correct. The detector stays powered and the display returns when you get back in. You do not need to run /tdetector again.

My layout doesn't appear in the dropdown

Layouts are enumerated at resource start. The commonest cause by far is a missing module.json — a folder holding only ui.html is not discovered and raises no error.

Fix

1. Confirm the folder sits directly under layouts/ with both ui.html and a module.json declaring "kind": "layout".
2. Confirm id matches the folder name exactly, and version looks like 1.2.3.
3. Check it is not named default, sounds or themes — all reserved.
4. Run restart tDetector.

/tdetector says I don't have permission

Config.access is { mode = "ace", … } and you lack the ace it names.

Fix — grant it, or set Config.access = { mode = "everyone" } and restart tDetector. The check is server-side on every /tdetector, so a granted permission works without a reconnect.

add_ace group.mechanic tdetector.use allow
add_principal identifier.license:xxxxxxxx group.mechanic

The toggle button is greyed out

Config.toggleRequiresItem = true. The dialog still opens for speed unit, layout and reposition; only toggling moves to the QBCore item.

Fix — use the item, or set Config.toggleRequiresItem = false.

The Marketplace and Sounds tabs are missing

Those are gated by tLib's admin level, not by the ace in Config.access.

Fix — grant tlib.admin or tlib.superadmin. The server re-checks on every sound write, so there is no client-side way around it.

the "radardetector" item is wired to the detector -- but qb-core is not running

Item support is QBCore-only.

Fix — ensure qb-core above tDetector, or turn off the key the message names. The rest of tDetector keeps working. With Config.toggleRequiresItem = true the item is the only switch, so the toggle is dead until qb-core runs.

My HUD position reset after a restart

HUD placement lives in tLib, keyed to your player identifier.

Fix — if your license or Steam ID changed, the saved placement belongs to a different player and there is nothing to recover. Otherwise reposition through /tdetector → Reposition HUD or /tlibhud.

It alerts constantly in town

Working as intended, with three controls.

1. Switch sensitivity to City — it cuts X and K reach to 45% and leaves Ka at full.
2. Press MARK on a repeat offender for a permanent GPS lockout.
3. Leave it to AutoLearn — three drive-bys past the same doorway.

For none of it, set Config.falseAlerts.enabled = false. See False alerts.

Known limits

None is fixable by reconfiguring: instant-on bursts shorter than Config.radarStateInterval can be missed; an edited radar export disappears on the radar's next update; event adapters can desync on a missed edge; a radar exposing nothing is unreachable even by a bridge; and a marketplace skin is only as compatible as its own geometry.

Still stuck

Open a ticket with the output of /tDetSources, the radar sync section of tdetector_diag, whether /tDetSources test looked right, your Config.radarResources block, the radar resource name and version, and the exact console error as text.

Next steps

• Integrating any radar — the full wiring reference.
• Usage — behaviour that looks like a fault and is not.