You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a crowd with instancing enabled and a huge amount of duplication (1200 agents duplicated several times to make 20500 agents). Based on stats from an Arnold render, the instancing is working as expected, but there is a unexpectedly high amount of "unaccounted" memory reported. It could be related to #15 or could indicate another memory issue in AtomsGaffer, or in Gaffer itself.
The text was updated successfully, but these errors were encountered:
Just noting that #15 and #36 did not fix this issue. I think our best bet is to tackle #35 first, to rule out any unaccounted memory coming from the Atoms side of the fence.
We have a crowd with instancing enabled and a huge amount of duplication (1200 agents duplicated several times to make 20500 agents). Based on stats from an Arnold render, the instancing is working as expected, but there is a unexpectedly high amount of "unaccounted" memory reported. It could be related to #15 or could indicate another memory issue in AtomsGaffer, or in Gaffer itself.
The text was updated successfully, but these errors were encountered: