Hi
Was wondering if there is any plan in near future for Fume 2 support on krakatoa.
I think you would need to internally find the version of Fume and have 2 different syntax in some of the code. Some of the functions on Fume2 are slightly different to Fume1 due to the more cache options (default , wavelet , retimer).
FumeFX 1:
$FumeFX01.getPath()
FumeFX 2:
$FumeFX01.getPath “default”
it seems right now that is the major incompatibility with Krakatoa.
We had the same problem with our internal pipeline for fume since we have a lot of automation and we were using both version at the same time. so we had to split the code in 2 and detect the version
We have an organizational problem right now.
We are finishing a show (same one as you ) that depends on FumeFX 1.2, so we cannot update our pipeline to 2.0 right now.
We got the 2.0 licenses purchased, but will have to find a way to develop and test outside of our plugin syncing system.
It is on our list of things to do for v1.6.0, but we could get in trouble if we would break the existing pipeline just weeks before the end of a project.
We have requested a node-locked license to work on this.
We cannot update our floating licenses without affecting our existing pipeline, so our hands a tied.
Krakatoa 1.6 works with the same version of FumeFX that Krakatoa 1.5 worked with.
Stay tuned…
We added support for FumeFX 2.0 yesterday and it looks great (wavelets and all).
We also separated the Emission channel from the Density influence and provided a separate Emission Strength control so now it is possible to control Smoke and Fire independently. In other words, the Density can now be reduced independently without affecting the strength of the Emission populated from the Fire channel.
) that depends on FumeFX 1.2, so we cannot update our pipeline to 2.0 right now.
most applicable