Suggestion for Improvement: Handling of Removed 3D Models in .cfg File

[GABRIEL HENRIQUE DUARTE DE SOUZA]

Dear JaamSim Team,
I hope you are doing well.

My name is Gabriel Henrique Duarte de Souza, and I am a Production Engineering student at the Federal University of Ouro Preto (Brazil), under the supervision of Professor  Cristiano Luis Turbino de França e Silva

I would like to suggest a potential improvement regarding the handling of 3D models within JaamSim.
Currently, when a 3D model is added and later removed (for any reason), the reference to this model remains in the associated .cfg file. This behavior can lead to errors during simulation runs, especially in large projects that involve many external 3D models.
For example, in complex simulations with multiple imported models, if one or more models are removed—whether manually or by the software—the corresponding entries persist in the .cfg file. As a result, this can cause issues or failures when attempting to execute the simulation.
As a suggestion, it would be very helpful if JaamSim could automatically clean up or update the .cfg file by removing references to deleted 3D models. This would improve robustness and reduce the need for manual file editing, particularly in large-scale scenarios.
Thank you for your attention and for the continued development of JaamSim.
Best regards,
Gabriel Duarte de Souza 
Este e-mail foi enviado por um ALUNO da Universidade Federal de Ouro Preto e não reflete a posição da Instituição.

[Harry King]

Hi Gabriel,

Thank you for the suggestion. The problem is that two separate objects are created when an image or 3d file is imported: the DispayModel (either an ImageModel or a ColladaModel) containing the graphics information, and the DisplayEntity that references the new DisplayModel. This separation is not obvious to most users, so when they delete the DisplayEntity, they do not realise that the DisplayModel needs to be deleted as well.

In the next release, when a DisplayEntity is deleted, the user will be have the option of deleting the DisplayModel as well, if it is not used by some other DisplayEntity and is not one of the pre-defined DisplayModels.

Harry