Hi,
I'm trying out generative component and have a simple graph where i calculate some points along a curve and create some objects on those points.The speed of the graph is horrible, there is a constant delay when doing almost anything....
Add new node (graph remains unchanged) delay > 7 seconds.
Connect / remove wires > delay more then 7 seconds.
Move graph node > delay around 1 second.
is this 'normal' behavior? Is there way to pause/stop running the graph (so that i can quickly change nodes and after multiple change run the graph to see the result) ??
i am using version 10.03.00.36
Hi Martijn,
We have been addressing performance issues in Update 4. Once it is released (AECOsim Building Designer timeline), you should see improvements in performance in the actions you describe. Would you mind sharing a script with which you observe the 7 second delay when placing nodes, so we can verify that Update 4 resolves that issue?
We don't have a pause capability for the entire Graph. GenerativeComponents does support deferred dynamics and deferred updates on individual nodes. In the Node Properties editor there is also a facility that lets you stop execution of the node which you edit until you are done with your edits for that node. However, I don't think these capabilities help with the problems you describe in the way you desire.
Your suggestion is interesting. While we hope to improve performance so that this type of "pause evaluation" capability may be less needed, as GC models grow, such a feature may still be useful. I have filed an enhancement for this type of capability.
Regards,
Volker
I just upgrade GC to 10.03.00.36 revision and having same problem. Is there a way to go back to use older version of GC until update 4 ?
Hi Emre,
My recommendation is to have a few days of patience and wait for Update 4. When upgrading I'd recommend removing Update 3 as described below before installing Update 4.
I do not think moving back in versions is recommended. In any case, after backing up your datasets and saving any scripts as GCT files, a thorough uninstallation of all related Bentley software, reboot and removal of all related residual files in Program Files, ProgramData (backup datasets!), Users/<user name>/AppData/Local, before installing any prior version could perhaps make this work --no guarantees, though.
Files and scripts will not be backward compatible. As mentioned earlier you might need to save scripts as GCT files and then copy/paste their contents (without the header information) into the Script Editor --however, additional editing might be required for them to execute in prior versions.
Hi Volker, Thanks for reply. I will try to follow your recommendation and wait for update 4.
I did check it little bit more and share what i found with bentley support. For my case it is happening only when i create a polyLine node with ByRange function. Any attribute change on graph is kind of triggering an Update Node Tree command over polyLine or range nodes, which cause 7-10 seconds lag.
Thank you, Emre, for willing to wait. The problem you describe is one that is fixed in Update 4. I confirmed this in the latest build which will most likely become the soon-to-be-released Update 4 on an example file in which a similar operation takes about 20 seconds in Update 3 and perhaps one second in Update 4.