TGB 1.7.3 addToScene issue

#1 Honestly, cloneWithBehaviours still isn't performing as perfectly as it could. In TGB 1.7.2, the behaviors portion worked fine, but CWB didn't register objects properly with the simulation in regards to namespaces, so you couldn't use both behaviors and namespaces, nor could you use CWB to allow for the concept of templates.

1.7.3 fixed this error, but the tweak resulted in a warning coming from the scene manager that is a "nice to know", but not something you have to fix report--in other words, you can ignore it if you are sure it is from the cloned with behaviors objects.

There is a pref you can set to turn off those specific errors:

$pref::T2D::warnSceneOccupancy = false;

should remove the warnings

Could you be more specific as to your observed "unpredictable behaviors with objects spawned by this method"? As far as internal and external beta testing showed, objects should spawn and clone properly, with the exception of needing the pref set above to hide the warnings. If you are having reproduceable errors, would be great to get specifics!

#2 Thanks, I didn't see that, I was just about to comment the warning out of the source and recompile. My other "unpredictable behaviors" were for other unrelated reasons, I think I've figured out the issues with those.

Are there other functions that are known to give this warning consistently? I'm happy to set this preference to false, but I don't want to run into a situation where I'm missing legitimate problems that I would have otherwise been warned about.

#3 I've not found any downside personally to removing the warning via the pref while I was developing the fix to the namespace cloning issue. I debated removing the warning completely from the source, but decided to err on the side of caution and leave it in for any unpredicted but valid issues.