Does Krakatoa recognize the current cache in Fume2 (Default, Wavelet, Post) when you select the Fume volume? If not, is there a way to select the proper .fxd sequence on the drive rather than selecting the volume in the scene?
Also, I’m getting a Path Error if I try to render (or save particles) from the Fume itself. I’m having to go through PFlow with a Fume Birth in order to export the PRT files.
Thanks~
~tsp
P.S. I just thought of potentially pointing the default Fume cache to the Post-Processed one. If, in fact, Krakatoa isn’t recognizing the current active Fume cache. I’ll let you know how it goes.
[size=200]KRAKATOA 1.5.X DOES NOT SUPPORT FUME FX 2.[/size]
FumeFX 2.0 is a different plugin and Krakatoa was built with the SDK of FumeFX 1.2. It did not work with 1.1 or 1.0 and it does not work with 2.0. We don’t read the Fume cache, we talk to Fume directly via its own functions and Fume reads the cache data and returns the values we need. So it is not a matter of us not knowing how to read the new cache, but a DLL difference like when Max changes the SDK and all plugins need an update.
Same applies to various builds of TP 4 - we use a specific version of the SDK and when the original developer changes the SDK, it breaks Krakatoa. This is to be expected and we are sorry for the inconvenience, but it is not under our control (we were not involved in the Beta of FumeFX 2 and just learned last week it even existed).
Krakatoa 1.6.0 will most probably support FumeFX 2.
Not sure if we can do anything about it in the mean time.
