This is the core element for Newton to work with EBasic.
I have a readme file in the zip, please read it.
Physics is used in its own little world.
You have 2 layers when programming 3d Games, you have the visual layer and the physics layer.
On every game loop, you have to call NewtonUpdate, pass it your world identifier and the time that has elapsed since the last run.
Newton will take care of keeping the two layers in sync.
Using this with EBasic will take time to understand, so expect some studing as to how pointers work along with subroutines. I would recommend downloading newtons sdk and reading through it, but at the moment, the creator of Newton has taken the files off his site do to bandwidth issues.
I do have the SDK installed on my PC though, but without his permission to post the CHM file, I am at a loss as to how to distribute the documentation on it.
Looks like a good addition.
Thank you