# Common Issues
## Stuck Props
* If you have props stuck on the grill you can use the `/clearGrill` command
* Requires the proper job to use this
* You can also use the [export](/documentation/premium-scripts/envi-food-truck/exports.md) to do this via code if you prefer
* Bypasses job check
***
## Third Eye / Target not working
### Incorrect Livery
The most common issue with Third Eye / Target not working is that your vehicle does not have the correct livery
* If you're seeing an all black vehicle then you do not have the correct livery, therefor this is not considered a food truck (unless you've explicitly added support for this livery in the config file)
* Correct default livery for `voodoofoodtruck`
* Correct default livery for `voodootacotruck`
***
### If using qb-target
Add Custom Bones
If qb-target isn't working it's most likely due to the fact that qb-target doesn't support custom vehicle bones, which is required for this script to function properly.
1. Navigate to `data/bones.lua`
2. Replace the very first line of that file with the following code
3. ```lua
local Bones = { Options = {}, Vehicle = { 'chassis', 'windscreen', 'seat_pside_r', 'seat_dside_r', 'bodyshell', 'suspension_lm', 'suspension_lr', 'platelight', 'attach_female', 'attach_male', 'bonnet', 'boot', 'chassis_dummy', 'chassis_Control', 'door_dside_f', 'door_dside_r', 'door_pside_f', 'door_pside_r', 'Gun_GripR', 'windscreen_f', 'platelight', 'VFX_Emitter', 'window_lf', 'window_lr', 'window_rf', 'window_rr', 'engine', 'gun_ammo', 'ROPE_ATTATCH', 'wheel_lf', 'wheel_lr', 'wheel_rf', 'wheel_rr', 'exhaust', 'overheat', 'seat_dside_f', 'seat_pside_f', 'Gun_Nuzzle', 'seat_r', 'misc_a', 'misc_b', 'misc_c', 'misc_d', 'misc_e', 'misc_f', 'misc_g', 'misc_h', 'misc_i', 'misc_j', 'misc_k', 'misc_l', 'misc_m', 'misc_n', 'misc_o', 'misc_p', 'misc_q', 'misc_r', 'misc_s', 'misc_t', 'misc_u', 'misc_v', 'misc_w', 'misc_x', 'misc_y', 'misc_z' } }
```
If the information in the expandable above doesn't fix your issue and the vehicle has the correct livery on then try the following:
* Typically this manifests as only being able to see "Push Vehicle" (and possibly one other option)
* qb-target really does not like several third eye locations in close proximity to one another
* One way to help this is to increase the target distance in the config file
* The other way is to upgrade from qb-target to ox\_target
* If you go this route you need to use [v1.16.0](https://github.com/overextended/ox_target/releases/tag/v1.16.0) as any version higher than that is not compatible with qb-core
* Installing v1.16.0 is a simple drag and drop. You do not need to update any scripts to change from using qb-target to ox\_target as this version automatically converts qb-target options to ox\_target
* Follow the [install guide](https://overextended.dev/ox_target#config) called out in their docs if you want to change options such as default keybind, or using Right Click vs Left Click to enable the mouse cursor to select options
***
## No ingredients in the truck
If `Config.RealisticMode` is enabled, the built-in ingredient shop is intentionally disabled.
You need to supply ingredients through your own economy or item flow.
***
## Orders disappear
If orders vanish unexpectedly, check `Config.MaxActiveOrders`.
Older orders are removed first when the order cap is exceeded.
***
## Payment goes to the wrong place
Check the `society.payToSociety` setting for that truck livery.
***
## Grill cleanup
If props are stuck:
* use `/clearGrill` if your job can use it
* or call the export from code if you need to bypass that check
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://envi-scripts-organization.gitbook.io/documentation/premium-scripts/envi-food-truck/common-issues.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.