Help! Problem with collisions keeps on haunting me

Halfhype3

I have no idea whether this is a bug, or if I’m doing something wrong. I’m still very new to ziva so any help is great. Whenever I apply this model as a bone, and have it interact with ztissue with collisions on. The model's collision mesh (Idk the right terminology, the white wireframe), seems to be delayed from the zbone. It hangs up for as small as 5 frames to as long as 80 frames before jumping to the zbone. Then it usually hangs up again. What follows is a cat and mouse game of the collision laggily trying to follow the zbone.

I have installed other versions of maya, maya 2022 and maya 2023 to be met with this same obstacle. I have sent the project with the alembics to another person and they can’t get the bug to replicate. Frankly they’re as stumped as I am when seeing the whole endeavor.

If it's not an issue due to my own blundering, would a reinstall of Ziva even help?

Is there a way I can do anything about this? Is it possible to install a previous version of Ziva so I can hopefully not encounter this? Help.

jamesj

Halfhype3 Is it possible that you have a cycle in your Maya graph? Sometimes cycles will introduce weird behaviour like this.

Halfhype3

jamesj Just checked, there's no cycles enabled in the Maya graph for the model.

jamesj

Halfhype3 that's a head scratcher - does the visualization ever catch up? Or is it always offset? Does it persist if you run a dgdirty -a; refresh; in the MEL script editor?

Halfhype3

jamesj The visualization does catch up at some points. Its not offset by a specific amount of frames at any time. The visualization sometimes matches up with the zbone for 1 frame but then stops before updating to the zbone's correct location at a random point.

Sometimes the updates every few frames or so, sometimes there's large gaps in between each update. Its kinda crazy lol.

Also, I hate to say this, since this just adds even more confusion. But If I close maya completely, open it up, launch the project and let the cache render by itself right away, this error does not happen! It comes back however if I change any settings.

jamesj

Halfhype3 That is very odd.
Are you able to recreate the problem with a simple scene?
Also, are you using the "rivit script" by chance to attach nodes to your bones? (That introduces an cycle that Maya doesn't flag - but can be problematic for simulations)
Another thing you can try is to change your DG evaluation from "Parallel" to "DG"
This can be found in Window->Settings/Preferences->Preferences->Animation

I hope one of these suggestions helps.

Halfhype3

jamesj I will test out soon if I can replicate it. Although changing the DG evaluation from parallel to DG has helped and solves the issue!