Rhino 8 Development

I used to work at an office where they used gbs worth of files easily on and when i exported the same file to rhino it slowed down my laptop. I just assumed rhino was bad at handling exports from sketchup. but was there something i was doing that was wrong?
Thank you for your reply!

Could it be that they’ve been running those files on workstation towers (quadro cards and all that good stuff) , while you tried to open the same files on a ultrabook?
All-in-all it seems the consensus is that mesh handling performance in Rhino is “really fine, but could be fine…er”


i had a large city model in skp. it orbitted well in sketchup but after import into rhino it was impossible to orbit. i suspect not meshes were the problem but nested blocks and groups.

When you do a Sketchup export, you tend to get not only the meshes, but every single edge around each mesh face as a curve. Try exploding your SKP import, and deleting all curves. Then run Join and Weld on the meshes.

There is a big difference between exporting from SKP and importing the skp directly in Rhino. Try both. We find that either way, things get messed up. They just get messed up differently. So depending on what you’re trying to do in Rhino (blocks, layers, colors etc), one or the other might work better.

1 Like

I’m not particularly in love with the ZBrush UI, but it’s not like the Rhino one is a masterpiece!

SketchUp is for soccer mommies (not that there’s anything wrong with that). :slight_smile:

1 Like

the difference is, we are always open to suggestions for improvement !


Sure, and that’s great, but do you know for certain that the ZBrush folks aren’t taking into consideration community suggestions?

I cannot agree more!!


I really try hard to establish Rhino instead of AutoCAD in the office. I told an older colleague I see Rhino is even better at drawing in 2d than AutoCAD (and it is), but he said spontaneously “but isn’t Rhino bad at layout printing?” Rhino has a bad reputation here.
I for my part know (mostly) how to deal with plan layouts, and circumvent the shortcomings. It could easily replace that old retarded AutoCAD, but to convince the old school guys it will take Layouts/Details to be better, too. (Yeah, hardwired 2d CAD brains from the last 25 years. Maybe reasoning will not help at all, only a change of generation)

Now the talk is to add ArchiCAD to the arsenal, because it’s ‘so good at 2d drawing’… oh man. And the Rhino<>ArchiCAD connection sucks.

The broken record:
Please, at first, focus on the layer visiblitiy problem in Layout Details. That’s really ugly.
There’s other stuff, too, but you know all this already.


It is - especially the management of attributes (line types, fill types - why are they such a pain in Rhino?). Actually, the best would be to have a combination of the two - I really like the pet palette and the way you can modify distances relative to a point by simply typing + or - after a distance - but I really miss the Scale1D functionality of Rhino, for instance - or not having to mess with GDL objects for simple 2D blocks… Argh.

Agree. Graphisoft is getting some bash over this at the Archicad-Talk forum these days…

1 Like

And colors. The new color chooser is fine, but still global colors (= instanced colors) would be very handy:


I would like to see some control of dashed and continuous lines in layout when model is shown in technical view with hidden lines. This presentation of edges should have same tools for linetype and thickness management as normal curves.

I don’t like idea of having both 3d model and seperate curves for 2d drawing.

Also some dynamic section of solid in layout detail would be cool.

1 Like

Rhino8 supports output in PLT format, which is used by many cutting machines and should be used as a design and development software

Have you ever tried contacting the ZB folks directly about anything? My experience with them over the last 10 years or so has been, saying it politely, a bit lacking.

Not really. I don’t use ZBrush any more. The rare cases where I need some digital sculpting are covered by Blender nowadays.

That’s a shame! I guess many companies are like that, but I can also somewhat understand why.

+1 to this and all previous comments concerning blocks.

Block system is the main thing about Rhino that makes some architects I know prefer SketchUp.

Architects are used to a workflow involving nested blocks, and that is insufferable to manage in Rhino.

Also as others mentioned before too, parametric blocks seem like a very natural and obvious extension of Grasshopper into more “normal” modelling workflows, ie. a block holding a grasshopper file as its DNA, remaining always baked and interactable with, but modifiable through block attributes.


PLEASE, put labeling and information in a way that will make interoperability with Revit better and native. Maybe use blocks similar to families or just in a way that can change between programs with no problems

When will V8 be available for beta testing?
Rough estimate if you have one yet?


1 Like

Is there something about the concept of the parametric blocks that Visual ARQ Grasshopper Style Elements won’t do?
From your description, it looks exactly like Grasshopper Style.