Tymesher causes 3ds max and Vray to crash with Gaussian Filter
#1
Using tyflow 1029 and 1028 versions, when adding tymesher to particles and adjusting the voxel filtering to Gaussian and changing the filter width value, this causes 3ds max to crash and close suddenly with error (see attached), this usually happens especially when navigating in the timeline

is there a workaround? I tried also tyrelax and played with it to achieve my desired result but still, do you think I can convert this mesh to alembic? is there any way?


Attached Files Thumbnail(s)
   
PC Specs: CPU i9-14900K - GPU RTX 4090 - RAM 192GB 5200MHz - MB Asus ROG Maximus Dark Hero
  Reply
#2
(01-20-2024, 08:22 AM)olivfx Wrote: Using tyflow 1029 and 1028 versions, when adding tymesher to particles and adjusting the voxel filtering to Gaussian and changing the filter width value, this causes 3ds max to crash and close suddenly with error (see attached), this usually happens especially when navigating in the timeline

is there a workaround? I tried also tyrelax and played with it to achieve my desired result but still, do you think I can convert this mesh to alembic? is there any way?

any idea anyone?
PC Specs: CPU i9-14900K - GPU RTX 4090 - RAM 192GB 5200MHz - MB Asus ROG Maximus Dark Hero
  Reply
#3
If it's crashing please submit the minidump:

https://forum.tyflow.com/thread-717.html
  Reply
#4
(01-22-2024, 03:08 PM)tyFlow Wrote: If it's crashing please submit the minidump:

https://forum.tyflow.com/thread-717.html


Attached Files
.dmp   3dsmax_minidump.dmp (Size: 8.26 MB / Downloads: 16)
PC Specs: CPU i9-14900K - GPU RTX 4090 - RAM 192GB 5200MHz - MB Asus ROG Maximus Dark Hero
  Reply
#5
Can you upload your file as well please...the minidump shows the issue happening deep within the OpenVDB library...I'd need the full scene to look into it any further.
  Reply
#6
sure check it here with a new dmp file also just happened an hour ago: https://drive.google.com/drive/folders/1...sp=sharing

also some frames seems to render the mesh wrong, randomly like frame 167 and are taking up to two hours of render meanwhile the normal render would take 17 mins
PC Specs: CPU i9-14900K - GPU RTX 4090 - RAM 192GB 5200MHz - MB Asus ROG Maximus Dark Hero
  Reply
#7
Can you upload the tyCache too please, it's missing from the drive folder.
  Reply
#8
(01-23-2024, 02:18 PM)tyFlow Wrote: Can you upload the tyCache too please, it's missing from the drive folder.

done
PC Specs: CPU i9-14900K - GPU RTX 4090 - RAM 192GB 5200MHz - MB Asus ROG Maximus Dark Hero
  Reply
#9
Thanks, so I haven't had any issues applying a Gaussian filter over here...I scrubbed to a few different frames and applied the filter repeatedly without issue. I can't speak to the rendering issue...frame 167 started rendering buckets after a few seconds (and once buckets begin to render, tyFlow is done initializing, which means any slowdowns or issues past that point are no longer in tyFlow's hands).

There was a rare issue that came to light a while ago, that affected versions of tyFlow using OpenVDB 9+, where certain machines would crash due to OVDB9's implementation of Intel's OneAPI over the legacy TBB library (cause of crash was rare and ultimately unknown).

You can try downgrading to tyFlow v1.007, which still uses OpenVDB 8, and see if the scene is more stable using that older version. I believe your cache and things should still load even though it's a much older build....v1.007 can be downloaded from the usual place:

https://docs.tyflow.com/download
  Reply
#10
(01-23-2024, 03:23 PM)tyFlow Wrote: Thanks, so I haven't had any issues applying a Gaussian filter over here...I scrubbed to a few different frames and applied the filter repeatedly without issue. I can't speak to the rendering issue...frame 167 started rendering buckets after a few seconds (and once buckets begin to render, tyFlow is done initializing, which means any slowdowns or issues past that point are no longer in tyFlow's hands).

There was a rare issue that came to light a while ago, that affected versions of tyFlow using OpenVDB 9+, where certain machines would crash due to OVDB9's implementation of Intel's OneAPI over the legacy TBB library (cause of crash was rare and ultimately unknown).

You can try downgrading to tyFlow v1.007, which still uses OpenVDB 8, and see if the scene is more stable using that older version. I believe your cache and things should still load even though it's a much older build....v1.007 can be downloaded from the usual place:

https://docs.tyflow.com/download

Thank you for your reply and the useful info, let me show you a video screenrec of what's happening I tried to trigger the error by myself now

check it is uploaded on this link: https://youtu.be/EmMHGrko6vM

also this is a log error in vray check it attached, no motion blur! I really need motion blur to have it perfectly why is that? or motion blur does not work with gaussian?


Attached Files Thumbnail(s)
   
PC Specs: CPU i9-14900K - GPU RTX 4090 - RAM 192GB 5200MHz - MB Asus ROG Maximus Dark Hero
  Reply
#11
(01-25-2024, 06:29 AM)olivfx Wrote:
(01-23-2024, 03:23 PM)tyFlow Wrote: Thanks, so I haven't had any issues applying a Gaussian filter over here...I scrubbed to a few different frames and applied the filter repeatedly without issue. I can't speak to the rendering issue...frame 167 started rendering buckets after a few seconds (and once buckets begin to render, tyFlow is done initializing, which means any slowdowns or issues past that point are no longer in tyFlow's hands).

There was a rare issue that came to light a while ago, that affected versions of tyFlow using OpenVDB 9+, where certain machines would crash due to OVDB9's implementation of Intel's OneAPI over the legacy TBB library (cause of crash was rare and ultimately unknown).

You can try downgrading to tyFlow v1.007, which still uses OpenVDB 8, and see if the scene is more stable using that older version. I believe your cache and things should still load even though it's a much older build....v1.007 can be downloaded from the usual place:

https://docs.tyflow.com/download

Thank you for your reply and the useful info, let me show you a video screenrec of what's happening I tried to trigger the error by myself now

check it is uploaded on this link: https://youtu.be/EmMHGrko6vM

also this is a log error in vray check it attached, no motion blur! I really need motion blur to have it perfectly why is that? or motion blur does not work with gaussian?

any updates on this?
PC Specs: CPU i9-14900K - GPU RTX 4090 - RAM 192GB 5200MHz - MB Asus ROG Maximus Dark Hero
  Reply
#12
Did you try my suggestion (downgrading to avoid the crash)?
  Reply
#13
I tried yes downgrading and same issue was happening, but at the end with all the bugs and crashes I finally made it till the end but was really hectic would really love this to be fixed...
check the final beauty render here with VFX breakdown and let me know what you think, tagged you on Instagram too:

Final beauty
https://www.instagram.com/reel/C2ho_hTps...c2M2x5ZGZl

VFX Breakdown
https://www.instagram.com/reel/C2y5t9Jpj...trMTJwdmd3
PC Specs: CPU i9-14900K - GPU RTX 4090 - RAM 192GB 5200MHz - MB Asus ROG Maximus Dark Hero
  Reply
#14
Hmm, well I'm glad you were able to finish your project. Unfortunately because the issue is happening deep inside the OpenVDB library, and I can't reproduce it here, it's going to be nearly impossible to debug. All I can hope is that next time I upgrade my OpenVDB integration to the latest version in their official repo, it'll be something they have already addressed and it will just sort of go away.
  Reply


Forum Jump: