Rhino 8 super slow

Rhino Rhino for Windows
1

I modified some sub-d objects using a cage and suddenly everything is super slow. Even moving an object with the gumball takes like 50 seconds to complete it.
Any idea what it could be?

2

My computer gets super slow when applications have used up most of its RAM. If this is the problem, you can restart your computer to free up some RAM.

But your case sounds different. Bring up the task manager to see if your RAM is getting full. If not, the problem is something else.

Regards,
Terry.

3

I restarted my computer and it is still doing the same thing.
Now the file is taking forever to open. it is a 145 MB file.
I think it has to be related to the meshing process. If I move any geometry on mesh mode, the response is fast.
This is killing me. I needed to finish this file today. Any other suggestions?

4

Can you share the file that’s slowing down your PC and include a systeminfo? That would be a great help in helping us help you

5

The company does not allow me to share the file.
I will try to replicate the issue with some portion of the file, to be able to share.
But this is not the first time I have had this issue with Rhino 8.
The weird thing is that the file is opening very fast in Rhino 7 and I have no issue in Rhino 7 either.
So, I has to be Rhino 8

6

Slow_Issue1.3dm (2.2 MB)
I have the issue with that file.

7

I can replicate the problem, simply moving the geometry make Rhino 8 hang for some seconds.
Rhino 7 do not have this problem.

I am missing some texture when the file load…

If you change the texture mapping type from “Custom object” to “Surface” , the problem stops:
2024-09-27 23_15_44-Window

1 Like
8

Thank you for looking at this. I will give it a try.

9

Awesome! That worked! Thank you!
Custome mapping was the main reason we changed to Rhino 8. : Let’s see how we deal with that.

10

Recap:

  • attached geometry extremely slow to move if rendermesh is visible (non-wireframe mode)
  • problem only in Rhino 8
  • problem gone if texture mapping type changed from “custom object” to “surface”

Bug or not bug, I do not know. Surely it’s quite slow for a simple move transformation…

14

Yes, this is a performance issue with the custom mapping. Filed as RH-84054 Custom mapping slow

1 Like