+- tyFlow Forum (https://forum.tyflow.com)
+-- Forum: tyFlow Discussion (https://forum.tyflow.com/forum-1.html)
+--- Forum: Bugs and Issues (https://forum.tyflow.com/forum-3.html)
+--- Thread: Ty Flow crashes max (/thread-3883.html)
Ty Flow crashes max - dv2000 - 09-15-2023
Hi,
If you enable the event or refresh 2023.3 max crashes. We are using the latest build.
This tyflow was made in version 1.011 and merged to another scene. And we are using the latest build now. Maybe that's the reason
RE: Ty Flow crashes max - tyFlow - 09-15-2023
I'm not able to reproduce the issue here...I can refresh and no crash occurs. However, in the scene you posted the Birth Objects input object is deleted - maybe that's why I don't get the crash.
Can you also post the crash minidump?
RE: Ty Flow crashes max - dv2000 - 09-15-2023
(09-15-2023, 02:56 PM)tyFlow Wrote: I'm not able to reproduce the issue here...I can refresh and no crash occurs. However, in the scene you posted the Birth Objects input object is deleted - maybe that's why I don't get the crash.
Can you also post the crash minidump?
Hi,
Here it is. Mine crashes when I click on the light bulb
Date/Time: 2023-09-15 10:28:21 -05:00
Application: 3dsmax.exe
Error: Access violation - code c0000005 (first/second chance not available)
Crashed Module Name: tyFlow_2023.dlo
Exception Address: 0x00007ffb0f420e95
Exception Code: c0000005
Exception Flags: 0
Exception Parameters: 0, ffffffffffffffff
RE: Ty Flow crashes max - tyFlow - 09-15-2023
Thanks for the minidump...
So the crash is happening during PhysX CUDA initialization. Can you update your CUDA DLLs from the tyFlow download page (specifically the PhysX DLL) and see if that alleviates the problem?
Alternatively you can just disable PhysX CUDA support for now.
RE: Ty Flow crashes max - dv2000 - 09-15-2023
(09-15-2023, 04:12 PM)tyFlow Wrote: Thanks for the minidump...
So the crash is happening during PhysX CUDA initialization. Can you update your CUDA DLLs from the tyFlow download page (specifically the PhysX DLL) and see if that alleviates the problem?
Alternatively you can just disable PhysX CUDA support for now.
Thank you, It fixed it.