Shifty: Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)

2026-05-29T06:31:28Z

Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)

New page

« [[Player Guide]]

Got a livery you'd like to see on the VRS server? You can upload it yourself. VRS runs an automated pipeline that checks new uploads and, if your livery is packaged correctly, adds it to the livery pack for everyone -- [[Player Guide/Open Mod Manager|OMM]] users pick it up on their next launch and it's announced in the <code>#liveries</code> Discord channel. In the normal case there's no staff hand-off.

__TOC__

== 1. Get an upload account ==

Liveries are uploaded through the VRS file-share (ProjectSend) at [https://victorromeosierra.com/upload/ victorromeosierra.com/upload]. Use the '''Register''' link on the login page to create an account, then log in. This is a separate account from Discord and from the game server.

== 2. Package your livery ==

Zip your livery in the standard DCS livery layout, with the '''aircraft folder at the top of the zip''':

<pre>
FA-18C_hornet/ <- DCS aircraft folder name (top level)
My Squadron Skin/ <- your livery's name
description.lua <- the standard livery definition
textures.dds <- your texture files
preview.jpg <- optional (see below)
</pre>

Key rules:

* '''The top-level folder must be the aircraft's DCS folder name''' -- the exact name DCS uses under <code>Saved Games\DCS\Liveries\</code> (for example <code>FA-18C_hornet</code>, <code>F-16C_50</code>, <code>A-10C_2</code>, <code>Mi-24P</code>). The [[Player Guide/Downloads#Liveries|Downloads page]] lists the folder name for every aircraft we carry.
* '''Include only livery files''' -- textures (<code>.dds</code>), <code>description.lua</code>, and images. <code>description.lua</code> should be the normal livery definition (the list of texture mappings) and nothing more; don't add extra scripting.
* '''One livery per upload''' is the cleanest approach. The per-aircraft pack is rebuilt for you, so you don't need to bundle anything else.

== 3. (Optional) Add a preview image ==

If you want a thumbnail shown in the <code>#liveries</code> announcement, drop a <code>preview.jpg</code> in your livery's folder:

* Filename <code>preview.jpg</code> (lowercase), at the root of the <code><livery>/</code> folder.
* JPEG, sRGB, at most '''256x256''', under about '''50 KB'''.

Leave it out and the VRS logo is used instead. A missing or oversized preview won't get your livery held back.

== 4. Upload ==

Log in to [https://victorromeosierra.com/upload/ the file-share] and upload your <code>.zip</code>. There's no special category to pick or form to fill in -- just upload the file.

== 5. What happens next ==

* Within a few minutes the upload is detected and checked automatically.
* '''If it's a valid livery''', it's added to that aircraft's pack and published. OMM users auto-update on their next launch, and a post appears in <code>#liveries</code>.
* '''You won't get an individual success or error message.''' If your livery doesn't show up in <code>#liveries</code> within a few minutes, ask in the <code>#liveries</code> Discord channel and staff will take a look.

== Replacing or removing a livery ==

To replace a livery, upload the corrected zip, then rename your '''old''' file on the share to include '''Old - Do Not Use''' in its name. The pipeline skips files flagged that way, so only your new version gets published.

== See also ==

* [[Player Guide/Downloads|Downloads]] -- installing the livery packs, and the per-aircraft folder names.
* [[Player Guide/Open Mod Manager|Open Mod Manager]] -- the manager that auto-installs published liveries.

Player Guide/Contributing Liveries - Revision history

Shifty: Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)