You don't need to put the DLLs in the max root anymore...as long as they're in the same location as the tyFlow DLO it'll find them.
Anyways, this is a tough one due to the limited availability of 30XX GPUs right now....I can't even buy one at the moment to test, so all debugging has to happen by proxy with users who send me info.
Can you open the tyProfiler from the editor right click menu (utilities), and then simulate a few frames (as many as you can before it freezes) and then expand the nodes in the tyProfiler to show where the slowdown is? (slower operations will be highlighted, allowing you to quickly determine which operations are the slowest). Then take a screenshot of which function is reported to be the slowest and post it here.
Next, can you open the Debugging rollout of the tyFlow and enable CCCS printouts. Then open the MAXScript listener and re-run the sim. It will run a lot slower, but you should see the MAXScript listener updating at least with CCCS info. Now wait until a frame where it normally would have "frozen"...is the MAXScript listener still updating with CCCS info? Or is everything completely frozen? If you don't mind, give it at least 5 minutes of non-updating MAXScript listener before concluding that it's totally frozen. Doing this part will help me determine if tyFlow is actually frozen, or if there's just an issue causing impact zones to take a really long time to solve.
Anyways, doing these things will hopefully allow me to track down closer to where the issue is.
Anyways, this is a tough one due to the limited availability of 30XX GPUs right now....I can't even buy one at the moment to test, so all debugging has to happen by proxy with users who send me info.
Can you open the tyProfiler from the editor right click menu (utilities), and then simulate a few frames (as many as you can before it freezes) and then expand the nodes in the tyProfiler to show where the slowdown is? (slower operations will be highlighted, allowing you to quickly determine which operations are the slowest). Then take a screenshot of which function is reported to be the slowest and post it here.
Next, can you open the Debugging rollout of the tyFlow and enable CCCS printouts. Then open the MAXScript listener and re-run the sim. It will run a lot slower, but you should see the MAXScript listener updating at least with CCCS info. Now wait until a frame where it normally would have "frozen"...is the MAXScript listener still updating with CCCS info? Or is everything completely frozen? If you don't mind, give it at least 5 minutes of non-updating MAXScript listener before concluding that it's totally frozen. Doing this part will help me determine if tyFlow is actually frozen, or if there's just an issue causing impact zones to take a really long time to solve.
Anyways, doing these things will hopefully allow me to track down closer to where the issue is.