Sketch to Model : Detailing your model in Rhinoceros

[@eobet]

Wow, finally an honest tutorial! All of these fillet and blend problems convinced me that Rhino is not the magic bullet I thought it was. :) I think the most interesting thing, though, would have been to see how these problems are solved, because that's exactly what 99% of tutorials never show, and it's where I always get stumped and go looking for better software...

[@federicopallitto6477]

@@naengineerwhich software?? how do you do it, you export rhino and then fillet with the other?

[@jimdeasy6720]

Federico Pallitto if you export your rhino files as a stp file into Solidworks, you can do fillets in there and they are much better

[@chuckintexas]

@@jimdeasy6720 _ ABSOLUTELY _APPROPRIATE_ SOLUTION - for those who laid out the THOUSANDS of $$ for a LICENSED Solid-Works seat ! Good call !

[@chuckintexas]

@eobetdisajn - No, there's ALLOT this presenter DOES NOT seem to know about the topic he's presenting on. To START with, later versions of RHINO have made "improvements" in filleting, but - yes - _THAT_ doesn't help here. _KNOWING your TOOL_ is - and always WILL be - the _KEY_ . Here's a "BETTER WAY" - and ONE of the _MANY_ reasons that even tho I've had access to MANY supposedly "Higher-End" or "BETTER" tools, RHINO _remains_ my first go-to (BESIDES the fact that it imports & exports STP/STEP and DWG/ACIS models nearly FLAWLESSLY ... ) - On showing the Fillet transition of the first "Spoke" to the in-board face of the revolved HUB - FAR better than "Filleting" at random or splitting the inner face with a random intersect-derived curve and HOPING you made it "bigger-enough" to "work" (NOTE the isocurves of the resulting Blend - and how along the "spine" of the blend they "come together" and actually INTERFERE, even tho they DO give a "Solution" to the solve? Look CLOSELY- the spine actually dips IN ever so slightly, glossed over by the presenter, as he immediately zoomed out ... ) . Try something a little more straight-forward, instead. Decide how big a "transition" you _MIGHT_ want. .25" ? .380 ? .5 ? Try them ALL and DECIDE ! - Here's HOW : 1. Do the "Intersect" between the Spoke and the Rim "complex" surfaces to get your initial curve. 2. Run the PIPE command on the INITIAL Intersect-generated curve. Play with "Radiuses" as mentioned above. Use Radius, just to keep things straight in your mind, as THAT approximates the amount of "Radius you'r ending up with in your BLEND . 3. _I_ like Trimming away the 2 surfaces, to the inside of the new Pipe (as LONG as it CLOSED successfully) , but YOU might decide YOU like Boolean-Subtracting the pipe from the 2 after having Boolean-UNIONED them, THEN subtracting the PIPE, then Extractsrf the surface you'd created and Blendsrf 'ing the result, but I _THINK_ you can see why _I_ prefer "Trimming" ... instead... . YOUR choice, however. 4. HIDE the "Pipe you decide you PREFERRED - for FUTURE reference ... and run Blendsrf on the 2 exposed nearby "EDGES" Like the result ? NO - CLOSE but you'd LIKE to refine it a bit more ? Try a larger "Pipe Radius, and/or play with the BlendSrf Sliders, or BOTH. Experiment: Try a SMALLER radius "Pipe" on the SAME curve for ONE surface, and THEN a LARGER Radius Pipe for the OTHER surface !! Cool _STUFF_ !! TOP notch results- the FIRST TIME - results worth _THEN_ experimenting with and REFINING _INSTEAD_ of repeatedly "OOPS"ing , starting over, and quickly zooming away to disguise otherwise marginal results. _BONUS_ Tip- In shaded Mode, turn off Edge-Curve Display AND Isocurves in your Display Control, and play with "Display Colors" to mimic the BASE colors in your Render Materials. You'll find this _impressively_ speeds up working times, as you can get away with FAR less system resource "Overhead" while you're WORKing (less powerful platforms anyone?) _ESPECIALLY_ if your Model is becoming excessively complex, and if your shadows are turned on in Rendered Mode. You MIGHT even like the RESULT (!) _and your components keep the general operating color as in your "Rendered" mode, all the way THRU Shaded AND _GHOSTED_ , and EVEN - _if_ you have your Surface Edge Color setting set to "Object Color" (By-Layer too, btw-) all the way to Wire Frame Mode , making Wire Frame ENORMOUSLY useful where you _MIGHT_ have avoided using it, previously !! _AND_ you _MIGHT_ find in MANY applications, the IMAGES generated in "SHADED-Mode" are very useful in communicating with your Client ! I've even had clients tell me they wanted _THAT_ image for their Brochure or Instruction manual - _instead of the "Rendered-Mode image"_ or the image from from some Hi-end "Photo"-Renderer , _AND_ with _ZERO RENDER-WAIT TIME !!!_ THEN for you BONGO Users, the Render-Per-Frame times in Shaded Mode are SPECTACULARLY _FAST_!! I can deliver a USE-ABLE result - SOMETIMES _PUBLISHABLE_ - to MY client _TOMORROW MORNING_ that'll take _YOU_ 2-Weeks to deliver. Uuuhhhmmmm. _YES_ . I _CAN_ . I've delivered some MASSIVELY _PROFITABLE_ Animations this way. _SERIOUSLY. _ _THE.VERY.NEXT.MORNING_ . Ok, ALL the BEST to ALL here from Texas- C.

[@colinturner2336]

Why is it when these tutorials are uploaded the file for the model can't be included as well?, it would help a great deal if people who actually watch these tutorials got the file which would allow them to try and learn at their own pace. By being able to watch the video whilst trying it for themselves, they can stop/start to suit their pace, having the basic curves of the model to start with is such a big plus, is it to much to ask?, if Rhino users can get the curves drawn like you are using I'm pretty sure they don't need to be following these tutorials.

[@johnbearross]

Great video. Best, JBR

[@aanchalbudhranii]

thanks so much :)

[@chuckintexas]

@eobetdisajn - No, there's ALLOT this presenter DOES NOT seem to know about the topic he's presenting on. To START with, later versions of RHINO have made "improvements" in filleting, but - yes - _THAT_ doesn't help here. _KNOWING your TOOL_ is - and always WILL be - the _KEY_ . Here's a "BETTER WAY" - and ONE of the _MANY_ reasons that even tho I've had access to MANY supposedly "Higher-End" or "BETTER" tools, RHINO _remains_ my first go-to (BESIDES the fact that it imports & exports STP/STEP and DWG/ACIS models nearly FLAWLESSLY ... ) - On showing the Fillet transition of the first "Spoke" to the in-board face of the revolved HUB - FAR better than "Filleting" at random or splitting the inner face with a random intersect-derived curve and HOPING you made it "bigger-enough" to "work" (NOTE the isocurves of the resulting Blend - and how along the "spine" of the blend they "come together" and actually INTERFERE, even tho they DO give a "Solution" to the solve? Look CLOSELY- the spine actually dips IN ever so slightly, glossed over by the presenter, as he immediately zoomed out ... ) . Try something a little more straight-forward, instead. Decide how big a "transition" you _MIGHT_ want. .25" ? .380 ? .5 ? Try them ALL and DECIDE ! - Here's HOW : 1. Do the "Intersect" between the Spoke and the Rim "complex" surfaces to get your initial curve. 2. Run the PIPE command on the INITIAL Intersect-generated curve. Play with "Radiuses" as mentioned above. Use Radius, just to keep things straight in your mind, as THAT approximates the amount of "Radius you'r ending up with in your BLEND . 3. _I_ like Trimming away the 2 surfaces, to the inside of the new Pipe (as LONG as it CLOSED successfully) , but YOU might decide YOU like Boolean-Subtracting the pipe from the 2 after having Boolean-UNIONED them, THEN subtracting the PIPE, then Extractsrf the surface you'd created and Blendsrf 'ing the result, but I _THINK_ you can see why _I_ prefer "Trimming" ... instead... . YOUR choice, however. 4. HIDE the "Pipe you decide you PREFERRED - for FUTURE reference ... and run Blendsrf on the 2 exposed nearby "EDGES" Like the result ? NO - CLOSE but you'd LIKE to refine it a bit more ? Try a larger "Pipe Radius, and/or play with the BlendSrf Sliders, or BOTH. Experiment: Try a SMALLER radius "Pipe" on the SAME curve for ONE surface, and THEN a LARGER Radius Pipe for the OTHER surface !! Cool _STUFF_ !! TOP notch results- the FIRST TIME - results worth _THEN_ experimenting with and REFINING _INSTEAD_ of repeatedly "OOPS"ing , starting over, and quickly zooming away to disguise otherwise marginal results. _BONUS_ Tip- In shaded Mode, turn off Edge-Curve Display AND Isocurves in your Display Control, and play with "Display Colors" to mimic the BASE colors in your Render Materials. You'll find this _impressively_ speeds up working times, as you can get away with FAR less system resource "Overhead" while you're WORKing (less powerful platforms anyone?) _ESPECIALLY_ if your Model is becoming excessively complex, and if your shadows are turned on in Rendered Mode. You MIGHT even like the RESULT (!) _and your components keep the general operating color as in your "Rendered" mode, all the way THRU Shaded AND _GHOSTED_ , and EVEN - _if_ you have your Surface Edge Color setting set to "Object Color" (By-Layer too, btw-) all the way to Wire Frame Mode , making Wire Frame ENORMOUSLY useful where you _MIGHT_ have avoided using it, previously !! _AND_ you _MIGHT_ find in MANY applications, the IMAGES generated in "SHADED-Mode" are very useful in communicating with your Client ! I've even had clients tell me they wanted _THAT_ image for their Brochure or Instruction manual - _instead of the "Rendered-Mode image"_ or the image from from some Hi-end "Photo"-Renderer , _AND_ with _ZERO RENDER-WAIT TIME !!!_ THEN for you BONGO Users, the Render-Per-Frame times in Shaded Mode are SPECTACULARLY _FAST_!! I can deliver a USE-ABLE result - SOMETIMES _PUBLISHABLE_ - to MY client _TOMORROW MORNING_ that'll take _YOU_ 2-Weeks to deliver. Uuuhhhmmmm. _YES_ . I _CAN_ . I've delivered some MASSIVELY _PROFITABLE_ Animations this way. _SERIOUSLY. _ _THE.VERY.NEXT.MORNING_ . Ok, ALL the BEST to ALL here from Texas- C.

[@juanvla1]

I saw what you mean and come to the comment to see if someone talked about.

[@chuckintexas]

On showing the Fillet transition of the first "Spoke" to the in-board face of the revolved HUB - FAR better than splitting the inner face with a random intersect-derived curve and HOPING you made it "bigger-enough" to "work" (NOTE the isocurves of the resulting Blend - and how along the "spine" of the blend they "come together" and actually INTERFERE, even tho they DO give a "Solution" to the solve? Look CLOSELY- the spine actually dips IN ever so slightly, glossed over by the presenter, as he immediately zoomed out ... ) . Try something a little more straight-forward, instead. Decide how big a "transition" you _MIGHT_ want. .25" ? .380 ? .5 ? Try them ALL and DECIDE ! - Here's HOW : 1. Do the "Intersect" between the Spoke and the Rim "complex" surfaces to get your initial curve. 2. Run the PIPE command on the INITIAL Intersect-generated curve. Play with "Radiuses" as mentioned above. Use Radius, just to keep things straight in your mind, as THAT approximates the amount of "Radius you'r ending up with in your BLEND . 3. _I_ like Trimming away the 2 surfaces, to the inside of the new Pipe (as LONG as it CLOSED successfully) , but YOU might decide YOU like Boolean-Subtracting the pipe from the 2 after having Boolean-UNIONED them, THEN subtracting the PIPE, then Extractsrf the surface you'd created and Blendsrf 'ing the result, but I _THINK_ you can see why _I_ prefer "Trimming" ... instead... . YOUR choice, however. 4. HIDE the "Pipe you decide you PREFERRED - for FUTURE reference ... and run Blendsrf on the 2 exposed nearby "EDGES" Like the result ? NO - CLOSE but you'd LIKE to refine it a bit more ? Try a larger "Pipe Radius, and/or play with the BlendSrf Sliders, or BOTH. Experiment: Try a SMALLER radius "Pipe" on the SAME curve for ONE surface, and THEN a LARGER Radius Pipe for the OTHER surface !! Cool _STUFF_ !! TOP notch results- the FIRST TIME - results worth _THEN_ experimenting with and REFINING _INSTEAD_ of repeatedly "OOPS"ing , starting over, and quickly zooming away to disguise otherwise marginal results. _BONUS_ Tip- In shaded Mode, turn off Edge-Curve Display AND Isocurves in your Display Control, and play with "Display Colors" to mimic the BASE colors in your Render Materials. You'll find this _impressively_ speeds up working times, as you can get away with FAR less system resource "Overhead" while you're WORKing (less powerful platforms anyone?) _ESPECIALLY_ if your Model is becoming excessively complex, and if your shadows are turned on in Rendered Mode. You MIGHT even like the RESULT (!) _and your components keep the general operating color as in your "Rendered" mode, all the way THRU Shaded AND _GHOSTED_ , and EVEN - _if_ you have your Surface Edge Color setting set to "Object Color" (By-Layer too, btw-) all the way to Wire Frame Mode , making Wire Frame ENORMOUSLY useful where you _MIGHT_ have avoided using it, previously !! _AND_ you _MIGHT_ find in MANY applications, the IMAGES generated in "SHADED-Mode" are very useful in communicating with your Client ! I've even had clients tell me they wanted _THAT_ image for their Brochure or Instruction manual - _instead of the "Rendered-Mode image"_ or the image from from some Hi-end "Photo"-Renderer , _AND_ with _ZERO RENDER-WAIT TIME !!!_ THEN for you BONGO Users, the Render-Per-Frame times in Shaded Mode are SPECTACULARLY _FAST_!! I can deliver a USE-ABLE result - SOMETIMES _PUBLISHABLE_ - to MY client _TOMORROW MORNING_ that'll take _YOU_ 2-Weeks to deliver. Uuuhhhmmmm. _YES_ . I _CAN_ . I've delivered some MASSIVELY _PROFITABLE_ Animations this way. _SERIOUSLY. _ _THE.VERY.NEXT.MORNING_ . Ok, ALL the BEST to ALL here from Texas- C..

[@xilefx]

good tutorial. but when you're recording, you can't just continue working like you always do. It's just too much happening and to much rotating and stuff

[@chuckintexas]

ABSOLUTELY _CORRECT . Showing the WRONG choice reinforces that step along with whatever ELSE is being "taught" . Pre-scripting your steps AHEAD of time is CRUCIAL, as there is _NO merit_ in showing a student trying to gain a new skill the WRONG thing to do and throwing in lots of apologetic "OOPS"es . Script out your steps, VERIFY your results AHEAD of time, and KNOW what YOU expect so that as part of your running "Narration" you can -along with describing what you're doing - tell the LEARNER what to EXPECT (what they're ABOUT to see) from the step you're running at the moment . THIS reinforces in the mind of the LEARNER 1. The RIGHT steps and 2. the ANTICIPATED RESULTS. A third result - JUST as important- is that the TEACHER (preparing their presentation AHEAD of time) spots a "better" way to complete the step or even a BETTER STEP TO TAKE _INSTEAD_ , thus improving the quality of the PRODUCT THE _DELIVER_ . @ xilefx- EXCELLENT CATCH !! - C.

[@thegemgarden2757]

Only 4:05 minutes in and being told by the presenter what they are not going show or do, hmmmm! Maybe the tone of how the presenter states it has me a little turned off from continuing, but what the he##, it might get better.

[@chuckintexas]

@ xilefx- _EXCELLENT CATCH !!_ ABSOLUTELY _CORRECT ! Showing the WRONG choice reinforces that step along with whatever ELSE is being "taught" . Pre-scripting your steps AHEAD of time is CRUCIAL, as there is _NO merit_ in showing a student trying to gain a new skill the WRONG thing to do and throwing in lots of apologetic "OOPS"es . Script out your steps, VERIFY your results AHEAD of time, and KNOW what YOU expect so that as part of your running "Narration" you can -along with describing what you're doing - tell the LEARNER what to EXPECT (what they're ABOUT to see) from the step you're running at the moment . THIS reinforces in the mind of the LEARNER 1. The RIGHT steps and 2. the ANTICIPATED RESULTS. A third result - JUST as important- is that the TEACHER (preparing their presentation AHEAD of time) spots a "better" way to complete the step or even a BETTER STEP TO TAKE _INSTEAD_ , thus improving the quality of the PRODUCT THE _DELIVER_ . @ xilefx- EXCELLENT CATCH !! - C.