I’ve recreated the same definition in GH2 as I used in GH1 (see screenshot). In GH1, panning and zooming work without any problems once all the active components have been calculated. Unfortunately, this isn’t the case in GH2, even though I’m using the same PC.
It’s really frustrating to work with.
Do you perhaps have any tips on settings I can adjust to fix this problem, so that once a calculation is complete, I can move and zoom the canvas just as I could in GH1?
Disabling the system-wide solver doesn’t help either.
I’ve also already set the computer’s graphics settings to maximum performance.
In GH1 turning of the Autosave features is the way to speed up large definition canvas performance. Those features options haven’t been fully developed in GH2 yet.
These are all native GH2 components or are there GH1 as well?
The shout / listen workflow gives the potential to be more modular in our workflows as well.
Backup Method is set on “No Backup” already and the “Preferences” window under “Grasshopper” does not open yet, as you said.
The large majority are GH2 but some are GH1 as well. Maybe 90% GH2 and 10% GH1 I would say - is that a problem for the canvas performance?
I thought that would only affect the time it takes to calculate.
I’m already using Shout/Listen within the definition to keep it clearer (fewer wires). Was that what you meant, or is there another way to use them to improve canvas performance?
Would having more RAM make a difference to canvas performance? I’m currently using 16 GB.
It very well may if the navigation is affected by the size of the definition. It’s also a better practice. If you edit one cluster you update the rest.
Either that or use data trees to apply logic to lists of lists.
