How can I decrease the memory usage while I am rendering polysurface? It’s not so complicated building. Texture size is 8MB.
As you see in 1st screenshot, the memory usage is high.
2nd image shows rendering bug (highlighted objects are not rendered despite I put UV mapping).
On 3rd screenshot you see, that after I made some more windows and switched to rendered mode, the memory usage became extremely high.
Those numbers are not “high,” it’s more like baseline noise you can’t tell anything from. People use Rhino on models with 5-figure object counts and 8-figure render mesh polygon counts without too too much trouble, with decent hardware.
What part is the problem? Can’t say anything about your render mode glitch without the file, the memory allocation is not an actual problem, it just takes a lot more memory to use the various rendered mode graphics features than to not use them, about a zillion things are suddenly all asking for a certain amount of memory regardless of the size of the model. How much were you expecting it to go up by? The size on disk of your texture? That’s simply not how that works, not at all.
Please run the Rhino command _SystemInfo and paste the text it generates in a reply here. We’ll have more information to help determine what could be the cause.
Windows 7 SP1 (Physical RAM: 16Gb)
Machine name: HAIK-PC
Computer platform: DESKTOP
Standard graphics configuration.
Primary display: NVIDIA GeForce GTX 1650 (NVidia) Memory: 4GB, Driver date: 8-12-2020 (M-D-Y).
> External USB display device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
Primary OpenGL: GeForce GTX 1650/PCIe/SSE2: NVIDIA Corporation. OpenGL Ver: 4.6.0 NVIDIA 452.06
> No graphics device is being used for OpenGL
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 8-12-2020
Driver Version: 27.21.14.5206
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
As you can see from this section, the system reports that no GPU is being used for OpenGL. I would try updating the GPU drivers first (open the Notifications panel and follow the links to the download site), and, if that doesn’t make things better, try a clean install of those drivers.
-wim
Hmm what is your monitor configuration? It says “no graphics device is being used for OpenGL,” that’s not good. Maybe it’s just the driver needs to be updated as Wim says. Is the monitor connected through some sort of hub? Some of those things have a horrible little GPU of their own built-in that just causes all sorts of trouble.
You do not have the latest driver. For stability you should use the Studio Driver. For your GPU the current driver should be NVIDIA DRIVERS NVIDIA Studio Driver
To see the proportion here is a screengrab of the entire texture in the uv editor. The selection is still the same as above, but it is so tiny on the next grab that the gumball center dot completely obscures it
What memory problem, again? There is no memory problem. If this was consuming several GB, that might indicate a problem, but still being under 1GB is essentially nothing.
Now I might be talking out of my butt here but this is definitely true with a lot of stuff, when Rhino starts doing OpenGL stuff on the GPU, that requires allocating at least as much memory as is being consumed on the GPU in regular RAM, because the software doesn’t actually directly talk to the GPU, it works with some area in RAM that is mapped to the GPU, that’s handled at another level of the OS. “Direct access” is a bleeding-edge feature that’s only available on some of the latest hardware. And that’s just ONE example of all the crap that’s going on. So yeah, I’m not seeing a “problem” here, unless you’re using 32-bit Windows.
The problem is, when I drag the small parts on UV map, if they are more than 200-300, the rendering changes and moving process take too much time. And when I copy-paste the object, I face 30-40 sec loading.
