It's usually better to try and simplify sketches and use features and feature patterns rather than sketch patterns. Also as mentioned by others, separating some of the sketches rather than do it all in one sketch.
I try to avoid sketching too many features in one sketch because it's not very stable if some of the dimensions changes. Unless you use it as a skeleton sketch...
- Unfortunately, this model violates a number of good practices :( For one, 'Rule #1: Make components'; and in this case, the model is an assembly, so components are especially pertinent. - It gets the job done, which many users are satisfied w/, BUT things are not as easily manageable/discoverable/editable/etc. - I know you wanted to keep things short, but there are many aspects of the model yet to constructively critique. - Anyhow, you have made some good notes/comments, so viewers will find benefit. - Thx for your continued efforts...
![XO (Only If You Say Yes) - ENHYPEN エンハイプン 엔하이픈 [Music Bank] | KBS WORLD TV 240712](http://i.ytimg.com/vi/wBT1bKKwPTo/mqdefault.jpg)
It's usually better to try and simplify sketches and use features and feature patterns rather than sketch patterns.
Also as mentioned by others, separating some of the sketches rather than do it all in one sketch.
Thank you
cool stuff
I try to avoid sketching too many features in one sketch because it's not very stable if some of the dimensions changes. Unless you use it as a skeleton sketch...
Can you please tell the model name
- Unfortunately, this model violates a number of good practices :( For one, 'Rule #1: Make components'; and in this case, the model is an assembly, so components are especially pertinent.
- It gets the job done, which many users are satisfied w/, BUT things are not as easily manageable/discoverable/editable/etc.
- I know you wanted to keep things short, but there are many aspects of the model yet to constructively critique.
- Anyhow, you have made some good notes/comments, so viewers will find benefit.
- Thx for your continued efforts...