Submodels issues
ITC
Dear all,
I have encountered two issues related to the visualization and duplication of submodels in version 2020-12 of JaamSim, and I would appreciate any insights or suggestions you may have.
-
Icon orientation issue:
When I set the icon orientation of a submodel to a vertical position (Rotation: 90 0 0 deg), the icon turns completely black in the simulation view. I am attaching a screenshot to illustrate the problem. -
Text entity not duplicated with submodel:
When I associate a Text type entity to the region of a submodel (e.g., to label a specific instance), I notice that duplicating the submodel via copy-paste does not replicate the associated text entity. In the screenshot I’m sharing, you can see that the label “Secadero 1” does not appear in the duplicated submodel I started to create for replicating the layout shown in the original display.
Due to the size and complexity of the model, I am using version 2020-12, as I am unsure whether newer versions would support it without compatibility issues given the many changes introduced in recent years.
My goal is to modularize and replicate the screen layouts visible in the images by creating reusable submodels and including on it texts, input value entities and charts. Any advice or confirmation on whether these behaviors are expected or if workarounds exist would be very helpful.
Thank you in advance.
ITC
As a follow-up to my previous message, I have noticed a few additional behaviours that might be relevant.
In particular, I’ve observed that if I have already created a text or any other entity and later try to assign it to a newly created submodel by setting its Region field to something like SubModel1.Region, the entity does appear to move correctly relative to the submodel’s region. However, when I try to perform actions such as copy-paste or use the undo shortcut (Ctrl + Z), the entity does not seem to persist. For instance, after undoing a deletion, the entity does not reappear. It seems that the object is not fully recognised as part of the submodel structure.
This raises the question of whether submodels are intended to be built incrementally, with all associated entities created from within the submodel’s scope from the start. If so, it would imply that simply reassigning the Region of existing entities is not enough to integrate them properly into a submodel for duplication or history tracking purposes.
I would appreciate any clarification on whether there is a recommended procedure for integrating existing objects into a submodel after its creation.
Thank you.
Harry King
- Icon orientation. This is a genuine bug in the graphics logic. It also affects an imported image. I'll look into fixing it.
- Text entity not duplicated with submodel. This problem is the result of using such an old version of JaamSim (2020-12). SubModels have improved a lot since then. I can help you to update your model to the latest release.
- Adding objects to a submodel. An object must be assigned to a submodel when it is first created, i.e. by drag-and-dropping it to the submodel's region. Changing the Region input affects its graphics but does not add it to or remove it from the submodel. If necessary, you can re-assign objects to a submodel by editing the configuration file.
ITC
Hi Harry,
Thanks for your reply and clarifications.
I’ve managed to run the model with version 2024-09 after making a few minor adjustments to some probabilistic inputs, which now require values strictly greater than zero. The transition was relatively smooth.
In this jaamsim version the model shows visualization issues related to the flow of SimEntities, but I understand — as you explained — that these are linked to changes in the way entity positioning is handled within EntityConveyors. I assume this will be addressed in upcoming releases.
Given these improvements, do you think version 2024-09 now offers a better framework for working with submodels? I would like to proceed with building a set of screens composed of submodels and need to ensure that this version supports a consistent workflow, particularly in terms of duplicating and reusing submodel instances.
Thanks again for your support.