More feedback. At the suggestion of @SimbolFSReborn I checked the flight_model.cfg file. The SimObject Editor doesn’t write the line with```material_guid = E48F59B9-94E0-4CA2-B261-8E5FFFF3CB03```, even though it is displayed in the editor window. See bottom of image:
“When applying the cloth simulation”
I’m not sure to understand. Are you talking about the modeling process ?
As it’s written in the documentation “This is a special physics object that is spawned by the simulation and does not need to be modeled”
If it’s a material issue, I checked the DA62 and the material guid is correctly referenced in the flight_model.cfg (function_exterior) file and its working as expected when we set it to a different material guid.
You can also use a different guid that correspond to a material your created in a modelLib.
@Boris the issue is that the Aircraft Editor doesn’t write the “Material GUID” line into flight_model.cfg. It is displayed in the editor, but not written in the file, so I had to edit that in manually using N++.
I just tested this in the DA62 sample on SU4, and it works as expected. When the file is saved in the SOE, flight_model.cfg is updated with the updated value.
I’m not sure why it’s not behaving the same way on your side. Have you tried using the DA62 SDK sample to compare the behavior?
The problem happens when you creating a new fresh configuration, not editing one..
For example, there are no flags on a new aircraft, you use the AE editor to create a new flag.. the material guid is present in the AE, but is not saved to the physical file.. if you edit it via an independent text editor (such as notepad or notepad++), add the GUID then it all works, further changes from the AE will continue to save the file..