+1 would love to use the data operator too
Today I personally tested "tyFlow_scaleScript_001.max" and I found that the speed of the script operation particle did not reach my ideal. Then when you map the height of the particle with the texture, the data options are faster than the current scene. I want to know why.
If you don't believe my feelings. I will provide a test scenario file that you can compare yourself.
A little bit more, the data operator, I admit that the script is fast. But for a scenario, the speed at which the data operator slows down is acceptable. If there are graphical operators, we will work more efficiently. When there are modifications, we only need to modify the parameters. However, the script operation requires us to modify the code to eliminate the bug. This makes the work very bad
The default script example is single-threaded.
You need to enable multi-threaded scripting to get the full speed out of the script operator.