Common Errors
Last updated
Was this helpful?
Last updated
Was this helpful?
In this section, you will find answers to commonly encountered issues. Remember that most errors stem from incorrect configuration, lack of required resources, or insufficient modification.
Bear in mind that troubleshooting requires patience and precision. Try to carefully analyze the errors and systematically review possible solutions.
If the issue persists after verifying the configuration and available resources, please contact the support on the VMS Discord.
If you are using ESX, go to your database - the jobs and job_grades table, get the information about your job and the job_grades that you want to have access to the tuning menu:
In the above screenshot, you can see the job whose name is mechanic, so in a specific tuning, it should be set job = 'mechanic',
In the above screenshot, you can see several grades that fall under the mechanic job, so they should be included grades_access = {'recrue', 'novice', 'experimente', 'chief', 'boss'},
In the above screenshot, you can see the mechanic job, as well as several grades, so they should be introduced job = 'mechanic',
oraz grades_access = {'Recruit', 'Novice', 'Experienced', 'Advanced', 'Manager'},
Find these
For the options Wheel Size, Wheel Width, and Custom Suspension Height to load with the optimized method, they must be created on the server side and must be assigned with vehicle properties. By default, in ESX, there is a server-side function ESX.OneSync.SpawnVehicle
, which fulfills all the requirements - spawn on the server side and automatic setting of vehicle properties, but in the case of QB-Core, such a statebag is not assigned, so you need to enter it yourself in your garage system when the vehicle is created, example below