jsmack
Did you try creating a package? That's the best way to associate a plugin with a specific version of Houdini.
axiom.json
{
"enable": false,
"path": "C:/USERS/PUBLIC/DOCUME~1/Axiom/${HOUDINI_VERSION}"
}
Hey Jonathan,
off topic package syntax question here: Can you elaborate the naming you just put in there with the “~1”? Does that evaluate into the first matching folder with “DOCUME” like tabbing in the shell on a linux machine? I was curious as the Houdini textport evaluates paths similarly.
Just ever confused using windows and having unix syntax in some places for Houdini.
Midphase
How does it compare to EmberGen?
https://jangafx.com/software/embergen/ [jangafx.com]
On that account, I believe the new 18.5 minimal solver (using a newer, more efficient version of VDBs) is similar, but Axiom is more production capable with the sparsity and ability to switch with the same algorythms, as the new minimal solver does not support that (yet).
Also with the Houdini minimal solver, I've experienced the promised switch from GPU to CPU NOT to be without change, so it does not match exactly, which is a shame - but I might be wrong. Concerning that, does anyone have experience with Axiom switching for final highres export?