Custom Feature: Multi Copy
I've got to think this has been done already, but I made one for me.
- Select one or more bodies
- Select from location (vertex or MC)
- Select to locations (vertices or MCs)
- Bodies are copied from FROM to TO ( First copy can be set as a move instead).
- Orientation:
- Auto
- If vertex-vertex, orientation is retained.
- If MC to MC, orientation matches new MC.
- Match First
- All copes retain orientation of first MC
- Match Previous
- Copies retain orientation of the most recently selected MC
- Auto
Comments
-
Nice. I could see having a per-instance scale option (both uniform and non-uniform, centered on their individual locations), although I'm not sure what the right UX would be for that. Perhaps a bunch of manipulators with numeric fields in the dialog to dial in the values? It could also be nice to add Add/Subtract/Intersect options which would apply to all the new bodies and a Merge scope selection.
Simon Gatrall | Product Development, Engineering, Design, Onshape | Ex- IDEO, PCH, Unagi, Carbon | LinkedIn
0 -
This look very similar to the "Transform Pattern" FS no?
0 -
I didn't actually look, @eric_pesty, things are so easy to write now, I just whipped this up mid-model.
0 -
@eric_pesty the thing that Transform Pattern doesn't do is allow alignment with target Mate Connectors. That would be a very welcome addition - and one of the things I would add too.
0 -
I think it might be the other way around: transform pattern doesn't allow "not aligning" with target MCs, so this has the option to work more like the point pattern FS where it keeps the original instance orientation.
0 -
What?? I must be confused. When I reach for the Transform Pattern (maybe it's the Point Pattern) I'm usually frustrated by the fact that the original orientation is maintained - when what I WANT is for each new instance to follow each individual target MC.
I'll check my work and see what the heck I'm talking about!
0 -
there are so many duplicates now, impossible to find features.
too bad we dont have a feature store, and a capable ai that has access to the forums, featurescript, api, and the feature store to search for existing features lightning fast. 😴
@onshape #wink #nudge
â–šâ–žâ–šâ–žâ–šâ–žâ–šâ–žâ–š2 -
@MichaelPascoe I'm not saying that crawling through the forums and all publicly posted featurescripts and building a searchable tagged index of all of that data is on my bucket list of things to do with Onshape cause I think that's probably a good way to have someone sternly read a EULA or TOS to me and that sounds like it could be a boring time, but I am saying that the more time goes on without the feature store the more I hear the call of the void.
2 -
Here's an example:
Here's the doc from where you can link to the "real" transform pattern.
1 -
Yeah, with vibe coding become so powerful, we are going to see an explosion in the number of Featurescript with tons of functionality overlap and it's going to be even harder to find the "good"/"best" ones, leading to even more custom options etc…I do wonder how this will affect the software landscape in general, we are going to see many more pieces of software with very similar but different functionality out there, how will we figure out which PDF editor to download when there's a thousand different options out there!
0






