Copy link to clipboard
Copied
I often get Designer doing that temporary couple minutes freezes when it gets grey saying "coocking" or "renderenig cash" while showing only 20% of using memory , close to zero gpu usage and not that much of cpu stress too. Still I hear how my pc cooling system is getting lauder .
So what may be an issue ?
Hello,
Thank you for reporting this. If this occurs after making a change in the graph, such as adjusting a parameter value, then the unresponsiveness is likely caused by the invalidation process. Invalidation involves traveling the graph and assessing everything that needs to be recomputed. If a graph uses a lot of subgraphs, with multiple levels of depth, then that process can take a long time.
We are actively working on making this process more efficient and improve Designer's responsiven
...Copy link to clipboard
Copied
Hello,
Thank you for reporting this. If this occurs after making a change in the graph, such as adjusting a parameter value, then the unresponsiveness is likely caused by the invalidation process. Invalidation involves traveling the graph and assessing everything that needs to be recomputed. If a graph uses a lot of subgraphs, with multiple levels of depth, then that process can take a long time.
We are actively working on making this process more efficient and improve Designer's responsiveness when working in large projects.
In the meantime, you can reduce the invalidation time by limiting the portion of a project that needs to be recomputed when making a change. For instance, do not view a main graph's outputs in the 3D View or 2D View when working on a subgraph. I understand this is not ideal, this issue is impacting our own technical artists as well.
Also, feel free to share your project with me so I can assess what optimisations can be made to reduce invalidation times
Thank you for your patience.
Copy link to clipboard
Copied
Thank you Luca . My sbs used a node from some other sbs I used as a test ground with lots of saved functions and dozens of copies of same things as versions with lots of links to other sbs and so on and on . Once I recreated that node cleaning everything redundant keeping only what absolutely necessary and deleting all unnecessary switches it started to work like a breeze. My guess it's got nothing to invalidate .
Copy link to clipboard
Copied
Indeed, that is the most likely cause. It makes sense that performance would be better in that case.
Thank you for following up, I am glad you can now work smoothly!
Best regards.
Copy link to clipboard
Copied
I have a question . Would SD invalidate node inputs /outputs and branches that is set invisible? Like those in Material nodes?
Should I avoid material nodes?