Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
demuff
in reply to: wayne.brill

Interesting...we were actually just upgraded from 2014 to 2016 yesterday and I'm now able to generate the loft for the part that I posted. I've still had it fail for a couple more intricate profiles even on 2016 but it looks like the code has gotten more robust. I would still like to find a better way to use a lot of rails if only to better control the loft shape but it sounds like there aren't a whole lot of options beyond what I've already tried.

 

I can't post my code, but I was actually able to resolve the problem. I was correct in my initial observation that the generated planes were somehow the problem. I was able to trace the error back to a the line where I define the current plane of the profile. I was using 

.ComponentDefinition.WorkPlanes.AddByPlaneAndOffset(...)

in a loop to define each plane. However, because I was editing the part in place, my Plane argument to the AddByPlaneAndOffset command was an assembly plane. Therefore I was able to modify the part freely in place in the same instance of the assembly, but as soon as I closed the assembly or saved the file elsewhere that relationship didn't transfer and I received that error.

 

I corrected this by defining the first plane with

.ComponentDefinition.WorkPlanes.AddFixed(...)

 and subsequent planes using the AddByPlaneAndOffset from the fixed plane.

 

I imagine you could duplicate this issue by doing exactly what I've described above during an in place edit.

 

Thanks for working with me on this. If there's any additional information I can provide to assist in resolution of this error let me know.