Version: *1.6.34 sdk 1.5.6
Frequency: Consistently*
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: if applicable
Context: What package? When editing or mounted from Community? In main menu or in flight? etc…
Similar MSFS 2020 issue: insert url here if applicable
Bug description:
I disagree with the definition of the merge_to_model description and it’s link to the alias in the simobject_attachment section.
Your description and link is confusing, and I believe it is incorrect to link it to an alias identifier.
existing:
"Here you specify the <alias> of the instance to attach the model to.
Note that if the attached_object.cfg file
...
If the attached_object.cfg belongs to a common object or an object preset,
then it must be included as the target model instance is ambiguous."
Is the merge_to_model actually linked to the alias in the sim_attachment section or is it linked to the model.cfg?
I’m confused as to what string to use. Both the model.cfg use exterior and interior and the DA62 sample aliased the Function_Interior and Function_Exterior folders with the files interior.xml and exterior.xml. The attached_objects.cfg for the attachpoints.gltf don’t link to an alias od exterior in the list of sim_attachements in the file for the ATTACH_POINT.gltf.
Too many similar strings to make a clear sense of things.
When do you use merge_model compared to sim_attachment, they both seem to do the same thing.
Repro steps:
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content