Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Best Of
Re: crazy Attractor Pattern feature coming soon, had to share
This is excellent, Evan! I'm evaluating Onshape for my needs a second time, and am finding it almost perfect - except for my need for this kind of attractor-driven patterning. I'd love to move away from the Rhino+Grasshopper combo for these kinds of projects:



Is this something your FeatureScript could do?
Re: crazy Attractor Pattern feature coming soon, had to share
@TimRice
Here's a better example of a more realistic use-case
. I expect to be ready to release it tomorrow sometime btw.

Here's a better example of a more realistic use-case


11
Re: naming
@rune_thorsen229 - I do rename my sketches and features. Also, its not that I like insignificant names, but I fear that "smart" names would be incorrect, causing more confusion than a name that's neutral.
Perhaps I'm not understanding your suggestion properly, but this is how I imagine that it would work based on your description:
Lets say I have a sketch named "Gripper". From that, I extrude two different gripper paddles and hinge pin. In a separate sketch named "Ribs", I design a couple of ribs that would be used to stiffen the gripper paddles, and extrude the ribs so that they merge with the paddles. Now, following your suggestion, I have a hinge pin named "Gripper 3" and two gripper paddles named "Ribs 1" and "Ribs 2". If I understand your suggestion correctly, the smart names are actually misleading.
I'm certainly not against improvements, but I think a simplistic "feature gets the referenced sketch name" doesn't add much value because the relationship between features and sketches is not 1-to-1. An extrude could reference multiple sketches, and multiple extrude features could reference a single sketch. So, any naming logic would have to make so many assumptions that it could easily create names that are confusing.
Also, development resources being limited... I would prefer other improvements be prioritized over this one.
Perhaps I'm not understanding your suggestion properly, but this is how I imagine that it would work based on your description:
Lets say I have a sketch named "Gripper". From that, I extrude two different gripper paddles and hinge pin. In a separate sketch named "Ribs", I design a couple of ribs that would be used to stiffen the gripper paddles, and extrude the ribs so that they merge with the paddles. Now, following your suggestion, I have a hinge pin named "Gripper 3" and two gripper paddles named "Ribs 1" and "Ribs 2". If I understand your suggestion correctly, the smart names are actually misleading.
I'm certainly not against improvements, but I think a simplistic "feature gets the referenced sketch name" doesn't add much value because the relationship between features and sketches is not 1-to-1. An extrude could reference multiple sketches, and multiple extrude features could reference a single sketch. So, any naming logic would have to make so many assumptions that it could easily create names that are confusing.
Also, development resources being limited... I would prefer other improvements be prioritized over this one.
Re: Improvements to Onshape - August 25th 2020
I have missed re-releasing in all the PLMs I've worked with.. so glad to be finally able correct small mistakes. Because no matter how many eyes you have, a mistake will be found at the moment after one hits "release"... 


7