If I use a proper surface as an input and get this error as output, is this a node limitation? Bug? Or workflow limitation that I can’t input a “flat” area?
Thanks in advance for your guidance…
Hi @ddrennen2QDK2,
This node has not changed for many versions. Perhaps there is something strange with the surface itself, or the geometry scaling settings? Feel free to send the DWG if you want me to take a look.
Hi gang,
I’ve met this exact same issue in C3D 2025 and 2026, where the TinSurface.Triangles reacts EXACTLY like that when the outer boundary passes through “certain coordinates”. See the attached files, where in ProposedDesign II.dwg the Parking surface boundary passes through point 241 and the node fails. In ProposedDesign II_V2.dwg, I’ve move the vertex somewhere else and now it works. In both cases, the surface is fine and doesn’t prompt any triangulation errors in C3D.
Maybe there is an unforseen exception that Autodesk is not aware of?
ProposedDesign II.dwg (1.1 MB)
ProposedDesign II_V2.dwg (1.3 MB)