Open johnnyquest opened 11 years ago
see also #403
any dynamically generated code should be passed on as a single string detail attribute instead of using a hidden asset parameter to store the code. the latter can cause evaluation loops and crashes. see #392
...and "automatic" code generation, a la Scatter qL SOP or Attrib Builder SOP. (This would get rid of the internal for-loop, and would be way faster and true multithreaded stuff)
(see code in Ray qL SOP)
more like the Time Blend qL SOP
should have 3 inputs, and "get from input 1/2/3" for weight attrib
This could be rewritten as an Attrib Wrangler gallery item (e.g. see the particle group visualizer dop/pop wrangler), and this asset should be sent to the graveyard.