Tweet
Started with this in the Rhino forum but after some troubleshooting it has become clear that it is a V-Ray issue.
I’m working on a Rhino file (~260mb) which every time it opens I have to wait about 30 minutes for it to become usable. The first 30 minutes, commands have a huge delay (5-10 seconds) if they even work at all. Even zooming in and out or panning has the delay. Somewhere around 30 minutes after opening this delay is gone and the file becomes more or less fine to work with. Additionally, when this file is open my computer will completely freeze 1-2 times per day. This happens more often during that first 30 minutes after opening. I’m using the file to to render with V-Ray. I have a decent amount of materials and proxies but I have tried to keep the file size down by using proxies, especially for objects with lots of polygons.
Part of the troubleshooting that was done was to open with the V-Ray disabled. When I did this, the file opened quickly and without issue.
I realize that this issue could likely be solved by increasing the performance specs of my computer but I am really trying to figure our what specifically is causing this and what I can do in the interim to make things run smoother.
A little about my computer:
CPU - Intel ® Core™ i7-7700 CPU @3.60 GHz (8 CPUs)
RAM - 32GB
GPU - AMD Radeon R7 450
256GB SSD (15-20GB of space left)
I’m working on a Rhino file (~260mb) which every time it opens I have to wait about 30 minutes for it to become usable. The first 30 minutes, commands have a huge delay (5-10 seconds) if they even work at all. Even zooming in and out or panning has the delay. Somewhere around 30 minutes after opening this delay is gone and the file becomes more or less fine to work with. Additionally, when this file is open my computer will completely freeze 1-2 times per day. This happens more often during that first 30 minutes after opening. I’m using the file to to render with V-Ray. I have a decent amount of materials and proxies but I have tried to keep the file size down by using proxies, especially for objects with lots of polygons.
Part of the troubleshooting that was done was to open with the V-Ray disabled. When I did this, the file opened quickly and without issue.
I realize that this issue could likely be solved by increasing the performance specs of my computer but I am really trying to figure our what specifically is causing this and what I can do in the interim to make things run smoother.
A little about my computer:
CPU - Intel ® Core™ i7-7700 CPU @3.60 GHz (8 CPUs)
RAM - 32GB
GPU - AMD Radeon R7 450
256GB SSD (15-20GB of space left)
Comment