Version: 1.38.2.0
Bug description: I use this ASOBO_uniqueID option so I am aware there is a conflict. And it warns you. Then I use the resolve tool to fix it. But now when I want to get a confirmation, objects are all getting added numbers to the part names and this breaks any of my visibility and emissive parts.
If intended, this is not a good idea to try to resolve the issue as we need our specific names for logic. Please confirm you also see this is now broken.
Or could I be wrong as the numbers are added after the quoted name. So does this allow the sim to continue to read the correct name?
For those watching this thread I seem to narrow the bug down to containers. Only parts in containers are having issues.
- If I have parts in a container and use the ASOBO_uniqueID, options It automatically adds numbers to the ID name.
- If I have parts in a container and I do NOT use the ASOBO_uniqueID, then when I build all in the sim it throws this error below.
UPDATE: Original bug report is wrong!
We found that having parts in a container will add numbers to the ID name from the Babylon exporter, but this is ok and does not hurt anything. Our issue is that we now have visibility code for child parts that are linked to a parent part that also has visibility logic. And we found if you use visibility for both child and parent parts there are some rules you need to consider. I will list them below.
Keep both in scope:
- Both Visibility codes for child and parent parts needs to be in the same XML or the same template if you use model behaviors.
- The parent visibility code must be listed first in order in the same scope.
- Components are not a factor here and they can also have subcomponents too.
