Precisely and since Zedd works completely in component vectors it makes life very easy

Yeah, but note that you can generalize even further into simply CV^2 and half your constant. 

Well you should probably be dividing your velocity by a constant inside of the square so that it doesn't reach ungodly numbers, so the equation is evolving into something along the lines of V/C^2 where C is now our constant, although it is starting to mean something different The greater C, the more slippery our water is.

And More Eye Candy!  Yayy i implemented Masses fully, and now the inelastic collisions are physically accurate!  Basic sliding friction has also been implemented, although it is not at 100% yet.  In this screenshot there are 16 randomly generated shapes of the same density but different sizes, meaning they each have a unique mass.  And then there is a very large block with a large mass so you can see how the equations affect the performance

Note that while Mass is represented by a number from 1-255, anything over 32 starts to cause bad errors.  the big block in this screenshot is 16Mass, the rest are from 1-4.

When the object is generated, the height and width are randomly chosen from 2-4.  The Mass is the product of these numbers divided by 4.  H*W/4 = M.  To give each pixel of the object about a 1/4 mass.

Sprites have not been implemented yet, but each object will have a sprite number from 0-255.  255 will represent a filled rectangle with no sprite attached to it, and all of the other numbers will take an offset from sprite data given to Zedd in the form of a pointer.

And yes, i am already planning to make a simple sandbox program with this Where you can create and erase objects, apply forces to them, set global forces, and pause and resume the simulation.  Coupled with Object selection and property editing i think it owuld be a great way to experiment with Zedd I might even start it right now and it will evolve automatically as Zedd improves.

Already working on it

Don't expect it anytime this year though

I'd make something with that -- maybe a sidescrolling open world where you can blow things up

That would require a feature i have not yet implemented into Zedd, an Open World.  Right now the entire world is stored with x256 precision.  That means that at some point, the numbers loop back to the beginning.  Well 2^16 = 65536 / 256 = 256 pixels wide of a simulation screen.  Unfortunately that doesn't give us much scroll space, but i am planning to implement an *open world* where if an Object goes outside of the 256 pixel region, it reverts to x1 accuracy and rudimentary (read: non accurate) physics.  When it comes back into the world, it is converted back into x256 accuracy. This might be tricky to implement, but the 256 region is big enough where i could even possibly freeze objects in place when they go outside and not have any physics at all.

EDIT: And in no circumstances will i be implementing Rotation unfortunately.  Not only does that make the collision many times more difficult, but the collision physics themselves would take exuberant amounts of time.  The entire reason for Zedd's speed is *Because* there is no rotation.

Im actually working on a sandbox demo to give everyone 100% control of Zedd and the new features