Originally Posted by Lapsus
I think that changing the character models would break any existing replays, because the replays depend entirely on the physics engine and models to be consistent. If you open one up in notepad, you'll see that they're essentially just a list of what joints were changed, and at what frames. It's also the reason why replays don't work very well, if at all, with scripts that affect the characters.
This only currently happens because the "models" are primitives based on the hitboxes, not the other way around.
Originally Posted by Jalis
This only currently happens because the "models" are primitives based on the hitboxes, not the other way around.
As a design choice it isn't entirely stupid, hampa just wanted to give the Toribash models an authentic physical feel based on the actual model used. I'm more concerned about how the physics are calculated, it seems that the time complexity is either quadratic or exponential, and really for a physics engine to work well you want it to be polynomial at most. I don't think it uses any kind of octree model to separate the physical objects into groups to check for collisions, and the solutions hampa has hacked in for when there are collisions to stop the joins from glitching out are slowing the game down significantly. The reason Toribash even needs you to have a good CPU is the physics engine, which I would characterise as "poorly programmed".
