Best Of

John, thanks so much for the comments! Glad it can unlock some workflows for you.

Regarding the limitation you mention, this is intentional in order to reduce the clutter, and reduce the derive to only need a single part. More specifically, the idea behind this all is to create a single "skeleton" part that has all the references you need for a particular downstream activity, a specific function, or that a certain collaborator would need. A classic use case is where different functional areas of the model are going to be addressed by different folks, in different documents. Think of chassis design, versus powertrain design, versus interior, etc. They will share certain common references, but also have some of their own. In other words, feel free to make multiple Publish geometries with the curves separated into their own groups… These can be named appropriately (like in the custom feature's test part studio) and thus there will be multiple Composite parts in available for downstream use as necessary.

As for sketches, I deliberately used the reference to a whole sketch feature. If you want to peel off a subset of entities from a sketch, or indeed choose a surface edge (like the edge from a face blend) then you could first create a Composite curve of the individual edge(s), then select these curves for the Publish geometry. They are always associated to the original geometry, and will update properly.

Not every predicate is supported as an input type for a featurescript. Predicates in general are special functions with some unique rules that are generally used to validate data types. I've run into a similar situation with things like area or volume inputs.

For the pressure, you can take in a unitless real number and assign the units in the feature body. Just add the units to the label of the input so the user knows.

As far as I know, only the density is provided from the getProperty call. So yeah, you'll have to make your own lookup table.

Haven't played with it yet but that looks really useful (a couple weeks too late to use on my current project!)

One thing I don't see and I think could be handy is the ability to include variables…

I know you can use variable studios but if you are going to use configurations (which would work for a "publish", that's not an option… You could also use this to derive in measured variables or "strings" to use in downstream features.

1. you can’t include sketches in a regular composite part, or mate connectors.
2. The feature creates a single composite part of all the references and automates a couple of other handy steps for the workflow

Basically #2 adds convenience and encourages a good workflow. #1 is not doable in any other way. Unless you write your own custom feature.

Changelog for release 1.201

⭐ Added per-segment reset. Select a segment to edit first, then click the reset button.
⭐ Add route point UX has been improved for clarity and consistency.
⭐ Addition and removal of clips keeps route edits intact.
⭐ New "nudge" option provides mechanism for moving edit points between route segments.

Note: this update does not guarantee backwards compatibility - please see video for details.