Added support for tyFlow volumes (Inferno).
Available from Octane plugin version 26.8
(for tyFlow PRO version 2.007 or higher)
Octane can render tyFlow volume direcly, without the need to export as VDB.
A new modifier "OctVolumeTyFlow (WSM)" should be used to control the Octane grid settings and medium.
When a OctVolumeTyFlow modifier is added to a tyFlow object, a Standard volume is automatically created, with default settings
Note that when there is no OctVolumeTyFlow modifier, an internal default Standard volume is used.
Note: The LocalDB Directory in Octane Preferences / Material should be set to a valid existing directory.
Basic usage steps:
New scene
Set Octane as renderer
Create a teapot
Create a tyFlow object
Open Editor (tyFlow)
Add a Birth Inferno
Select Interno Emitter
Pick button : select the teapot
Close tyFlow editor
Move the timeline to frame 100 (to let tyFlow do the simulation now)
go to frame 50
Open Octane viewport
Check that the render match approximately the display in the 3dsMax viewport.
Close Octane viewport
Select the tyFlow object
Add a OctVolumeTyFlow modifier.
Open Material Editor
drag the medium from the modifier to the Material editor (Instance)
Open Octane viewport
The render should be the same as without modifier
Adjustments can now be made to improve the result.
----- tyFlow volume channels
tyFlow can generate the folowing volume channels:
temperature (single float value)
density (single float value)
color (3 float values, for r,g,b)
fuel (single float value)
velocity (3 float values, for x,y,z velocities)
2 additional channels are made available to the Octane OctVolumeTyFlow modifier, that are based on the temperature channel:
temperature color ('temperColor')
temperature opacity ('temperOpacity')
Depending on the tyFlow simulation settings (tyFlow node editor), those channels may or may not be enabled, or may contain empty values or same value for all voxels.
The values may be in a range that match what Octane expect ('Normalized') (usually in the [0,1] range), but may also be much larger or smaller.
In most cases, it might be more easy to adjust the Octane medium settings with normalized values.
The OctVolumeTyFlow modifier provide a way to remap each channel to a range better fit for Octane medium.
That is especially usefull for the Temperature Color channel, that can have RGB values much higher that 1.0.
----- Assigning tyFlow channels to Octane channels ------
The Octane Volume object (that is used internally for the tyFlow Inferno object) has several default channels that are used by the Octane medium.
Those are Absorption, Emission, Scatter and Velocity. There are scale values for each of those channels.
Those are used by legacy medium types, like Absorption, Random walk, Scattering, Volume medium.
But the new medium 'Std Volume medium' (recommended for tyFlow Inferno) do not use those channel in a fixed way, and will instead just make the selected channels available for it's various settings
(Density, Scatter, Transparency, Emission, Temperature)
The Std Volume medium also ignore the scales set in the modifier, and use the 'weight' parameters of the medium instead.
To use other tyFlow channels, there are additional 5 extra channels that can be used and make those tyFlow channels available to the Std Volume medium.
The typical use case is to set the tyFlow 'color' channel to the extra channel 1,
the tyFlow 'temperColor' channel to the extra channel 2,
and the tyFlow 'temperOpacity' channel to the extra channel 3, and use the usual channel settings for the others
(tyflow density, temperature, velocity to Octane Absorption, Emission, velocity)
Channel remapping
The first step is to read the values generated by tyFlow.
In the OctVolumeTyFlow modifier, enable 'Collect Min/Max values'
Then, open the Octane viewport to start rendering.
That will display the min and max values of each channel for the current frame in the modifier text box.
For example,
density -> Absorption [0.000, 1.000] shows that the tyFlow 'density' channel is assigned to the Octane 'Absorption' channel, and the values and in the range [0,1].
This channel do not need to be remapped.
temperature -> Emission [0.000, 5.500] shows that the tyFlow 'temperature' channel is assigned to the Octane 'Emission' channel, and the values and in the range [0, 5.5].
This channel should be remapped.
temperColor -> ExtraCh1 (0.00, 0.00, 0.00) - (15.00, 14.55, 14.78)
This channel should be remapped.
Use the 'Channel remapping' section and select one channel to edit.
Enable 'Remap channel'
Set Old Min and Old Max to the tyFlow values (eg Old Min:0, Old Max:15.00) and
Set New Min and New Max to the desired Octane values (eg New Min:0, New Max:1.00)
Once the remap is set, the 'Collect Min/Max values' can be disabled for better performance.
--- Other mediums
The other Octane mediums can be used (Absorption, Random walk, Scattering, Volume medium),
but the color channels won't be available.
----- Other settings
The OctVolumeTyFlow modifier has a Voxel size setting.
It is calculated by default using tyFlow settings and the System Unit.
It is possible to overwrite the voxel size by using the 'Custom Voxel size' checkbox.
When disabled, the current default value is displayed.
When enabled, any value can be set.
This will affect the how the Density and Volume step values are applied, and could be used to adjust the general density if some artifact are visible.
----- Known issues ----
When Octane viewport is open and rendering is in progress, and tyflow need to re-calculate the simulation, the simulation calculation can become very slow.
In this case, it is better to cancel the simulation and close Octane viewport. Move the time slider to the last frame to let tyFlow calculate all the frames, then re-open Octane viewport.
When Octane viewport is open, changing some settings in the tyFlow editor may not be detected. (eg changing the display preset from Classic to CoolMagic)
For those cases, use the Rebuild button in Octane viewport.
The current System Units influence how the result will look.
Some artifacts (blocks) may appear with 1 unit set to large values, like 1 Km.
Some tyFlow feature are not fully supported and may result in incorrect render.
For example, the Upres feature of the Inferno Recall operator produce incorrect position and size of the volume.
tyFlow object Inactive.
When loading a scene, the Birth Inferno operator of the tyFlow object may sometimes become inactive.
If that happens, just click on the Inactive buton to activate it.
This seems to be an issue with tyFlow, not related to Octane plugin.
3dsMax will crash when trying to render with Octane and tyFlow version lower than 2.007.
--- Samples ----
Inferno_Fire_classic_01_noModifier.max
This is a simple fire created with tyFlow default settings, and no Octane setting or modifier.
Inferno_Fire_classic_02.max
Same as previous sample, but with the Octane OctVolumeTyFlow modifier.
The channels 'temperature' and 'temperColor' have been remapped to the [0,1] range
In the Std Volume medium (Map #12), the Emission color has been set to a light orange, that is multiplied with the temperColor channel
Inferno_Fire_CoolMagic_01_noModifier.max
This illustrate the tyFlow Fire color in the Inferno Display operator. The preset 'Cool Magic' has been selected.
Inferno_Fire_CoolMagic_02.max
Same as previous sample, but with the Octane OctVolumeTyFlow modifier.
The modifier and the medium have been adjusted to match the tyFlow viewport display.
Inferno_MultiColors_01.max
The first Inferno Emitter operator was setup with a color emission set to blue.
A second Inferno Emitter operator was added, with a color emission set to yellow.
Those colors are accessible to Octane via the 'color' channel, and is set in the Scatter color channel of the Std Volume medium
Inferno_MultiColors_02.max
An Inferno Color operator was added, and uses a color gradient from blue to green.
Those colors are accessible to Octane via the 'color' channel, and is set in the Scatter color channel of the Std Volume medium
inferno_velocity01.max
This uses the velocity with a scale of 200
The Octane object property for tyFlow001 has Object motion blur enabled, and the Render settings/Camera has Motion Blur enabled.
Adjust the shutter time to see the effect of the motion blur.
Support for tyFlow volumes (Inferno)
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Hi NZ ! Thank you very much for this release !
First, you make a really good job to implement Inferno in octane, it works, it is straightforward !
I have some question because I'm a noob with vdbs : I tried to use medium created by OctVolumeTyFlow modifier to a vdb exported from my Tyflow inferno simulation, and I'm not able to see Density , just temperature...
Any idea ?
I tried a very detailled Tyflow Inferno ( I mean very low Voxel size in Tyflow ) : Memory size exploded
( need a good balance between voxel size in tyflow sim and voxel size in Octane )
Could it be possible to have a command menu to hard kill octane viewport, because sometimes it is impossible and I need to hard kill max...
Best regards.
[EDIT : you seriously made sample files in millimeters ? ]
First, you make a really good job to implement Inferno in octane, it works, it is straightforward !
I have some question because I'm a noob with vdbs : I tried to use medium created by OctVolumeTyFlow modifier to a vdb exported from my Tyflow inferno simulation, and I'm not able to see Density , just temperature...
Any idea ?
I tried a very detailled Tyflow Inferno ( I mean very low Voxel size in Tyflow ) : Memory size exploded
Could it be possible to have a command menu to hard kill octane viewport, because sometimes it is impossible and I need to hard kill max...
Best regards.
[EDIT : you seriously made sample files in millimeters ? ]
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
- neonZorglub

- Posts: 1097
- Joined: Sun Jul 31, 2016 10:08 pm
Hi HHbomb,HHbomb wrote: Thu Jun 11, 2026 9:18 am Hi NZ ! Thank you very much for this release !
First, you make a really good job to implement Inferno in octane, it works, it is straightforward !
I have some question because I'm a noob with vdbs : I tried to use medium created by OctVolumeTyFlow modifier to a vdb exported from my Tyflow inferno simulation, and I'm not able to see Density , just temperature...
Any idea ?
VDBno density.jpg
I tried a very detailled Tyflow Inferno ( I mean very low Voxel size in Tyflow ) : Memory size exploded( need a good balance between voxel size in tyflow sim and voxel size in Octane )
memory1.jpg
Could it be possible to have a command menu to hard kill octane viewport, because sometimes it is impossible and I need to hard kill max...![]()
Best regards.
[EDIT : you seriously made sample files in millimeters ? ]
Thank you ! Glad to hear that the inferno usage is straightforward !
The default medium created for the OctVolumeTyFlow uses the special channels temperColor and temperOpacity
but those 2 channels are not available in the exported VDBs..
So you need to replace temperOpacity by density in the Transparency section, and the temperColor by density for example, in the Emission section.
The 'color' channel should work and could be used to display the fire color I think, but you'll need to setup the Inferno nodes for that..
If you need a typical flame / fire, you could use a Volume medium instead of the Std. Volume medium, and setup the colors with a volume ramp. That would work for inferno and VDBs
Here is a sample with both an tyFlow Inferno object and the corresponding exported animated VDBs in an Octane volume object: The killing of the octane viewport is not easily possible unfortunately.. but one of the reason it can be stuck in calculation is a too low Volume step..
While experimenting, make sure it's in the 50~200+ % area.. and set your sample per pixel to very low, like 50 spp..
For the memory usage, big grid takes big memory.. see if you can disable the tyFlow cache, this might help..
Thanks
- neonZorglub

- Posts: 1097
- Joined: Sun Jul 31, 2016 10:08 pm
------------------------- Update from Octane plugin 26.9 -----------------
----- GPU VRAM -----
By default, tyFlow will use as much VRAM as available to cache the simulation frames.
This can conflict with Octane and result in a CUDA out of memory error, that prevent octane to render the scene.
The simplest way to avoid this issue is to use at least 2 GPUs, and select one exclusively for tyFlow, and one for octane.
To select the GPUs to assign, see the tyFlow 'GPU' panel, and the Octane Device tab in Render settings.
For machines with a single GPU, you may need to deactivate the 'playback cache' in tyFlow 'Cache' panel.
The Render settings / Device / Octane device settings opens the Octane device dialog that shows detail of the memory usage.
The VRAM used by tyFlow will appear as 'Unavailable'.
Another workflow is to export the tyFlow simulation as VDB files.
----- VDB files -----
Currently, Octane creates 2 additional channels from the tyFlow data, to use the temperature color and temperature opacity in a simple way with Octane modifier and mediums.
Those channels are selectable in Octane with the names 'temperColor' and 'temperOpacity'.
Note that those are simply calculated by tyFlow based on the temperature channel.
The addition of 'temperColor' and 'temperOpacity' as extra channels is not an ideal solution as this uses additional memory, but is the only way to use it with Octane.
However, when exporting tyFlow volume as VDBs from the tyFlow editor, those channels are not exported.
To render tyFlow volumes as VDBs in the same way as the tyFlow objects, a new option has been added to export tyFlow VDBs with all the transformations and additions used for Octane.
------ tyFlow VDB export from Octane ------
The OctVolumeTyFlow modifier read the tyFlow data, and perform those optional transformations:
-Remapping
When enabled, that re-calculate each cell value of a channel for better fit with Octane. (for example rgb values from the [0,22] range to [0,1] range)
-Additional channels
When assigned to one of the octane channels, 'temperColor' and 'temperOpacity' are created based on the temperature channel and the current tyFlow conversion setup.
The resulting volume is used to render with Octane, and can now be exported as VDB.
This allows to create an Octane Volume object that will use the same medium as the tyFlow object.
The 'tyFlow VDBs' section in the Render settings / Tools / Octane export tabs has the following items:
'Export VDBs' button:
This will export a range of VDBs for the selected tyFlow object.
It uses the Start/End frame as set for Octane export.
It uses the path and base orbx name, as well as the tyFlow object name to create a sub folder in the export location
For example, if 'Export as' is set to 'myScene.orbx', and the selected tyFlow object is 'tyFlow001', a sub folder 'myScene_TOV_tyFlow001' will be created.
It will contain TOV_tyFlow001_1.vdb, TOV_tyFlow001_2.vdb, etc..
Note that the TOV suffix (Tyflow Octane Volume) is added to avoid confusion with VDBs exported by tyFlow.
'Fetch last frame' checkbox:
This forces tyFlow to calculate the simulation until the last frame, and store the result in tyFlow's cache.
This improves the export performance.
It should be disabled if the tyFlow 'playback cache' is disabled.
'Explore VDBs' button:
Opens Windows explorer at the VDB's location.
A status text shows the export progress or selection status.
Notes:
While the export is in progress, the 'Export VDBs' is changed to 'Cancel export'.
The user interface is less responsive than usual, so allow a few seconds after pressing 'Cancel export'.
Also, the dialog should not be closed, and any other actions should be avoided.
Regardless of the start frame number, the VDB files will be named xxx_1, xxx_2, ...
----- Orbx export -----
Scenes with an active tyFlow object can be exported with animation.
The resulting orbx file can be used with an Octane 'Orbx Proxy' object.
Note that the orbx file will contain all the VDBs, so the size will be large.
As the temporary VDBs used for export are usable for Octane Volume objects, an option 'Keep generated VDBs' is available in the Export settings tab.
When disabled (default), the temporary VDBs will be deleted.
When enabled, those VDBs should be equivalent as those exported by the 'Export VDBs' button.
----- GPU VRAM -----
By default, tyFlow will use as much VRAM as available to cache the simulation frames.
This can conflict with Octane and result in a CUDA out of memory error, that prevent octane to render the scene.
The simplest way to avoid this issue is to use at least 2 GPUs, and select one exclusively for tyFlow, and one for octane.
To select the GPUs to assign, see the tyFlow 'GPU' panel, and the Octane Device tab in Render settings.
For machines with a single GPU, you may need to deactivate the 'playback cache' in tyFlow 'Cache' panel.
The Render settings / Device / Octane device settings opens the Octane device dialog that shows detail of the memory usage.
The VRAM used by tyFlow will appear as 'Unavailable'.
Another workflow is to export the tyFlow simulation as VDB files.
----- VDB files -----
Currently, Octane creates 2 additional channels from the tyFlow data, to use the temperature color and temperature opacity in a simple way with Octane modifier and mediums.
Those channels are selectable in Octane with the names 'temperColor' and 'temperOpacity'.
Note that those are simply calculated by tyFlow based on the temperature channel.
The addition of 'temperColor' and 'temperOpacity' as extra channels is not an ideal solution as this uses additional memory, but is the only way to use it with Octane.
However, when exporting tyFlow volume as VDBs from the tyFlow editor, those channels are not exported.
To render tyFlow volumes as VDBs in the same way as the tyFlow objects, a new option has been added to export tyFlow VDBs with all the transformations and additions used for Octane.
------ tyFlow VDB export from Octane ------
The OctVolumeTyFlow modifier read the tyFlow data, and perform those optional transformations:
-Remapping
When enabled, that re-calculate each cell value of a channel for better fit with Octane. (for example rgb values from the [0,22] range to [0,1] range)
-Additional channels
When assigned to one of the octane channels, 'temperColor' and 'temperOpacity' are created based on the temperature channel and the current tyFlow conversion setup.
The resulting volume is used to render with Octane, and can now be exported as VDB.
This allows to create an Octane Volume object that will use the same medium as the tyFlow object.
The 'tyFlow VDBs' section in the Render settings / Tools / Octane export tabs has the following items:
'Export VDBs' button:
This will export a range of VDBs for the selected tyFlow object.
It uses the Start/End frame as set for Octane export.
It uses the path and base orbx name, as well as the tyFlow object name to create a sub folder in the export location
For example, if 'Export as' is set to 'myScene.orbx', and the selected tyFlow object is 'tyFlow001', a sub folder 'myScene_TOV_tyFlow001' will be created.
It will contain TOV_tyFlow001_1.vdb, TOV_tyFlow001_2.vdb, etc..
Note that the TOV suffix (Tyflow Octane Volume) is added to avoid confusion with VDBs exported by tyFlow.
'Fetch last frame' checkbox:
This forces tyFlow to calculate the simulation until the last frame, and store the result in tyFlow's cache.
This improves the export performance.
It should be disabled if the tyFlow 'playback cache' is disabled.
'Explore VDBs' button:
Opens Windows explorer at the VDB's location.
A status text shows the export progress or selection status.
Notes:
While the export is in progress, the 'Export VDBs' is changed to 'Cancel export'.
The user interface is less responsive than usual, so allow a few seconds after pressing 'Cancel export'.
Also, the dialog should not be closed, and any other actions should be avoided.
Regardless of the start frame number, the VDB files will be named xxx_1, xxx_2, ...
----- Orbx export -----
Scenes with an active tyFlow object can be exported with animation.
The resulting orbx file can be used with an Octane 'Orbx Proxy' object.
Note that the orbx file will contain all the VDBs, so the size will be large.
As the temporary VDBs used for export are usable for Octane Volume objects, an option 'Keep generated VDBs' is available in the Export settings tab.
When disabled (default), the temporary VDBs will be deleted.
When enabled, those VDBs should be equivalent as those exported by the 'Export VDBs' button.
