Hi there, I am pretty new to GH and I am wondering how to make sure that my laptop runs smooth when creating 3d geometries in Rhino through GH. My specs are i7-10875H CPU, 32gb RAM, GeForce RTX 2070 Max-Q. Also, an example of when the laptop is slow is: I use an attractor point on a grid to change both the radius and length of cylinders on a surface. When I adjust the MD slider to play around with the cylinder parameters, the geometry in Rhino takes a long time to refresh and switch to the new parameters.
We’d have to see the gh file to be able to tell if there is something amiss with that or not.
Please run the SystemInfo command and copy-paste the result here. If there is something blatantly wrong with the set-up, we might be able to tell from that information.
-wim
There are two different SystemInfo commands: Rhino command and Microsoft Windows command. You have posted Microsoft Windows command, but Wim Dekeyser asked you about the Rhino command.
Windows 10.0.22000 SR0.0 or greater (Physical RAM: 32Gb)
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2070 Super with Max-Q Design (NVidia) Memory: 8GB, Driver date: 12-29-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 511.09
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Secondary graphics devices.
Intel(R) UHD Graphics (Intel) Memory: 1GB, Driver date: 12-3-2021 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
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: 12-29-2021
Driver Version: 30.0.15.1109
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB
Thanks for that information and the GH file.
When you say “the geometry in Rhino takes a long time to refresh and switch to the new parameters”, how long are we talking about here? I ran that file on my old macAir and the response is pretty much instantaneous. Do note, however, that the file that you posted doesn’t have an attractor that modifies the radius nor the length of the cylinders - only the shape of the surface they are created on. Perhaps you meant to post a different file?
-wim
Thanks Wim, if I plug the mapped output of remap numbers to the radius of the circles, then it becomes really slow (it takes at least 30 seconds to refresh). Also, if the files I sent before refreshed almost instantaneously on you macAir I am assuming it should run pretty smoothly on my laptop, however it is lagging about half a second. I just wanted to understand if there is something I am doing wrong.
It sounds like you have some mismatched data trees.
In your file I see the ‘mapped’ output has 984 values in a list. Your circles are in 21 branches, each with 21 items. Connecting these to the radius input would mean generating tens of thousands of extrusions with each parameter update.
I presume you actually meant to make the radii dependent on the distance, which you can do like this tree_fix.gh (19.6 KB)