[SOLVED] "lactose-carbon-tango" when spawning add-on cars

MarcelR · 2018-08-31T08:05:22.537Z

GTA V version?
After Hours Update (Patch 1.44 / Version 1.0.1493.0)

Up to date?
Yes

Legit or Pirate copy?
Legit bought copy

Steam/CD/Social Club?
Steam

Windows version?
Windows 10 Pro 64Bit

Did you try to delete caches.xml and try again?
Yes. Still crashes.

Error screenshot (if any)

System specifications
AMD FX 6100 Six-Core Processor 3.30GHz
8GB RAM (DDR3)
NVIDIA GeForce GTX 1060 3GB

What did you do to get this issue?
I don’t know. My FiveM dowloaded a small update and it’s been happening ever since.

What server did you get this issue on?
Any server I join and try to spawn an add-on car on

CitizenFX.log file
CitizenFX.log (130.1 KB)

.dmp files/report IDs
Report ID: si-f8c0d60c4f8d4ce3bcce3f146215dc71
Dump file : 503f84a5-2e38-4bc8-9a08-ff083a3973d5.dmp (4.9 MB)

Also add what you already tried so far:
Clearing Client Cache
Reverting to an older version of simple trainer
Deleting “caches.xml”

MarcelR · 2018-09-10T21:01:17.264Z

[SOLVED] The error is caused by an error/exeption in the “handling.meta” file of a vehicle resource

XxBAYOU · 2018-09-25T09:04:55.058Z

how did you fix it i’m having the same issue

MarcelR · 2018-09-25T10:46:08.210Z

Run the handling.meta through an xml-validator. Itll most likely tell you where the exeption is in the file.

XxBAYOU · 2018-09-25T10:50:34.672Z

i got it fix i don’t know how i did’t change anything to fix it lol

desertbeer · 2018-09-30T05:28:44.306Z

mine is saying that there is nothing wrong with the handling file

captcarter25 · 2018-10-04T01:10:44.459Z

I have checked and double checked my handling.meta there are no issues, and still having this issue.

Bozza2067 · 2018-10-09T11:55:00.289Z

I’ve been having this issue aswell. In my case, the add-on cars were set to use handling data that weren’t in the handling.meta file. Make sure you’ve spelled the ID correctly and that the handling data is actually in the meta file.

imsonutz · 2018-11-01T20:43:58.618Z

I was having the same issue i fixed it by putting the handling.meta on top of the all the other metas in the resource.lua. Making it looks as below

files {
‘data/handling.meta’,
‘data/vehicles.meta’,
‘data/carcols.meta’,
‘data/carvariations.meta’
}

data_file ‘HANDLING_FILE’ ‘data/handling.meta’
data_file ‘VEHICLE_METADATA_FILE’ ‘data/vehicles.meta’
data_file ‘CARCOLS_FILE’ ‘data/carcols.meta’
data_file ‘VEHICLE_VARIATION_FILE’ ‘data/carvariations.meta’

16BitShooter · 2018-11-23T21:04:47.278Z

tried all of those and nothing worked. I noticed that the handling files that don’t work look very similar. I also checked all the other metas and found no errors on the xml validators.

Stephen_Evans · 2018-12-03T00:22:40.502Z

same here

Code_Zanther · 2018-12-04T09:04:29.812Z

Also having this, have tried everything above.

Calles27 · 2018-12-22T02:53:44.233Z

This can also be caused by changing the handling id in vehichles.meta to an invalid vehicle

16BitShooter · 2019-01-06T00:34:44.309Z

Already checked that, still no global fix on this issue
EDIT;
If your XML is valid and your resource.lua looks right, then check the handling id. If none of that works then the only way I’ve been able to fix it is by compiling the vehicle on your own. Meaning, the only thing you take from the download is the streamable items. (.y files) The only downside is if you don’t know how to make or modify the .meta files you are SoL. If you do know what your doing when it comes to the .meta files then this is a bit of an upside for you. You will be able to make the car pretty much how you want it. Later on if you guys want I’ll post a youtube video here explaining this more…
EDIT; Here is my video explaining the fix, sorry about the rambling… You should get the point though…

Calles27 · 2019-01-07T14:32:30.925Z

I understand what your saying but a youtube video would be great…

16BitShooter · 2019-01-08T04:41:26.463Z

just finished rendering it, it’s uploading right now

EDIT; Video is now up!

system · 2019-02-07T04:41:30.968Z

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.