Ross Nordby

Reproduced the asserts and some wonky behavior; should have a fix pushed tomorrow. Notably, I couldn't reproduce the memory corruption. Not sure what's going on there, but there's a good...

>should have a fix pushed tomorrow. The ostensible fix was secretly possessed by satan; more time may be required.

Alright, should be fixed as of 0ecb874632905da8ffd474ebf1564eed273a25fc (2.5.0-beta17). The hulls created for that sort of pathological case should now be much less likely to contain spurious internal faces. I wasn't...

Woooooooooops! I guess it was inevitable that I was going to forget to re-disable that one of these times. I'm at a conference, but I'll get that fixed as soon...

Note: there are two single threaded paths for partitioning. One uses a pingpong buffer to avoid having to do in-place shuffles. It's marginally faster and is used by default when...

Meshes are composed of triangles and triangles are one sided; collisions on the backface of a triangle go through. By the way, standard recommendation is avoid mesh-mesh collisions. They're expensive...

The original code has inconsistently wound triangles; the bottom face is flipped from the other faces. When I run it on master with consistent windings, it works as expected. The...

> Or is that problematic in some way because I add the shape to the simulation twice? Compounds can only refer to child shapes which have been added to the...

> Can you promt some kind of warning for that case? Now(2.3) it appears to just ignore that and have no collisions. I don't remember when they were added, but...

> Hey, was pointed at this repo by some other people and just wanted to say looks awesome! Thanks! > As the owner of the System.Numerics and System.Runtime.Intrinsics APIs on...