VDB issues
#1
I'm having a couple of issues that I think are both related to the VDB implementation in tyFlow.

I upgraded to the latest version of tyFlow (1.1333) and the VDB mesh being created (from some scene geometry) is noticeably 'fatter' than before. The object is quite small in the scene but I rolled back the plugin and confirmed the VFB mesh used to match the underlying objects much more closely.

The second issue is weirder, and may be V-Ray's problem rather than tyFlow's so I'm attaching an example scene to hopefully shed some light on it!

In the scene is some geo with vertex animation, which is then being turned into an SDF>VDB in tyFlow. So far, all good (although you should be able to see the 'puffiness' of the VDB here). 

I then have a simple Plane object following the surface of the original geo using Skin Wrap (I have also tried tyConform in Temporal mode). In the viewport, everything's fine but when I render in V-Ray, after frame 0 the Plane stops rendering and/or max crashes. If I hide then unhide the tyFlow object, then the plane renders fine but only on that frame, scrubbing the timeline breaks it again. Also, if I disable or hid the tyFlow object, the Plane renders fine.

I haven't applied any materials in this example, just in case that was part of the issue. Oh, and this second issue was happening in an older version, I upgraded to see it if would fix it, hence noticing the puffier VDB mesh.


Attached Files
.max   vdb_problems_max2026.max (Size: 756 KB / Downloads: 148)
  Reply
#2
Here's a screenshot comparison of the VDB mesh generated in 1131 vs 1133

1131
   

1133
   

I checked and 1132 also created the larger mesh, so it looks like the change was introduced there, if that helps track it down.
  Reply
#3
I don't know if this helps but I think one of the contributing factors is having geometry that's listed in the 'Object to VDB' operator used in a Skin Wrap or tyConform(Temporal) modifier eslewhere.

If I keep re-rendering the same frame, the skin-wrapped geometry either vanishes or will randomly move/scale.
  Reply
#4
Hey moonjam,

The fatness issue is actually the result of a recent bug fix - in older builds, the VDB Mesh operator's Iso value took no effect on SDF grids - now that is fixed, but because the default value is 0.5, this puffs up meshes compared to before. I can understand the confusion though - I'll set the default to 0.0 in the next build so the old behavior returns.

In terms of the rendering issue, I'm not able to reproduce that. Using your scene, in Max 2026 with VRay 7 Hotfix 2, I can hit render on the sequence and see no issues after letting a dozen or so frames go through...
  Reply
#5
(02-04-2026, 03:06 PM)tyFlow Wrote: Hey moonjam,

The fatness issue is actually the result of a recent bug fix - in older builds, the VDB Mesh operator's Iso value took no effect on SDF grids - now that is fixed, but because the default value is 0.5, this puffs up meshes compared to before. I can understand the confusion though - I'll set the default to 0.0 in the next build so the old behavior returns.

In terms of the rendering issue, I'm not able to reproduce that. Using your scene, in Max 2026 with VRay 7 Hotfix 2, I can hit render on the sequence and see no issues after letting a dozen or so frames go through...

Hey Tyson,

Thank you for looking in this. The SDF thing makes sense, I'm glad it wasn't just me!

I've just noticed that in the file I uploaded, the tyFlow object is disabled. If you turn it on, and render the sequence does it still work for you?

Thanks again!

AJ
  Reply
#6
Ah yes, now I can repro.

I can see the crash is happening in VRay's light cache thread...not sure why, though. Might be one to send directly to the Chaos devs (the crash minidump, especially).

Tried caching out the deforming mesh and could no longer repro the crash. So something about rendering the tyFlow directly (with VRay) is triggering the issue, but only Chaos would be able to tell why. I also tried rendering with Arnold and Scanline and get no crash or issues with those.
  Reply
#7
Ok cool. I will now hassle Chaos as well!

Thanks man!
  Reply


Forum Jump: