HumanGenerator
HumanGenerator copied to clipboard
optimization (stored imports)
Optimize load times by caching loaded data
The scope of this issue has become nebulous as we refactor and move away from Makehuman's code base. Revisit later.
was this resolved in the new human class?
was this resolved in the new human class?
Kind of. Human prims do store their properties, but the values still need to be loaded back into Makehuman every time a selection changes. Didn't necessarily speed anything up, just more elegant than previous method.
We can re-examine this when we move away from an internal Makehuman instance
we have this as on-hold, so lets keep it here
request we clarify desired behavior + discuss implementation