My guess is that using a for-collect loop to build a maxscript array first, and then converting that into a .NET array implicitly by passing it to a ….

Maybe you have a reason to do it all in maxscript, but I can’t help but wonder why you wouldn’t do your .NET development in C# with Visual Studio?

How about a when construct with the “topology” attribute? From the maxscript help: topology Signaled when the topology of an object changes in the …

Ok, I found a solution. It works, but no further comments… :surprised testCA = attributes testCA attribID:#(0x42a4cdb9, 0x13c71b46) ( ) ( s = sphe…

denisT: testCA = attributes testCA attribID:#(0x42a4cdb9, 0x13c71b46) ( ) ( s = sphere() custattributes.add s testCA instances = custAttribute…

Hm yes that works, curiously enough. Thanks for that. Although the scene def does appear to stay in memory while the scene is open, but that’s not a b…

Yes indeed, and the garbage collector doesn’t seem to be able to deal with it. I’m wondering whether that’s my fault or Autodesk’s though…

Looking at the “test” script here, that scene only contains one new layer, one object…

Are you sure your solution works for all cases? I recall that the scene you merge into does not have to contain any CA to make the crash occur. So if …

I’ve submitted an “official” defect report to Autodesk about this btw.

Thank you for your reply Patrick. I got your email too, but I’ll just reply here so others here can read it too if that’s ok. So, let me start by say…

I’ve also tried to get the most general case where the error can be reproduced. Like you Denis, it was with an empty CA definition on a layer. And it …

Hmm I wonder if that’s the sort of behavior I would expect. How does it work when merging/xrefing a scene? Does that bring the nested layers into it?

So how does that work when merging a single object then though?