I am getting this error when I use Fume as a velocity source. Any ideas?
Thanks
It might be fixed internally already, but it would be nice if you would post the actual error report from the MAXScript Listener. The screenshot shows nothing usable for debugging.
Also, when reporting bugs, please post STEPS to reproduce.
E.g.
*Create a FumeFX sim
*Create a Stoke particle sim object
*Pick the FumeFX and Distribution and Velocity source
*Hit Simulate
RESULT: The following error appears in MAXScript Listener: …
sorry about that, had to leave suddenly and didn’t have to write up a full description.
So with the new build I get a different error message.It says there is no velocity channel in the Fume.
[list=]Made a simple Fume Sim.
Created a Box
Used Box as distibution object in stoke.
Added the Fume as velocity source.
Error msg when simming.
[/list]
I am using max 2014.
Yay! That new error popup paid off 
So the question is - did you export the Velocity channel when you made your FumeFX object? You have to add it to the list of exported channels explicitly.
If you do have a valid Velocity channel in FumeFX but Stoke is not seeing it, we will have to investigate further…
Hi
Yes, Thats the first thing i checked it is exporting the velocity channel.
So this is in Max 2014. Can you also post the version number of FumeFX?
I am running Max 2013 and FumeFX 3.0.2 and it works as expected.
It might be a good idea to post a simple scene showing the problem so Darcy can take a look at what’s going on.
In general, the error message you saw should never appear since we changed the internal functions to produce a zero-velocity field when no Velocity channel is found in the source. So it must be something deeper causing it to fail…
Hi
The problem seems to be with Fume, I was using max2014 with fume 3.0.1 but onceI updated the Fume it is working as expected now. Thanks for looking into it.
Fume FX 3.0.1 was broken and not supported by our products.
There was a bug in the Fume SDK which made it impossible to use with Krakatoa MX and Stoke. 3.0.2 or higher is required.
Glad to hear it is working now.
Reusing the same Fume sim for various pflows is very liberating. I have 5 pflows in the scene and I thought I would have to sim them each separately. But with Stoke I just use the same sim over and I still get what I want, which is secondary particles coming off the main ones. I love it! 
I was wondering though if you use a field loader you dont have the option to turn off limit fields to bounds(as in a stoke field) which leads to particles hitting the edge of the fume grid. In this case is the best method to use the field loader as a velocity input in a field magma.
Thanks
Yay! We must have done something right! 
The Loader cannot produce data outside of the original FumeFX grid because there is no simulation data there. The Field Magma often can because the field you generated using your Magma nodes can be evaluated anywhere in the world.
If you load the FumeFX simulation into a Field Magma, you can still evaluate anywhere in the world, but the FumeFX will have zero values outside of the loader’s bounds. So you could load multiple Filed Loaders into a single grid and blend them together, add them together and so on and produce larger fields than the parts you are mixing.
Still, given the nature of Stoke Particle Simulations, if a particle reaches the edge of the Fume sim and there is no other data to move it further, it would stop there. This was true in Stoke 1.0, too. So it is up to you to provide more data from other sources in the Field Magma flow, or pick additional velocity sources in the Stoke Velocity Sources list to prevent it from stopping, e.g. space warp forces, other simulations, procedural Magma stuff etc.
If using the PFlow Stoke Field Follow, checking the Limit To Bounds should theoretically let the particles continue moving outside of the Field Magma’s grid. When the checkbox is checked, the operator will not even bother asking for a value outside the grid, so the particle will continue with its last known velocity. If you uncheck Limit To Bounds and there is no valid data outside the Field Magma grid, a 0,0,0 velocity would be returned and the particle would stop…
Definitely doing something right. 
Before saving out Fume to PRT via pflow was painful and superslow. With stoke I can do a 3 million in an hour or so.
This seems like the way to go. Although for now I think I will sim a bigger fume grid. Also I realised the last time I had particles moving beyond the grid I had a Wind added as a velocity source as well thats why they continued to move.