RobGalanakis
09-19-2008, 02:48 PM
We've implemented a Vertlet cloth sim at work and I've been optimizing it the past couple days. I've run into a very strange bug.
We have two #nodeTab parameters on our collision objects, to store what edges and particles the object will collide with. When I add any objects to these parameters, the simulation slows down, tremendously (12 to 5 fps per collision object, the larger the array is the more it slows down also). I'm not actually running the collision during the simulation, even- the slowdown is due to these parameters. If I leave them empty, or comment them out from the collision object, I run at a normal speed. But if I set them, I get huge slowdown.
I've found a way around this by using a local variable to store the array, instead of a Tab parameter, and there is no slowdown. This has to be some sort of bug, has anyone encountered anything similar?
Tried the following:
Using both tabSizeVariable and tabSize: neither made a difference.
Storing different types of objects in the array: nothing made a difference.
I've been working on this bug for probably 6 real hours and evaluated the problem a ton and tried loads of things... the 'solution' with a local confirms for me this is a bug but I wanted to see if there was something else happening (going to submit a bug to Autodesk today as well, need to come up with a simple repro setup but I doubt it'll be possible).
We have two #nodeTab parameters on our collision objects, to store what edges and particles the object will collide with. When I add any objects to these parameters, the simulation slows down, tremendously (12 to 5 fps per collision object, the larger the array is the more it slows down also). I'm not actually running the collision during the simulation, even- the slowdown is due to these parameters. If I leave them empty, or comment them out from the collision object, I run at a normal speed. But if I set them, I get huge slowdown.
I've found a way around this by using a local variable to store the array, instead of a Tab parameter, and there is no slowdown. This has to be some sort of bug, has anyone encountered anything similar?
Tried the following:
Using both tabSizeVariable and tabSize: neither made a difference.
Storing different types of objects in the array: nothing made a difference.
I've been working on this bug for probably 6 real hours and evaluated the problem a ton and tried loads of things... the 'solution' with a local confirms for me this is a bug but I wanted to see if there was something else happening (going to submit a bug to Autodesk today as well, need to come up with a simple repro setup but I doubt it'll be possible).