Order of objects in collections
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi,
I'm having an issue with a model that uses a discrete user parameter. It is a bass guitar that can be either 4, 5, or 6 strings, so there's no way to continuously change the parameter.
The issue is that some features seem to change drastically when I change this parameter. For example, if I delete faces, which faces get deleted can change based on the parameter. Or paths used for lofts or patches get messed up.
It looks like the features are likely referencing objects by index, and where those objects are in the collection is changing for some reason. I know that position isn't guaranteed. but I'm not sure how to work around this.
All that changes is some dimensions. It's not like I add new bodies or components when I change the number of strings.
I can kind of work around this by using configurations, but it's kind of a pain. Once I branch at a feature everything downstream is affected.
Any pro tips?
Thanks in advance,
Doug Roberts