Fyll
commented
8 years ago Ah yes. I remember seeing that happen once, giggling, then immediately forgetting about it. This is because the code doesn't have any special cases for handling things being inside other things, it just pushes them out as if they'd moved that far in in one step (hence, bouncing back massively). I suppose this could be nicely fixed (code-wise) by just implementing a max velocity, but that'd mean the crate would still get fired out, just at a more reasonable speed.
As you say, putting something into the code to just ignore things that are already inside each other (as opposed to moving into one another) would also be a fix, as would just smashing things (but what if the prop can't be smashed, e.g. Steel crate?). Would one of these be more desirable?
As to pushing two crates into each other, I can't seem to replicate that. How did you do it? Was it just a little bit of overlap? As a potential fix, there's a constant in Skeleton.hpp called VERLET_LOOPS, which should be set to 1. If you increase that, the collisions should get sharper (but everything will slow down substantially. You'll have to try changing it to see if it's just my computer being slow).
mspraggs
DivFord
Interesting things happen when freezing water with crates in. For example, I managed to launch a crate through the stone wall and out of the level. Also, I pushed two crates inside each other. Not convinced either of those is desirable behaviour.
The fact that we can turn water blocks into ice is clearly going to be problematic. I wonder if we ought to destroy any prop that's inside a block when it becomes solid. Either that, or try to re-implement the old behaviour where crates just got stuck inside the ice.