[BUG] helppp

[ApxAura]

when i am tryin to play a tv, it works in certain angles etc it will render fine then soon as i move to the left slightly, the tv goes black and then spams me with this error, anything i do to fix it doesnt fix it, just creates a new error on a diffrent line, would appreciate if anyone had some advice or a fix,,,,

[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
Fetching: https://qb-target/selectTarget with data: 1 (@qb-target/html/js/app.js:70)
Received BOLO update: [object Object] (@lgmods_anpr/html/script.js:1)
Fetching: https://qb-target/selectTarget with data: 1 (@qb-target/html/js/app.js:70)
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
Fetching: https://qb-target/selectTarget with data: 1 (@qb-target/html/js/app.js:70)
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
^1[qb-target] RaycastCamera returned nil values! Skipping this tick.^7
Fetching: https://qb-target/selectTarget with data: 1 (@qb-target/html/js/app.js:70)
Fetching: https://qb-target/selectTarget with data: 1 (@qb-target/html/js/app.js:70)

[NebelRebell]

Hi 👋

This is a known issue with RaycastCamera in qb-target and it’s not directly related to your TV script.

What’s happening

When you slightly change your camera angle, the raycast may stop hitting the TV prop and instead hit:

• world collision
• a render target surface
• or nothing at all

In those cases, GetShapeTestResult can return invalid / nil entity data.

Older versions of qb-target don’t fully guard against this, so RaycastCamera returns nil values and you get:

[qb-target] RaycastCamera returned nil values! Skipping this tick.

That’s also why the TV turns black — the interaction context is lost when the raycast fails.

---

Why editing random lines creates new errors

If you only patch a single native call (like GetEntityType or HasEntityClearLosToEntity) without fixing the return logic of RaycastCamera, another part of the loop will still receive invalid data and error somewhere else.

So the real fix is not changing one line — it’s making sure RaycastCamera:

• never returns nil
• always validates entityHit
• safely handles world / non-entity hits

---

Proper fix (concept)

Inside RaycastCamera you should validate before returning:

if not hit or not entityHit or entityHit == 0 or not DoesEntityExist(entityHit) then
    return playerCoords, 999.0, 0, 0
end

Instead of returning nil values.

This prevents the spam and keeps the loop stable.

---

In short:
This is a raycast validation issue in qb-target, not your TV script.

If you share your RaycastCamera() function I can point out exactly where the guard should be added 👍