Just working on tile collision and thought I'd share my method for people curious on how to do tile physics. There is a map class that takes care of the collision. The heart of it is the customizable callbacks called the preSolve and postSolve. With the callbacks, you can do neat things like one way...

rar format is not supported. Use zip.

Ah classical mechanics! Just a warning to readers, this method only works if the acceleration is constant. If your acceleration is a function of position or velocity, then you will need an approximate method or solve for the differential equation in another way.

I was curious about the blend modes too. Here's the link on how they work: viewtopic.php?f=4&t=10268&p=62175&hilit=+blend#p62171

You can set up a toggle variable which you can change with a key press or mouse press.

I wish college wasn't taking so much of my time.

I discovered that closures are cheap if the underlying operations per closure creation are more expensive than the creation of the closure. I have made this same update in my sweep and prune for raycasting. Before that, I used a table to store my state for the raycast iterator. Now I just create a c...

Yes I understand. I only posted the paper because I have done some research on this before and recognized your findings. Plus math is a bit easier for me to understand than programming (this is something I just do for fun).

Continuous collision detection is a very interesting subject. If you're really into that, you could also visit the bullet or box2d forum and talk to the authors about some techniques. This is pretty cool though combining your previous post for line intersecting test with the Minkowski Sum. For the c...

It's unlikely that you'll get good performance for a sand game without using shaders. Love can't handle that many particles (90000!?) See: https://love2d.org/forums/viewtopic.php?f=4&t=3733&p=37873&hilit=sand#p37873 I take it back. Someone apparently made a nice demo (I even commented!)...