Every time I have checked the create fluid motion box in my stoke it crashes max. Every single time I check this it crashes. I am using version 1.0.051286.
Does anyone else have this problem?
Thanks.
This is the first time anyone reports this as far as I know.
When you say crash, does it crash to desktop, or does it cause an error in MAXScript? If the latter, can you post a screenshot?
Also, does it crash “when you check the checkbox”, or “when you simulate with the checkbox checked”? From your post, it is not clear what action is performed when the crash occurs. This is why we prefer error reports with numbered steps that indicate what you did and what the outcome was. A screen capture video would be even better 
Finally, what version of Max are you using? Does it crash in all your Max versions if you have more than one?
I personally tested mostly in 3ds Max 2013 64 bit.
Thanks for the feedback!
sure thing Bobo, I will be more specific here:
I check the box and it crashes Max to desktop when I hit simulate. I have a Thinking Particles system that I setup that is my distribution and velocity source. When I uncheck the box and run the simulation it works as expected.
I am running Max 2012 x64 on a windows 7 x64 machine. I have a copy of max 2013 and 2014 but I do not have all the plugins that I am using for those two so I am unable to duplicate this setup with those other two versions.
Hope this helps. Please let me know if you need anything else.
-Christian
Ok, this is very helpful.
Can you try creating a simple PFlow or even a Spray system and run the same Stoke with the option checked to see if it still crashes?
This way, we can concentrate on the TP aspect if it is related to the cause, or look deeper if it crashes with ANY particles.
I will go and test in 2012 with TP myself to see what happens on my system…
So I opened Max 2012 64 bit, loaded an existing scene with TP in it, distributed 10K particles on a ground mesh that was used to roll stones onto using TP, and picked the TP particles as the Velocity source. With and without Create Fluid Motion I couldn’t find any problems.
So now the question is - does it crash with EVERY TP scene you make, or with this particular one you are using?
Would it be possible to get the simplest possible scene setup that causes the crash so we can test it here?
It is quite possible something about your TP setup is different and causing the problem…
Bobo, thanks checking this out. I tried another scene that I had put together that was not TP or Particle flow related but which I had imported a Realflow SIm into a prt and as soon as I checked that button I got a crash just like the TP one.
Having said that, do you still want a scene from me? If so, what would you like me to put into it? Do you still want me to do the test with Particle Flow?
-Christian
I would like to get ANY scene of yours that crashes with that option on.
I want to see if it crashes here or not. If it does not, then there must be something special about your system.
It would be useful to get some more people to test it on various machines to see if it is a common problem or localized to your PC.
ok, here is a simple scene. Just turn off the kraktoa prts and turn on the tp systems and then try and run it through Stoke with the option on. This is a scene that I did that with and crashed on me.
I did have one of the artists here try it on their machine as well and the same thing happened. We all have the identical machines here that we are using. They are HP Z820’s with the E5-2665 chips, running on Quadro 6000 cards.
-Christian
ForBobo.7z (38.9 KB)
I don’t seem to have the FumeFX TP plugin, and something happened to our TP licenses too (so I cannot open the UI to take a peek).
Can I assume you are driving the TP particles with FumeFX?
Can you set up a TP that does NOT use anything outside TP, so no FumeFX, and see if you still get a crash?
We are dealing with multiple plugins that might or might not work well together, so debugging them one at a time is key.
Please create a simple TP with just a simple PositionBorn op and drive some Stoke. Does it still crash? If it does not, add a FumeFX op and try again…
I will try to get this to work here next week, but you should really start simple and exclude each component that is uncommon first.
ok, so I stripped this back to simplicity like you said and here are two max files that you can hopefully use. I took the tutorial scene for stoke that demonstrates fluid motion and I followed this to create a basic scene with a plane and a space warp and two stoke objects. This scene simulated fine when I turned on Fluid Motion and increased the sampling. I then took this same scene and added thinking particles to it. All I did was had the particles spawning from the plane and then set the tp system as the source and velocity for a new stoke object. When I simulated with the normal settings it seemed to go fine. When I turned on use fluid motion it immediately crashed to desktop. So it would seem that there is a bug with TP in general as I was not using any FUME FX or other type of 3rd party plugins (besides Thinking Particles).
I have attached the two scenes for your perusal. I hope this helps.
-Christian
scenes.7z (21.1 KB)
Thanks for the files!
I opened your scene in 3ds Max 2013 64 bit running TP 5.0.0.48 and got no errors or crashes. It simulated correctly with and without “Create Fluid Motion” checked.
Then I loaded the same scene in 3ds Max 2012 64 bit running TP 4.0.7.2 and there were no errors either.
That being said, I don’t have TP 5.1 and have not tested with it. I will see if the Stoke lead developer could load that scene - I believe he has TP 5.1 on his machine…
Am I correct in my assumption that you are running TP 5.1?
no, I am running max 2012 x64 with TP 5.0.0.48. 
Maybe it has something to do with my max configuration. I will see what I can do to strip all the plugins away temporarily to see if it fixes the issue. BTW the Stoke version is 1.0.0.51286.
-Christian
I did another test with Max 2012 and max 2013 x64. I loaded a prt with a bin file sequence of a realflow simulation. In both cases it crashed when I checked the use fluid motion button. In the case of Max 2013; its pretty much a fresh install as I don’t have alot of plugins for it yet.
I am going to try this on a different computer next that’s not the HPs that we run here to see if there is any difference with that.
-Christian
It looks like this has something to do with the HP machines. I tried all the test scenes that I sent you on a different machine and they all totally worked fine with no crashes. So at least I got it working.
-Christian
YAY! that it works on others, and that it does not work on the HP. Not sure what the cause could be though…