We did not want to document the MAXScript side of things yet, because Beta 4 completely changed the way the simulation is controlled.
You will now find three scripts in the folder, the StokeUI.ms, a StokeSimulator.ms and a StokePartitioning.ms (which is still WIP).
I will start documenting these now since we believe they won’t change much anymore.
It lacks examples, but I just wrote a quick Velocity Field Visualizer by creating a plane and setting its Vertex Colors based on the results of the EvaluateVelocity() method exposed by the Velocity Field interfaces, so I hope to have more to share in the near future.
Here is a preview:
[attachment=0]STK_Beta4_VelocityFieldVis_67f_v001.png[/attachment]
The content of the other Stoke scripts represents ONE possible implementation of particle advection.
For example, right now the Stoke UI provides a global setting for the Particle Velocity sources (Grid Size, Padding, Fluid Motion), but it would be possible to implement these per-source. We felt it would be easier to set up with a global control, but if you want to modify the existing simulator or write your own where each particle system has its own grid size etc, it is quite easy to implement differently.
Another thing - you can take the StokeBase class and write a PRT Player scripted plugin that reads PRT sequences from disk and caches them in memory, minus all Stoke simulation stuff. So for people who work a lot with Krakatoa, it could provide a faster alternative for playing back PRT sequences with awesome memory caching… I wrote myself one, we might provide it in the future.
I have some more ideas about possible scripted tools employing the MAXScript access to velocity fields data. Stay tuned!