I am finding that when a GC model becomes large in size, that the commands in graph etc. are very very slow?? When I create a model, it is sometimes complex with many variables. i try to split up my models as much as i can but I find that sooner or later I need to add more nodes? Is there anything that can be done to remedy this?
Hi Richard,I'm a new user of GC myself and I've had the same problems. To add on to what Alifur advice, I noticed if you turn off the Auto Save function that speeds the whole thing up significantly.
I have tried with Auto Save off and I found no significant speed change, and also it could be quite dangerous with this setting off.
I am also finding that when i change structural member sizes or change any of the parts or families it really becomes so slow that I need to get out of the model and get back in? That helps until I create more commands or add more nodes then it just gets so slow again? I am really battling with others within my workplace about speed of GC and maybe I would be better off to do modelling manually??
RIchard that's interesting. You seem to have identified the exact action which may cause a slow down which is great. I will reach out to see if I can get the script and see if we can repeat the action and have it attended to.
For anyone that finds the exact action the that may cause a slow down, we would like to hear the description and see the example. Feel free to raise that via a Service Ticket. It would help greatly.
Thanks Stuart
Worth noting that even without using the structural elements (I've never actually used these) there is still a lot of lag in GC, so this is definitely not the only issue here. I recall Wayne saying a while back that getting out and back into the model improved performance, and I have experienced this as well but it only helps to a certain degree: The larger the graph or dataset, the more sluggish the performance is in the GC GUI - something is causing a lot of unnecessary overheads since opening the same model without the GC interface loaded has no such issue when navigating in 3D. I suspect it is GC constantly evaluating if it needs to update any graphics / elements in the model, since it will work just fine on small scripts, but scale it to larger datasets and it becomes unusable, with inputs to freshly placed nodes that should have no effect on the model taking an unreasonable length of time for the changes to be applied.