Talk:Rhinoceros 3D

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Commentary
Please see WP:TALK


Untitled[edit]

I have been using Rhino for several years now starting with version 1. The user interface is an order of magnitude easier to learn and better than Solid Works. In fact IMHO solid Works should throw out the current user interface and copy Rhino.

The drawback to my use of Rhino is it has serious problems with "unions" and "differences". A "union" is when two solids are joined together. A "difference" is when you subtract one solid from from another. These features are essential when you are designing molds for castings rather than just rendering them for pretty pictures. You can easily draw complex solid parts and render them but there is no guarantee they will union or difference.

The same thing goes for fillets but it is worse as the rendered pretty pictures depend on fillets and Rhino more often than not refuses to fillet the juncture of two complex solids. Also compared to Solid Works the filleting capability is limited. No variable radii fillets for an example.

Another problem is no shell command which is another requirement for molds. Shells are a constant wall thickness for a hollow part. Shells can be drawn but it is a tedious process of drawing the part twice. Copying, 3D scaling down and differencing the parts does not always provide an accurate shell.

Another problem is no draft command. Draft is essential in models that are going to be sand cast or made in hard female molds. The part must have draft or it will not come out of the mold cleanly. Again drafts can be drawn with similar work arounds to shells. This is tedious but it sure would be nice if one could specify draft angles.

Hopefully version 4 will address these problems. —Preceding unsigned comment added by 209.234.173.57 (talkcontribs) 15:48, 6 October 2006

Wikipedia isn't a review site, and the Discussion page isn't for discussing the topic, but the article itself. —Preceding unsigned comment added by 76.10.136.151 (talk) 02:10, 13 July 2008 (UTC)[reply]

Illustrations[edit]

Is there a posibility to post more pictures of models done in Rhino 3d in this article, except the only one of metallic robot that is already present? There is one my model of Apache AH-64 done in Rhino 4.0 and it's pretty detailed. Link:http://www.rhino3dhelp.com/forum/index.php?topic=395.0 There are many pictures there to chose from. —Preceding unsigned comment added by Packe777 (talkcontribs) 16:23, 2 December 2009 (UTC)[reply]

Possibly, but for an article so short, it seems excessive. If another picture were to be added, I'd suggest a screenshot of the stock Rhino interface instead. --King Öomie 16:48, 2 December 2009 (UTC)[reply]

wow those are incredible renderings. If you don't add them to the article, you should definitely replace the robot with them. I think they nicely show what's *possible*, which is important, even if they aren't somethign that a new user is likely to tackle.216.107.202.66 (talk) 12:50, 25 August 2010 (UTC)[reply]

File formats[edit]

Added file formats supported by Rhino, as seen in the Rhinoceros website. I think version 5.0 (expected do be released this year) will add some more file formats, like DWF and DWFx; specially the XML one, which is easier to read. 200.196.51.166 (talk) 15:06, 30 January 2012 (UTC)[reply]

Shortcomings[edit]

Section blanking. Content preserved here.

Despite numerous Service Releases (Rhinoceros 3D version 5 is now at SR10) there are still a number of critical shortcomings, many of which have been present since the first version of Rhinoceros;

  • Filleting The filleting of edges often fails and produces incorrect results.
  • UV mapping UV mapping functionality is extremely limited, giving bad or no unwrapping results and only works on very basic shapes.
  • Meshing The meshing algorithm used produces meshes of low quality often requiring the use of 3rd party software to fix the mesh.
  • Stability General instability, especially when using plugins, resulting in numerous crashes of Rhinoceros.

JiminyCroquet (talk) 18:39, 10 March 2015 (UTC) This section is heavily biased, unreferenced and inconsistent with other CAD articles on Wikipedia. Please refrain from restoring this to the main article[reply]


More section blanking. Content preserved here.

Suitability for 3D printing[edit]

In a recent overview 3D printing company i.materialise had a closer look at the top 25 most popular 3D modelling software programs in use today.

In this extensive survey Rhinoceros 3D only came out in 13th place, behind software packages like Solidworks and even free packages like Blender and Sketchup. The high learning curve, lack of parametric design features and generally poor meshing conversion are but a few of the reasons why Rhinoceros did not score higher on this list.

snurglab (talk) 15:32, 5 January 2016 (UTC) This section misrepresents the referenced i.materialise survey, e.g. the survey makes no mention whatsoever of "high learning curve, lack of parametric design features and generally poor meshing conversion". The same Misterkimono user has been repeatedly adding this section, first using various sockpuppet accounts and then as an anonymous user.[reply]

Rhino 7 available[edit]

https://www.rhino3d.com/7/system-requirements/ — Preceding unsigned comment added by 2A02:6D40:3491:A701:18B4:BCEB:8EDC:FDC (talk) 14:34, 7 December 2020 (UTC)[reply]