Thank you tremendously for your tutorials. I am an Ind Design student, and right now my sketching is terrible. Do you have any equally as good sketch tutorials? Or recommend any other recourses?
i dont wana tell u ur software but if u used the delete faces command, u coulda selected all the faces to delete, instead of selecting everything including the points, and having to select the fasces individually like u did.,. it woulda been easier and more professional! hah
I laughed out loud when in the middle of your brilliant demo, the Boolean Union failed! The fact that you have reached the seventh version of Rhino and you are still unable to reliably union two objects together is disgraceful! Arguing about precision and shared surfaces is bullshit - it should "just work", even if you have to detect the failure internally (by the fact that you have not managed to create a single object) and then judder things around until it does. Please fix the bread-and-butter operations before adding more bells and whistles. PLEASE!
@@Rhinoceros3d I should have explained more of my use case and why the failed booleans are irritating: I primarily use Rhino through the Grasshopper interface, since I really love the parametric approach. I am generally a very happy customer! Grasshopper allows me to think more slowly and to correct mistakes made earlier in the process. It allows a simple module to be made complicated later. I mostly make mathematical surfaces, for CNC routing and 3-D printing. When a boolean operation fails in Grasshopper, the resulting failure is awkward, since it affects the downstream operations. There is no indication that the failure has happened, other than that the resulting unioned output contains too many objects. The failure happens sporadically, depending on exact sizes/alignments/interrelationships, which can sometimes be fixed by very minor tweaks to sliders upstream. Sometimes I am reduced to adding a 'move' operation to jiggle things around explicitly, so that volumes really inter-penetrate and surfaces are not shared. But real-life objects DO share surfaces. I am a software engineer; I understand the limits of representing numbers in a computer and the problems of representing volumes and their intersections/unions. I made my comment at three in the morning, when I should probably have gone to bed, but I stand by the basic message: in mathematics, unioning and intersecting volumes is not an ill-defined operation capable of failure (other than perhaps disjoint volumes): why should it fail in Rhino? You fixed your problem by jiggling the ribs inwards, and it happened to work nicely. This solution should have been performed internally by the unioning command. I would happily wait 30 seconds longer to have a reliable, unfailing operation!
@@bobmackay1856 thanks for that- Booleans are somthing that have been continuously refined since Rhino’s inception. I’m an artist, not a software dev, and I’m not even going to try and offer an explanation as to why they fail. I’d need to refer you to our devs who are a lot smarter than me. What I can offer is, when we find issues we can fix, we do it. If you have specific examples that are failing please send them to support@mcneel.com so we can analyze them and ideally improve. One other tool to look at is srfseam which allows you to relocate the seam of a closed surface, which can often make a failed Boolean work by removing a coplanar seam scenario.
One of the best tutorials I've seen. Continue like that! Simple and with humor. Well done!
Thanks! More coming!
Once again I improved my modeling skills by 10x and decrease my design time by 1/3 or less. THANK YOU! 😊
Reflector panels - genious!
Felicitaciones, gran video...
rhino 7 subd is aawesome!
excellent
hello your explanation is awesome
But can you explain how to make a box and how to put pictures and logos in it?
use the cube tool to make the box and decals, planar mapped, for each face .
Hi, I can't seem to be able to snap any objacts as you do on minute 41. Do you have any idea how to fix it? I have Osnap on. Thank you
If you are snapping using gumball, make sure to turn on "snappy dragging" in the gumball options. Also make sure your osnaps are not disabled
Thank you tremendously for your tutorials. I am an Ind Design student, and right now my sketching is terrible. Do you have any equally as good sketch tutorials? Or recommend any other recourses?
Check out Scott Robertson on UA-cam and insta. Dude is legend.
I could've sworn I'd seen this tutorial on this channel before. Was it deleted and reupload?
Yes
Hi, great tutorial!
I have a question please. How do you drag the object then snap to a midpoint of another like at 57:20?
Set your gum ball to snappy dragging in the gum ball settings
@@Rhinoceros3d Thank you
doubled in a week!
When subD boolean?
there is a project going on now, see this post-
discourse.mcneel.com/t/subd-union-help/100628/10
i dont wana tell u ur software but if u used the delete faces command, u coulda selected all the faces to delete, instead of selecting everything including the points, and having to select the fasces individually like u did.,. it woulda been easier and more professional! hah
thanks for your input!
I laughed out loud when in the middle of your brilliant demo, the Boolean Union failed! The fact that you have reached the seventh version of Rhino and you are still unable to reliably union two objects together is disgraceful! Arguing about precision and shared surfaces is bullshit - it should "just work", even if you have to detect the failure internally (by the fact that you have not managed to create a single object) and then judder things around until it does. Please fix the bread-and-butter operations before adding more bells and whistles. PLEASE!
You can identify where the problem lies in a failed boolean by running the intersection command and examining the resulting curve.
@@Rhinoceros3d I should have explained more of my use case and why the failed booleans are irritating: I primarily use Rhino through the Grasshopper interface, since I really love the parametric approach. I am generally a very happy customer! Grasshopper allows me to think more slowly and to correct mistakes made earlier in the process. It allows a simple module to be made complicated later. I mostly make mathematical surfaces, for CNC routing and 3-D printing. When a boolean operation fails in Grasshopper, the resulting failure is awkward, since it affects the downstream operations. There is no indication that the failure has happened, other than that the resulting unioned output contains too many objects. The failure happens sporadically, depending on exact sizes/alignments/interrelationships, which can sometimes be fixed by very minor tweaks to sliders upstream. Sometimes I am reduced to adding a 'move' operation to jiggle things around explicitly, so that volumes really inter-penetrate and surfaces are not shared. But real-life objects DO share surfaces. I am a software engineer; I understand the limits of representing numbers in a computer and the problems of representing volumes and their intersections/unions. I made my comment at three in the morning, when I should probably have gone to bed, but I stand by the basic message: in mathematics, unioning and intersecting volumes is not an ill-defined operation capable of failure (other than perhaps disjoint volumes): why should it fail in Rhino? You fixed your problem by jiggling the ribs inwards, and it happened to work nicely. This solution should have been performed internally by the unioning command. I would happily wait 30 seconds longer to have a reliable, unfailing operation!
@@bobmackay1856 thanks for that- Booleans are somthing that have been continuously refined since Rhino’s inception.
I’m an artist, not a software dev, and I’m not even going to try and offer an explanation as to why they fail. I’d need to refer you to our devs who are a lot smarter than me.
What I can offer is, when we find issues we can fix, we do it. If you have specific examples that are failing please send them to support@mcneel.com so we can analyze them and ideally improve.
One other tool to look at is srfseam which allows you to relocate the seam of a closed surface, which can often make a failed Boolean work by removing a coplanar seam scenario.