This update includes changes to the Custom Cars system. Examples of all new features can be found in "EXAMPLE CAR ONLY FOR CREATORS".
All new features are optional, and existing vehicles should continue to work without any changes.
New Features
1. Paintables Texture Resolution
The general.paintablesResolution field in data/properties.json.
Allowed values: 256, 512, 1024.
2. isVisualSubpartAndBelongsTo Combined with openableParentId
Both keys can now be used in a single customPart.json.
Part visibility is controlled by isVisualSubpartAndBelongsTo, while its position in the hierarchy (e.g. under a door or hood) is controlled by openableParentId.
3. Video Support
A videos folder, containing a separate subfolder for each video.
Required:
Exactly one .mp4 file.
A videoData.json file containing the following fields:
videoId (must be unique).
meshIdToDisplayOn (a non-paintable partId on which the video will be displayed).
textureWidth and textureHeight.
Videos do not play automatically. They can be started and paused using an action trigger with triggerCustomActionId matching the videoId.
Example: videos/example, screen non_paintables/video_screen, action trigger actionTriggers/video_player.
4. Entering Triggers and Exit Positions
The following fields are available in data/properties.json:
leftDockTriggerPosition
rightDockTriggerPosition
leftDockUndockPosition
rightDockUndockPosition
All fields are optional.
Example: data/properties.json.
5. Action Triggers
An actionTriggers folder containing a separate subfolder for each trigger.
Required:
actionData.json
An activatedTrigger folder containing one .obj file (used to calculate the trigger's bounding box).
One of the following fields is required in actionData.json:
triggerPredefinedAction (MAINTENANCE, ENGINE, RADIO, LIGHTS).
triggerCustomActionId (an openable ID or a videoId).
Optional folders:
deactivatedTrigger
activatedMesh
deactivatedMesh
activationSound
deactivationSound
Optional fields:
openableParentId (reparent, works the same way as for vehicle meshes).
requiredPartId (the trigger only exists when the specified part is installed).
activationText
deactivationText
The example vehicle available on the Workshop contains all possible action trigger variations in its actionTriggers folder. This includes an openable front-left door with one trigger for opening it and another trigger for lowering the window.
6. Part Mounting Triggers
Every part with "isObtainable": true can have a mountTrigger subfolder containing one .obj file (used to calculate the trigger's bounding box).
Without a mountTrigger, the part is installed using the vehicle's shared trigger, just like before.
One trigger handles one part, so if there are multiple variants (e.g. different spoilers), I recommend placing their triggers next to each other to prevent them from overlapping.
7. Custom Cars Menu
The Custom Cars menu now supports more installable parts and can be scrolled.
8. Speed, RPM and Fuel Gauges
A gauges folder.
The example vehicle includes support for all three types of gauges.
9. Vehicle Subscription Handling
Unsubscribed vehicles will now also disappear from the game.
The vehicle's saved state is preserved, so after subscribing again, it will return with all its previously installed parts.
10. Expanded Debug Menu in Developer Mode
Y – Respawn the test vehicle.
1 – Show colliders.
2 – Show openable pivots.
3 – Show mounting triggers.
4 – Reload gauges without respawning the vehicle.
5 – Generate missing mounting triggers (paintables and non_paintables only).
If you have any questions about the new Custom Cars features, feel free to join our Discord! I'll be happy to answer any questions.