Severity:Low
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)
Marketplace package name: Asobo_FA18
Context: Asobo_FA18 in the base game without mods
Bug description: The stock Asobo FA18 missing attachment.cfg’s necessary for livery decals to be applied to the moving parts of the aircraft. These can be added along with the livery package, but it’s not ideal as anyone can write a file to that location and could change the tags. It would be much better if these where included by default.
The following folders need attachment.cfg with tags:
function_exterior
function_interior
part_exterior_front
part_exterior_rear
part_exterior_wingleft
part_exterior_wingright
part_exterior_gear_front
Repro steps:
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content
Tags are used to selectively load part of a livery. By associating a list of tags to an attachment the related texture.[tag_name] and model.[tag_name] folders of the livery will be loaded when instancing this attachment. The models in model.[tag_name] will be merged to the attachment and the texture.[tag_name] will be listed first in the list of texture directory fallbacks.
You need tags if you want a part of your livery to only be displayed if the attachment using that tag is used by a variation.
So if you want to put a decal on a float of an aircraft that also has wheels and skis variations, you will need tags so that your decal is only showing when the corresponding variation is used.
Regarding decals following moving parts, your livery being exported as a submodel, identifying which parent node of the original model you want to be attached to and creating a parent dummy with that node name in your own gltf should be enough to have the decals follow the animations.
Is this something you tried already and it didn’t work?
This is the issue. For the livery model to merge to the node in the attachment, it needs to know what attachment to merge to, and afaik, this is what the tags are doing. However, the stock FA18 has no default tags since it has no attachment.cfg’s.
For example, the main flaps are part of the “function_exterior” folder. If I make a livery model that adds a decal to that flap, and it is parented to the same parent node as the flap so it get the animation. I would need to put it into a model.[tag] so it can be merged with the Node in “function_exterior”.
“function_exterior” has no attachment.cfg and therefore no tag, so I can’t put it into a model.[tag] folder to merge.
Oh ok I see, if you put your livery gltf in model.exterior, it will be loaded but since the flap attachment is not yet loaded, the parent will not be found during the merging process and the decal will not be correctly attached.
Adding the tag makes it so the livery part is loaded after the attachment that declares it, and the parent node is found.
There is a design flaw there, you are right.
I will have this reviewed.