So buzz format, what is up with it? All I know is it is a fields format, I guess what was once naiad uses(d) it, another plugin in my beta list is adopting it. Does Ember play with it too?
Just some info on the format and maybe some specifics I guess.
Field3D was one of the formats that had support announced.
viewtopic.php?f=148&t=7854&p=32611&hilit=field3d#p32611
sites.google.com/site/field3d/
We have not implemented support for it yet, and it might not even happen in v1.0 depending on many factors.
Highest priority on the format front is supporting FXD in both directions (reading works, saving to be done).
Also, Dreamworks just announced their own file format and toolset similar to Ember: openvdb.org/
Depending on the industry adoption of these formats, we might adjust our plans as time passes…
Aye ok, I was trying to get a heads up to see if it is something I should invest some time into learning or wait and work on other things. I think I’ll get the brief of it.
It is good to see studios releasing more open formats, yet though now deciding which ones to support, gees.
Looks cool though and something of which I don’t know about other formats, although I suspect Kreso is working on something like this but:
Looks real useful. like 2.1+ billion units in any direction from point 0!
is .fxd an open format?
Not that I am aware of. I am pretty sure you need to have the Fume SDK to get at it.
Does the Fume SDK depend on 3ds max?
No idea, Darcy/Bobo would/should know. SDK is too far into the Dark side for me to be getting into atm, I haven’t got that kinda time.
Its not Max specific, everything to save/load fume data is contained in VoxelFlow.dll which is included with FumeFX, but is not the actual 3ds Max plugin.
Naiad doesn’t have Field3D support… you have to save out bgeo to Houdini and export Field3D from there in order to read it into other plugins/programs that support it.
Hey thanks for the clarification Tobbe, I wasn’t sure, I had heard that somewhere but nothing specific in relation to naiad.