https://forum.tyflow.com/ Fri, 06 Nov 2026 21:15:35 +0000 MyBB https://forum.tyflow.com/thread-5285.html Fri, 06 Nov 2026 07:13:31 -0800 Fabrice]]> https://forum.tyflow.com/thread-5285.html I created some smoke in a room and I wand some wind to come through an open window.
I tried to use a 'Inferno Force' node but I cant add any of the Max 2027  standard forces like 'wind' or 'Turbulence', Inferno wont pich it up.

How to achieve that then please?]]> I created some smoke in a room and I wand some wind to come through an open window.
I tried to use a 'Inferno Force' node but I cant add any of the Max 2027  standard forces like 'wind' or 'Turbulence', Inferno wont pich it up.

How to achieve that then please?]]> https://forum.tyflow.com/thread-5284.html Mon, 02 Nov 2026 21:52:50 -0800 jcjworks]]> https://forum.tyflow.com/thread-5284.html
  indep.mp4 (Size: 35.3 MB / Downloads: 11) ]]>
  indep.mp4 (Size: 35.3 MB / Downloads: 11) ]]> https://forum.tyflow.com/thread-5283.html Fri, 23 Oct 2026 15:22:11 -0700 Findus]]> https://forum.tyflow.com/thread-5283.html Maybe tyFlow could offer a secondary route to ensure UV Data is preserved and retrieved where it's needed, be it from an external file or internally saved.

Edit: Turns out, pasted UVs from the channel info tool are comparably stable in the modifier stack, wasn't aware of that.]]> Maybe tyFlow could offer a secondary route to ensure UV Data is preserved and retrieved where it's needed, be it from an external file or internally saved.

Edit: Turns out, pasted UVs from the channel info tool are comparably stable in the modifier stack, wasn't aware of that.]]> https://forum.tyflow.com/thread-5282.html Fri, 23 Oct 2026 15:14:04 -0700 Findus]]> https://forum.tyflow.com/thread-5282.html
As per the thread subject, it might be handy at times to create and retrieve named sub selections parametrically, maybe even compatible with 3ds max's own named selection sets. This way, multiple complex selections could be passed higher up the stack despite interruptions or prepared in the base object.
This could probably done with vertex colors as well, but selection sets would be much easier.

Thanks for reading!]]>
As per the thread subject, it might be handy at times to create and retrieve named sub selections parametrically, maybe even compatible with 3ds max's own named selection sets. This way, multiple complex selections could be passed higher up the stack despite interruptions or prepared in the base object.
This could probably done with vertex colors as well, but selection sets would be much easier.

Thanks for reading!]]> https://forum.tyflow.com/thread-5281.html Fri, 23 Oct 2026 15:08:13 -0700 japetus]]> https://forum.tyflow.com/thread-5281.html https://forum.tyflow.com/thread-5280.html Thu, 22 Oct 2026 08:30:05 -0700 mike-6435]]> https://forum.tyflow.com/thread-5280.html
I would like to link rotating beacons that spin continuously to a Tyvehicle 
I tried the tyParticleController, but I can't get the rotating beacons to rotate.
Do you have any ideas that don't require exporting the geometry?

Thanks a lot
Regards
Mike]]>
I would like to link rotating beacons that spin continuously to a Tyvehicle 
I tried the tyParticleController, but I can't get the rotating beacons to rotate.
Do you have any ideas that don't require exporting the geometry?

Thanks a lot
Regards
Mike]]> https://forum.tyflow.com/thread-5279.html Thu, 22 Oct 2026 03:12:07 -0700 ldotchopz]]> https://forum.tyflow.com/thread-5279.html
Cheers]]>
Cheers]]> https://forum.tyflow.com/thread-5278.html Wed, 21 Oct 2026 06:11:13 -0700 307896794]]> https://forum.tyflow.com/thread-5278.html I am a licensed tyFlow user and I am reporting a critical, reproducible crash bug.
Version information: tyFlow version: v2.100 3ds Max version: 3ds Max 2026 GPU: RTX 4060Ti 8GB Graphics Driver: NVIDIA Studio Driver
Bug description: Whether I work in an existing scene with geometry, OR a brand-new blank empty scene with NO objects at all in the viewport, adding and enabling the Shape operator inside a tyFlow event will immediately trigger an Application Error and force 3ds Max 2026 to close/crash.
This crash is 100% reproducible. It is not an intermittent error caused by scene geometry, collision meshes or resource overload. I have already troubleshooted my workstation environment thoroughly: removed redundant CUDA developer packages, clean-reinstalled NVIDIA Studio graphics drivers, tested multiple brand-new empty Max files, and the crash still happens consistently.
The Shape operator is essential for my workflow of cloth simulation, sheet/paper dynamics and mechanical particle animation. This bug completely blocks my production work, I cannot continue my projects when this operator crashes the host application.
Screenshot is attached: it shows the crash popup window, tyFlow editor UI and the application error message.
Could you please investigate the Shape operator code in this release as soon as possible? Please let me know the progress of the fix, or any temporary workaround if available.
Thank you for your support.
Best regards, Date: 2026-10-21

  003.png (Size: 315.59 KB / Downloads: 35)

  004.png (Size: 840.54 KB / Downloads: 38) ]]> I am a licensed tyFlow user and I am reporting a critical, reproducible crash bug.
Version information: tyFlow version: v2.100 3ds Max version: 3ds Max 2026 GPU: RTX 4060Ti 8GB Graphics Driver: NVIDIA Studio Driver
Bug description: Whether I work in an existing scene with geometry, OR a brand-new blank empty scene with NO objects at all in the viewport, adding and enabling the Shape operator inside a tyFlow event will immediately trigger an Application Error and force 3ds Max 2026 to close/crash.
This crash is 100% reproducible. It is not an intermittent error caused by scene geometry, collision meshes or resource overload. I have already troubleshooted my workstation environment thoroughly: removed redundant CUDA developer packages, clean-reinstalled NVIDIA Studio graphics drivers, tested multiple brand-new empty Max files, and the crash still happens consistently.
The Shape operator is essential for my workflow of cloth simulation, sheet/paper dynamics and mechanical particle animation. This bug completely blocks my production work, I cannot continue my projects when this operator crashes the host application.
Screenshot is attached: it shows the crash popup window, tyFlow editor UI and the application error message.
Could you please investigate the Shape operator code in this release as soon as possible? Please let me know the progress of the fix, or any temporary workaround if available.
Thank you for your support.
Best regards, Date: 2026-10-21

  003.png (Size: 315.59 KB / Downloads: 35)

  004.png (Size: 840.54 KB / Downloads: 38) ]]> https://forum.tyflow.com/thread-5277.html Mon, 19 Oct 2026 02:28:13 -0700 Mahiro]]> https://forum.tyflow.com/thread-5277.html 3ds Max version: 2026

I can execute an Inferno VDB export with MAXScript using:

(getNodeByName "tyFlow001").Event_001.Inferno_Export.exportVDB()

Steps to reproduce:

1. Create a tyFlow object with a Birth Inferno operator and an Inferno Export operator.
2. Configure the Inferno Export operator so that exporting from its UI works correctly.
3. Select the Inferno Export operator in the tyFlow editor.
4. Execute the MAXScript command above. The VDB export works correctly.
5. Select another operator, or reopen the .max file so that no operator is selected.
6. Execute the same MAXScript command again.

Result:

3ds Max reports an EXCEPTION_ACCESS_VIOLATION inside tyFlow_2026.

The operator selection is not restored after reopening the .max file, and I cannot find a MAXScript method for selecting an operator.

Is exportVDB() intended to work without the Inferno Export operator being selected?

Is there a supported way to execute Inferno VDB exports from Deadline, the command line, or another automated process?]]> 3ds Max version: 2026

I can execute an Inferno VDB export with MAXScript using:

(getNodeByName "tyFlow001").Event_001.Inferno_Export.exportVDB()

Steps to reproduce:

1. Create a tyFlow object with a Birth Inferno operator and an Inferno Export operator.
2. Configure the Inferno Export operator so that exporting from its UI works correctly.
3. Select the Inferno Export operator in the tyFlow editor.
4. Execute the MAXScript command above. The VDB export works correctly.
5. Select another operator, or reopen the .max file so that no operator is selected.
6. Execute the same MAXScript command again.

Result:

3ds Max reports an EXCEPTION_ACCESS_VIOLATION inside tyFlow_2026.

The operator selection is not restored after reopening the .max file, and I cannot find a MAXScript method for selecting an operator.

Is exportVDB() intended to work without the Inferno Export operator being selected?

Is there a supported way to execute Inferno VDB exports from Deadline, the command line, or another automated process?]]> https://forum.tyflow.com/thread-5276.html Thu, 15 Oct 2026 12:49:28 -0700 Martin Kossmann]]> https://forum.tyflow.com/thread-5276.html Max 2024 and latest tyflow.

  tyflowCrashWithForceInForceOp.max (Size: 496 KB / Downloads: 36) ]]> Max 2024 and latest tyflow.

  tyflowCrashWithForceInForceOp.max (Size: 496 KB / Downloads: 36) ]]> https://forum.tyflow.com/thread-5275.html Wed, 14 Oct 2026 13:23:23 -0700 rjanders0003]]> https://forum.tyflow.com/thread-5275.html
So I am back, I think !! - Life got in the way (Bought a house, Moved, Sold a House, Renovating a house)  It just didn't give me time to create tutorials or be on a computer.

I am slowly breaking down all the tyVehicle stuff, so I can fully understand it.  

I have posted two intro tutorials on my Udemy Course (tyFlow The Missing Manual), they are the very basics at this time.  

Much more on tyVehicle coming (Section 25 of the course), I hope to make it very comprehensive information, but it will take time to create, caption, translate and upload videos.

I also plan to add some free stuff to my You Tube Channel,  but it will be after I have at least 5 or 6 videos on my Udemy course.

So thats the news for now !! (stuff coming)

Regards
  Rob]]>
So I am back, I think !! - Life got in the way (Bought a house, Moved, Sold a House, Renovating a house)  It just didn't give me time to create tutorials or be on a computer.

I am slowly breaking down all the tyVehicle stuff, so I can fully understand it.  

I have posted two intro tutorials on my Udemy Course (tyFlow The Missing Manual), they are the very basics at this time.  

Much more on tyVehicle coming (Section 25 of the course), I hope to make it very comprehensive information, but it will take time to create, caption, translate and upload videos.

I also plan to add some free stuff to my You Tube Channel,  but it will be after I have at least 5 or 6 videos on my Udemy course.

So thats the news for now !! (stuff coming)

Regards
  Rob]]> https://forum.tyflow.com/thread-5274.html Wed, 14 Oct 2026 00:27:26 -0700 nayan]]> https://forum.tyflow.com/thread-5274.html Its been a long time, Congrats on tyVehicle - wonderful vehicle system.
When I export cloth to tycache, tycache dont show me any cloth geometry, it shows me the points and animation, but no geometry at all

Thank you
Nayan Bodawala]]> Its been a long time, Congrats on tyVehicle - wonderful vehicle system.
When I export cloth to tycache, tycache dont show me any cloth geometry, it shows me the points and animation, but no geometry at all

Thank you
Nayan Bodawala]]> https://forum.tyflow.com/thread-5273.html Mon, 12 Oct 2026 15:21:50 -0700 Kev]]> https://forum.tyflow.com/thread-5273.html
Cheers.]]>
Cheers.]]> https://forum.tyflow.com/thread-5272.html Thu, 08 Oct 2026 06:26:23 -0700 jswedenhjelm]]> https://forum.tyflow.com/thread-5272.html
For vehicle treads can we get an additional mode for machines with a continuous track, like a rubber track? I can do a workaround by generating tysplines from the track rig and using a path deform to wrap my track mesh, but it would be cool if that functionality was built into the tread tool.]]>
For vehicle treads can we get an additional mode for machines with a continuous track, like a rubber track? I can do a workaround by generating tysplines from the track rig and using a path deform to wrap my track mesh, but it would be cool if that functionality was built into the tread tool.]]> https://forum.tyflow.com/thread-5271.html Thu, 08 Oct 2026 06:25:42 -0700 tyFlow]]> https://forum.tyflow.com/thread-5271.html
Additions:

* added soft-selection propagation controls to tySelect modifier - allowing you to soft-select entire triangles/polygons/elements instead of just vertices
* added enabledModifiersBelow function to tyCache modifier
* added inheritance options to tyParticleController (position/rotation/scale toggles)
* added "radius" as an option to all relative-to-property multiplier dropdowns (ex: in Value operator)
* added "radius" as a Value operator property
* added "offset" parameters to Terrain Scatter operator
* tyVehicle parts created with the helper wizards and presets will now be scaled to match user scene units (at time of creation)
* added midpoint parameter to Surface Force texture mode

Fixes:

* fixed an issue where recursive tyVehicle multi-wheel fitting could result in messed up suspension ranges
* fixed a regression that could cause cloth collision artifacts in a setup where cloth is moving but has no explicit velocity
* fixed an Inferno memory leak which could prevent emitter RAM cache from being cleared during simulation reset
* tyVAT export will now work even if modifier is disabled
* fixed an issue where creating 150+ tyFlow objects could cause Max to crash, due to GDI object consumption
* fixed an instability with Value operators in surface mode
* fixed an issue where simulations could reset when operator output connection selection changed
* fixed a race condition which could cause 3ds Max 2025 to crash during startup
* tyVehicle wheel helpers are now set to be driven by default
* fixed an issue where sorting helpers by name in a tyVehicle listbox would remove them all from the list
* fixed an issue where particles could not break their PhysX spline bind and then be rebound to a different spline
* fixed an issue which could cause PRISM operations to crash in some scenarios due to an incompatibility with AMTVoxelizer.dll (Max 2022-24)
* fixed an issue which could cause the Inferno Properties operator to crash in some scenarios
* fixed an issue with tySplineMesher extrusion mode face winding order (some splines would extrude with flipped faces if cap tessellation operation flipped spline winding order)
* fixed a regression where the less/greater than conditions of the Property Test were also equal-inclusive
* fixed an issue where inferno recall cache display would not properly display animated intersectors
* fixed an issue that prevented tyFlow from properly saving/loading animated RGBA values
* fixed an issue which prevented negative steering multipliers on tyVehicle wheel helpers from working properly
* fixed an issue where tyVehicle struts were not properly respecting the rest offset parameters of physical wheels
* fixed an issue where the Particle Bind operator's "weld connected cloth meshes" option could generate cloth mesh artifacts
* fixed an issue where tyTerrain Downloader would fail to download large color textures (larger than 13K x 13K pixels)
* fixed an issue where trying to connect multiple selected operators to the same input would only connect one of them
* fixed an issue where tyPush element push values could not be negative
* fixed an inconsistency with how the PhysX Vehicle operator computed differential velocities, which could affect skid particle generation (users may need to reduce slip/drag thresholds to generate the same number of skid particles as before)]]>
Additions:

* added soft-selection propagation controls to tySelect modifier - allowing you to soft-select entire triangles/polygons/elements instead of just vertices
* added enabledModifiersBelow function to tyCache modifier
* added inheritance options to tyParticleController (position/rotation/scale toggles)
* added "radius" as an option to all relative-to-property multiplier dropdowns (ex: in Value operator)
* added "radius" as a Value operator property
* added "offset" parameters to Terrain Scatter operator
* tyVehicle parts created with the helper wizards and presets will now be scaled to match user scene units (at time of creation)
* added midpoint parameter to Surface Force texture mode

Fixes:

* fixed an issue where recursive tyVehicle multi-wheel fitting could result in messed up suspension ranges
* fixed a regression that could cause cloth collision artifacts in a setup where cloth is moving but has no explicit velocity
* fixed an Inferno memory leak which could prevent emitter RAM cache from being cleared during simulation reset
* tyVAT export will now work even if modifier is disabled
* fixed an issue where creating 150+ tyFlow objects could cause Max to crash, due to GDI object consumption
* fixed an instability with Value operators in surface mode
* fixed an issue where simulations could reset when operator output connection selection changed
* fixed a race condition which could cause 3ds Max 2025 to crash during startup
* tyVehicle wheel helpers are now set to be driven by default
* fixed an issue where sorting helpers by name in a tyVehicle listbox would remove them all from the list
* fixed an issue where particles could not break their PhysX spline bind and then be rebound to a different spline
* fixed an issue which could cause PRISM operations to crash in some scenarios due to an incompatibility with AMTVoxelizer.dll (Max 2022-24)
* fixed an issue which could cause the Inferno Properties operator to crash in some scenarios
* fixed an issue with tySplineMesher extrusion mode face winding order (some splines would extrude with flipped faces if cap tessellation operation flipped spline winding order)
* fixed a regression where the less/greater than conditions of the Property Test were also equal-inclusive
* fixed an issue where inferno recall cache display would not properly display animated intersectors
* fixed an issue that prevented tyFlow from properly saving/loading animated RGBA values
* fixed an issue which prevented negative steering multipliers on tyVehicle wheel helpers from working properly
* fixed an issue where tyVehicle struts were not properly respecting the rest offset parameters of physical wheels
* fixed an issue where the Particle Bind operator's "weld connected cloth meshes" option could generate cloth mesh artifacts
* fixed an issue where tyTerrain Downloader would fail to download large color textures (larger than 13K x 13K pixels)
* fixed an issue where trying to connect multiple selected operators to the same input would only connect one of them
* fixed an issue where tyPush element push values could not be negative
* fixed an inconsistency with how the PhysX Vehicle operator computed differential velocities, which could affect skid particle generation (users may need to reduce slip/drag thresholds to generate the same number of skid particles as before)]]>