I use this command in a button script for objects, where the display mesh looks bad. Some times it helped.
! _Explode
_rebuildedges _enter
_join
I use this command in a button script for objects, where the display mesh looks bad. Some times it helped.
! _Explode
_rebuildedges _enter
_join
!_Circle command line highlights P and O keys for options 2Point and 3Point, but they work with keys “2” and “3” as well. Was pleasantly surprised with this possibility.
I really enjoyed this wonderful thread, and while reading (and contributing) I realized that it would be a pity to let those tips rot here.
So I decided to go bold and collect a ‘best of’ and put it on Github.
You can see the collection ››› here ‹‹‹.
I want to continously update this site. And while I done it mostly for myself as some kind of Wiki for the Rhino secrets (it’s so easy to forget something…), I hope y’all might enjoy it as well.
Great work: looks very nice too
That’s great!
I never thought this thread would be so popular. It would be great if users could upvote tips so the best ones would be shown on top (reddit style).
really cool work! Thank you!
Hi Luc - just fyi - https://wiki.mcneel.com/rhino/hiddensecrets
-Pascal
Oh dear…
Thanks for the link, Pascal!
I’ve been following this thread for a while now and I decided to compile some of the tips in a small video collection I’m building. Still working on it… Here. Is in Spanish too btw
here’s mine:
best 10 crv tools
10 srf tools you can’t miss
10 solid tools you can’t miss
hope you like it.
(NOTE : there’s a skippable fb enter page)
step1:
step2: while drawing, hold middlemouse button down, hover over desired snap, then release.
In many occasions, “Curve boolean” creates inaccurate results. Using “Trim” and “Split” is slower, but much more accurate. Rhino 5 had huge problems with that, and Rhino 6 is not an exception either.
Can you post some specific examples? I have used CurveBoolean regularly for many years and never noticed an accuracy problem…
Omg, finally I know why mine sometimes failed… THANK YOU!
I stopped using “Curve boolean” long time ago, but I will notify you as soon as I find a good example of the aforementioned issue with lower accuracy.
I use CurveBoolean all the time for creating low tolerance parts that get cnc milled and never notice any inaccurate results. Only issues I sometimes might get is with self-intersecting or overlapping curves.
Would interest me what kind of inaccuracies you are getting, as I too use the command for later CNC milling a lot.
Likewise. Makes me a little concerned - important to know whether there is something to be concerned about.
BUG!!!
Another huge issue with tolerances comes with the “Line: Tangent and perpendicular to curves” tool. This seems to happen when “Planar” is turned on. Open a new scene, set the tolerances tight enough (Model units: Millimeters; Absolute tolerance = 0,001 mm; Angle tolerance 0,1 mm or 0,01 mm), then draw in the Front viewport a circle, followed by a line or a point. Then run the “Line: Tangent and perpendicular to curves” and draw the tangent line starting from the circle and ending to the end of the line or to the dot. In many situations there is no real tangency, despite what the name of the tool suggests. Doing exactly the same in the Top or Perspective viewports (the latter uses the XY plane) sometimes will result in a proper tangency between the circle and the tangent line, but sometimes will be also wrong.
Here comes the funny thing. If you use the “Set XYZ coordinates” tool to flatten the already flat circle and the line before building the tangent line, the tangency will work as it’s supposed to be. I have no idea why “Planar” will mess up the tangency since all the drawn objects are already on the CPlane level 0.
This is why, I suggest to use “Set XYZ coordinates” before using the “Line: Tangent and perpendicular to curves” tool. It does its magic. Here is a 40,5 MB GIF video that shows the issue:
https://mega.nz/#!uxx1FAqa!ql6Tj0Ec2a14PR0kExW21OmE1Wjv8pF3IuNGLR8CJ0M
“Line: Tangent and perpendicular to curves” has another limitation. It will not align the tangent line to be actually tangent to the flat circle or arc used for its creation while the “Planar” setting is active. With other words, if the totally flat circle or arc is vertical or oriented at a random angle in the 3d space, Rhino gets confused and refuses to set the end of the tangent line upon picking a point with the “Osnap”'s “End” turned on. Basically Rhino will ignore the tangency and the “Osnap” while “Planar” is on. In this case the resulting tangent line is definitely not tangent. I think that any command that used tangency must ignore “Planar”, otherwise there is no tangency.
Grasshopper?