tyFlow v2.001
#1
tyFlow v2.001 is up!

https://pro.tyflow.com

Additions:

* added options to customize location to load CUDA modules from in tyFlow GPU rollout
* added new box size modes to tyIcon helper

Fixes:

* fixed an issue that could cause tyDiffusion to leak memory after opening, eventually filling up system RAM completely
* fixed an issue that could cause Max 2025 to crash during startup when VRay 6 is installed
* fixed an issue where 2XXX/3XXX GPUs would not run Inferno simulations
* Inferno Recall operator will now warn users if their GPU is not compatible with compression requirement (compute capability 7.0+ required)
* fixed an issue where Inferno Recall operator was not showing warning if required DLLs not found
* added checkbox option to not display C++ redistributable version warning again, if a problem version is detected on your machine
* fixed an issue where the tyMaterial modifier would always generate a multi-sub material with at least 100 submaterials, regardless of what the specific max unique ID range was
* Inferno Emitter operator can now emit negative temperature values
* fixed an issue where the Inferno Export operator wouldn't export temperature in some situations
* fixed some editor drawing issues related to windows DPI scaling
* fixed a regression where VRay render/IPR could crash in certain versions of Max when multiple versions of VRay exist on the machine
* fixed an issue where Inferno velocity streamlines would not be displayed for active solver frames
* improved behavior of middle-click spinner value stepper popup
* fixed an issue that could cause the Export Inferno operator to crash when exporting an upres'd sim
  Reply
#2
Is it possible to select open vdb build versions when exporting vdb caches? Noticed not everything is supporting v13 yet.

Is there also a way to compress the vdb when exporting?
  Reply
#3
VDB is already internally compressed. Perhaps not to the theoretical Max, but we use BLOSC compression which is the fastest of the format.

What software was having trouble opening the v13 VDBs?
  Reply
#4
(03-10-2026, 03:32 PM)tyFlow Wrote: VDB is already internally compressed. Perhaps not to the theoretical Max, but we use BLOSC compression which is the fastest of the format.

What software was having trouble opening the v13 VDBs?

I was trying to test them in houdini / karma.
  Reply
#5
Is it not loading them? Or just showing a warning?

VDB import to Houdini from Inferno works fine over here - note that I'm using the latest version of Houdini.
  Reply


Forum Jump: