Skin Naming Convention??

[TigersharkBAS]

Not trying to cause unnecessary overhead, but should we introduce some kind of community std. regarding skin naming.

 

If you try out a few skins you end up having the same skin name without knowing who authored it.

 

 

For example:

 

3 letter author code - Unit code - Unit name - CAG/XO/LINE - Year(optional) - BU# )optional

 

TSH VFA-195 Dambusters (2003) CAG BU164908

 

At least at the folder naming level this would be great.

[Rudel_chw]

Not trying to cause unnecessary overhead, but should we introduce some kind of community std. regarding skin naming.

 

I fully agree. Currently I always rename the skins I download in order to both credit their authors and making them easier to find on the Mission Editor .. my standard is:

 

Country - Descriptive name (by author)

 

Example:

 

 

I rename both the folder and the name within the description.lua

 

If the community sets a common standard, I would adopt it, as it would make so much easier to share missions that make use of custom liveries.

 

Best regards

[TigersharkBAS]

Nice!

[Rudel_chw]

Nice!

 

 

 

Seems like we are the only ones that care about this issue :)

 

 

To me it makes sense to have proper names as it makes the ME easier to use, for example these are my livery options for a ficticious german Ka-50:

 

 

 

 

For countries that dont exist on DCS, I name their liveries after the most similar country, so for example the latin-american liveries I have them under "Spain" :) like this:

 

 

 

 

Yes, I've to update some of them, as Mexico was recently added to DCS ... but you get the idea :D

 

 

Cheers!

[TigersharkBAS]

He he...to be fair we've posted this in a particular forum area dedicated to a single airframe. It's probably a discussion for the skinning forum in general.

 

But yeah...doesn't seem like there is much appetite.

 

I would say we just document what the standard is, and the link to it in a read me or the details section of the DCS Files area. Set the example....see if other follow.

 

End the readme saying "This skin conforms with the community standard defined here <insert url to standard>"