GDL warning is too cryptic

[Patrick M]

I don't even know what this is supposed to mean... maybe the object was saved too far from 0,0,0? it it is a morph based object; but that shouldnt be the issue

 

[Lingwisyer]

The actual error line in the message is missing XD

[Patrick M]

the object was just saved from a modeled morph... so AC writing scripts with baked in errors?

[Barry Kelly]

Was the morph checked for solidity before saving as an object?

I have found solid morphs are better as it can help to eliminate free floating or overlapping edges and surfaces.

Also if you can, simplify the morph as much as possible.

Seems strange the first line of the error message is missing.

Does simply re-saving the object fro the morph create the same error?

Can you try in a different version of Archicad?

Trying to figure out the error in these 'primitive' codes can be almost impossible.

Split the morph into pieces and save each piece as an object.

This might help to narrow down where the problem is in the morph.

And if all the pieces work OK, union them back together and try again.

Barry.