UP_TO_NEXT with scope?

EvanReese

Is there a way to limit the scope of an UP_TO_NEXT endBound in a custom feature? Otherwise it can sometimes behave unintuitively. For example, if the feature is creating multiple extruded bodies using a loop, and the second body runs into the first one.

MBartlett21

I don't think there is any 'official' way to do it. You should be able to approximate it with another way, though, like creating a new context, deriving everything you need, extruding in that context, then deriving the extrude back.

EvanReese

Thanks! I haven't messed with multiple contexts at all yet, but this sounds like it would do it. Would this incur the same performance costs that the native derive feature does?

MBartlett21

I expect it would (twice!)