$ ensure page_resource
starting…
starting…
A vehicle resource whose fxmanifest is written once and never touched again. Adding a car is making a numbered folder and dropping your files in. It ships with a working car already installed, so the first thing you do is watch it spawn, not debug your own model against a folder you can't be sure about.
Free, one step
Connect Discord and the download unlocks. This also adds you to the Trase.Dev server, which is where the support and updates live.
I only ever see your username and avatar. No email, no password, and you can leave the server whenever you want. Already in from another download? This unlocks straight away.
No mystery zip. Eleven files, listed in full, and it's the same template I use when I record.
Step one gets the resource running with the car it came with. Two to four are what you repeat for every car after that.
Put vehicle_template in your resources folder, add the one line to server.cfg, restart. The car in slot 1 spawns straight away, so you know the resource works before you touch anything.
For your second car, create data/2 and stream/2. The number is only a name. Nothing else in the resource needs to know it exists.
Your model files go in stream/2, your meta files go in data/2. Copy the ones from slot 1 if your model didn't come with a full set.
That's it. fxmanifest globs data/** and streams everything under stream/, so it finds the new car on its own. You never open fxmanifest.lua again.
No, and that's the entire point of this. The data_file lines are globbed as data/**, so a new numbered folder is found without the manifest ever mentioning it. Most vehicle packs make you add seven lines per car, which is where the typos come from.
One number per car, in both data/ and stream/. Nothing reads the number, it just keeps each car's files apart so a broken one is obvious and deleting it is dragging a folder to the bin.
Yes. Delete data/1 and stream/1 once you've seen it spawn and you have an empty template. It ships installed so the first thing you do is watch it work, rather than debug your own model against a folder you can't be sure about.
It's the full set of game layouts, which is what lets custom seat and animation setups resolve instead of falling back. It's data, it costs you nothing at runtime, and you can leave it alone.
Yes. Streaming a vehicle didn't change between them, so the same folder works on both. I test against Enhanced, so that's the one I'll support.
Almost always the spawn name not matching across vehicles.meta, carvariations.meta and handling.meta, or a missing .ytd. Slot 1 is a working reference, so diff yours against it before asking.
No. This is a streaming resource, so ESX, QB and standalone all treat it the same. Adding the car to a dealership or a job is your framework's job, not this folder's.
The template is mine and it's free to use however you want. The car that comes with it is an example, so check you're allowed to run any model you ship, including that one.