Hello everyone,
I create custom vehicle liveries for players in roleplay communities. I would like to request official support for assigning a runtime livery texture to an individual vehicle instance in FiveM.
The use case comes from a workflow I previously used on a RAGE roleplay server: I prepared a 1024×1024 PNG using the vehicle’s UV template, and players submitted the image URL through an in-game panel. The resulting design appeared on their vehicle and was visible to other players.
The essential requirement is that two vehicles of the same model can display different custom liveries simultaneously, without either vehicle affecting the other.
From the public API and source code I reviewed, AddReplaceTexture maps one shared texture to another. Creating a DUI or runtime texture provides the image, but does not itself provide a vehicle-instance-specific livery binding. SetVehicleLivery selects an existing livery index.
Prepared livery slots can provide a workaround within a limited pool, and additional model variants can expand that capacity. However, these approaches introduce slot allocation, capacity and asset-management constraints.
I would like to see a supported client-side API that accepts a target vehicle and a runtime texture dictionary/name, and applies that texture specifically to the vehicle’s livery on models with compatible materials and UV layouts.
The desired behavior would be:
-
Different instances of the same vehicle model can use different runtime livery textures.
-
Updating or removing one vehicle’s override does not affect other vehicles sharing the original texture.
-
Developers can clear an override and restore the original appearance.
-
Texture lifetime, cleanup and behavior during vehicle streaming are documented.
-
The vehicle’s normal livery material behavior, including lighting and transparency, is retained where supported.
Server resources could handle permissions, image validation, hosting and the distribution of vehicle-to-design metadata. Each client would load the approved image and apply the override to its local vehicle instance. Direct URL downloading and automatic image transfer would not need to be part of the native itself.
A useful validation scenario would be two vehicles of the same model, each displaying a different 1024×1024 design, viewed correctly by two clients. A resource should also be able to restore the correct assignments for a player who joins later or approaches after the vehicles stream in.
This would support player-run livery businesses, racing teams, sponsorship designs and personal vehicle customization. Reasonable texture limits, caching and visibility-based loading would be acceptable.
I have attached screenshots of previous livery work to illustrate the intended visual result.
Relevant references:
Is a supported mechanism for this already available that I have overlooked? If not, could vehicle-instance-specific runtime livery binding be considered as a platform feature?
Thank you.
