Make 2D and hyperthreading

i’m doing a make2D and looking at my Task Manager:
2 of my 12 cores are fluctuating at 25-50%, 4 cores less than 5%, and 6 cores at 0%

I remember from discussions in the previous NG that hyperthreading make2D was too difficult. With the overhauling of Make2D for Rhino 6, will it get hyperthreading?


1 Like

Working on big performance improvements for Make2d.

1 Like

is it possible to make “make2D” function in interior views? must have in architecture:) :slight_smile: :smile:

as currently 3d vector print is not possible.


As far as I know this should work in V5. Please provide an example of what
isn’t working.

Hi Greg,
I use make2D for interior elevations all the time. The easiest way is to set up a clipping plane where you want to take your section, and in the clipping plane Object Properties, clip the viewport you want to look at. When you make2D in this viewport you get vector elevations. Works for plans as well.

Another technique is to use the visualArq plugin which allows stepped section lines, custom wall hatching, and linked vector elevations that update when the model changes.

Based on your experience can the VisualArq plugin generate vector output of perspective views? Rhino5 can’t do that - perspective output is raster.

if you are in an interior view in perspective, its not possible to use make2D.

see attached images of simple scene, do I have to set up clipping planes to achieve this?

Hi Greg,

My Rhino 5 doesn’t seem to have any issues with interior perspective scenes. Below is an example of my viewport and a vector make2D from that viewport. No clipping planes required. Make2D seems to automatically clip to the viewport boundary.

what is the trick then? I can never get those perspectives in 2D. is your model fully enclosed, does it have ceiling?

test.3dm(237.4 KB)

I’m not sure if there’s any trick. I make sure my perspective view is current when I hit Make2D. In the Make2D properties I use the ‘Current View’ option. The model has 4 walls and a floor as one polysurface and a ceiling as a separate polysurface, but it also works if the ceiling is Unioned to the walls.

I have attached the file I used in my last post. Does it work for you?

seriously, this is ridiculous.

waiting 30 minutes to get a plan on a 12 core i7.

Aaron, is it just extrusions and simple stuff in your model? What happens if you increase your tolerance setting? Also, do a trouble shoot elimination: make2d half of your model. If no quicker then potential issues exist in that half of model (bad geometry or gremlins). Keep halving your model until you find the trouble area, and eliminate areas that are not the problem.
Little tiny things in a big complex model have really dinged me sometimes, had to run through this process to find the issue and when found, the whole model went to make2d no problem. Still slow of course, but not ‘hang’ slow.
good luck, hopefully this can help.
edit: sorry didn’t notice you were getting some help with this in another topic

Thanks for this generous answer.

I have def gone through the process of elimination that you describe above with make 2d.

I just think the lack of multi-threading is lame.

@ATH Make2D has been under par since it was introduced in Rhino v2 (?).
It was in my opinion never a really serious tool, but a way to stop us from going nuts for not having a proper 3D->2D tool. It IS better than what it was, but everybody would expect that after 10 years. It still does strange things, like hiding parts of outlines, so I hope they fix that, as that to me is more important than shaving off some time. If it had a status report then we would now how far it had come and guess on how long it would take to compete, and that would save a LOT of frustration, as not knowing, and wondering if it has crashed is the worst there is when on a deadline.

Luckily they are working on a new solution for V6.

Always calculate with Hidden lines and move the wrongly calculated ones to the right layer, then delete the rest. And group the output. And keep on nagging, as make2D is probably the biggest reason to not use Rhino fulltime if you are an architect. (And remember that many architects are used to AutoCad, so they are not so spoiled, yet)