McNeel 'THE OSCARS' best custom code best model and more

[Rhino_Bulgaria (Bobi)]

Also, best most ignored ideas for years. Sadly, I immediately win this particular category…

Rhino urgently needs these tools!

Currently, Rhino is in something like a NURBS-crisis. Alias made a huge progress in the past 20 years, unlike Rhino’s main NURBS surfacing and control point editing tools that are nearly unchanged since Rhino 2 (with a few minor exceptions). The last few versions of Rhino focused more on non-NURBS stuff, such like tools for Sub-D, 3d meshes, ShrinkWrap etc. While these are nice additions, the NURBS tools are left in the corner. Both, “Blend surface” and “Match surface” lack a huge amount of fun…

---

Most critical bugs to be fixed in Rhino 7:

Never trust Rhino for 90 degree extrusions (BUG)

BUG: Huge deviation by the "Distribute objects" command

Biggest bug in Rhino related to single-span surfaces

Bug: Inability to move an object to the CPlane zero

Here are their respective topics with deep explanation. These 4 bugs make the corresponding commands unusable for me…

Never trust Rhino for 90-degree extrusions

There is a bug with Rhino which leads to an unwanted loss of accuracy when extruding planar curve profiles on a custom CPlane. The bug is caused by the '_CPlane _Object which fails to maintain true planar coordinates. On the other hand, a Cplane set by the '_CPlane _3Point command properly aligns the coordinates to the planar curves. You can observe the bug in the attached video. I also upload the same 3dm file here (Rhino 7): Never trust Rhino for 90-degree extrusions.3dm (141.8 KB) […

Gumball User Experience Suggestion

Maybe it’s tied to the inaccurate bounding boxes used by Rhino since more than two decades ago. It was discussed in another topic that the inaccurate bounding box was made to save calculations by the old CPUs. However, it’s now 2025 and we still use that flawed approach… Trying to snap an exact circle or a box with Gumball’s Snappy dragging is almost never accurate, because it uses the bounding box which itself is inaccurate to begin with. Other tool that suffer from the same bug is ! _Distrib…

Rebuilding surface produces weird CV distribution

This particular bug have been discussed in several topics over the past few years, but I think that the programmers at “McNeel” should take it seriously and try to fix it, because “Rebuild surface” is known for producing highly distorted, unusable conversion of single-span surfaces. That’s pity, because this particular bug in Rhino destroys the general flow of the control points, thus directly impede its users from achieve high-quality surfaces. I wonder, is it going to be fixed any time soon? …

Bug: Inability to move an object to the CPlane zero

Looks like there is some bug while dragging an object with one of the 3 Gumball arrow handles and setting a 0 to the used direction. Every time I do this, Rhino 7 will move the object in a different, totally random location that’s not the exact zero of the active CPlane. Тhat bug should be fixed as it leads to unwanted inaccuracy. Typing zero while dragging with the Gumball’s arrow should always move the selection to the zero of the CPlane in the chosen direction. [Bug: Inability to mov…

---

As for the “Best script” category, I vote for @jim 's filleting script from this topic:

Filleting Tangent Surfaces

For those Rhino users who use the FilletSrf command and would like the process to be a little less tedious here is a Python script that will make strings of fillets that expands FilletSrf capability when filleting tangent surfaces: FilsrfEX.py (40.1 KB) This script works the same as the filletsrf command - just pick 2 surfaces that you want to connect by a fillet. The difference is the script will continue to make all the tangent fillets connected to the first fillet until it runs out of tangen…