Just a thing though : the text actually slows down the program. Try removing it and test it again in wabbit.

By the way I just saw the screenshot at http://tiplanet.org/forum/archives_voir.php?id=20611 and it looks really great

this is the exact screen that as been posted by nikitouzz a few post ago, but I am glad that you like it 

EDIT : by the way, I forgot to tell you that a little update is coming =)

What do you exactly want as shader ? 

lol  I am getting close, you know ?
*TheMachine02 run too

Ok, I work a little on shaders, and I have add a vertex shader and a pixel shader 

EDIT : I also got idea on adding skybox

Just a little question to all of you :

What do you want me to add to the library?  (new feature .... ) 

The following shaders/effects: Fog, Water, real-time shadow casting, DOF, God rays, motion blur, bloom

Now serious:
Better documentation and more examples: The current documentation is a bit hard to use, and (not meant offensive), it kinda feels incomplete and like it was written in a hurry. And the examples do demonstrate what the engine can do, but it would be very usefull to programmers if you'd add comments (maybe in a .txt file so it can be read on a computer) for everything that uses a part of the library to describe in detail why it's there and what it does. A simple tutorial to get started might be nice too.

Finally, a real feature: It would be nice to have some basic collision detection. It would be okay for me if it could only handle rectangular shapes, even if they are alligned to the x and y axes. This is easy to program and doesn't require a lot of calculations so it is not slow.
If you're unsure of how to implement collision detection, I wouldn't mind to help.

BTW: About the documentation: It can be hard to write clear documentation because even when it's incomplete, it will be clear to you because you know how it works. Therefore, it helps if you let someone read it who hasn't used the library yet, and if he(/she) understands it, then you can be almost sure that most other people will understand it too.

What do you exactly want as shader ? 

I think he wants you to make Crysis for calcs.

Well  I guess Fog, DOF, God rays, motion blur, bloom is not really calc level.
But I work on some real-time shadows casting, and now I can have a sun with shadows ! (pretty limited for the moment though : shadows only on the ground (no
user-defined plane) , and the light source is multi directionnal and must be the most higher point in the decor)

You really have shadows? That's actually pretty awesome for a calc engine. The suggestion of those effects was just a joke.

For collision: if a simple system like the one I used in my racing game, it's not hard at all:
This is how the collision with the ground is done:
The player should have a variable that represents the speed at which it falls. At the beginning of the update loop, increase that variable with a value that represents the gravity, and make sure it doesn't go above a certain value (let's call that value the terminal velocity) to make sure that if the player falls a long way, it still won't go so fast that the collision checking may miss it. Play around with that value to see what looks realistic (depends on the size of your units and the framerate). At the end, substract the falling speed variable from the Y-coordinate of the player(Y is the up axis, right? Otherwise, use the axis that points up). You can repeat this for other objects that need collision checking, but every one of those needs it's own falling speed variable.
For a simple collision with an infinite and flat ground (the simplest and fastest kind), you basically do this:
If(Y <= [Ground level]){
    FallSpeed = 0;
    Y = [Ground level]
}
In words: if the player/object is at or below the grown level, set the fallspeed to 0, and set the Y position of the player (or object) to the ground level (so that if the player hass fallen slightely further than ground level, the player will still end up on the ground). This method is quite fail-safe because it's impossible for the player to fall trough this floor, even when the player fals at a high velocity.

You can also add position parameters to the above method. This can be used in the combination with the previous method to create a raised area in the otherwise flat world:
if(X >= Floor.Xstart && X <= Floor.Xend && Z >= Floor.Zstart && Z <= Floor.Zend && Y <= Floor.height){
    FallSpeed = 0;
    Y = Floor.height
}
With this kind of platform, it is also impossible to fall trough it, but it needs additional collision checking for the sides, because otherwise, a player walking into the edge of the platform will be teleported to the top of the platform. It's also possible to do this with platforms that aren't rectangular or aren't alligned with the X/Z axes, and for that, you replace the if above with one that checks if the player is inside the 'shape' of the platform. This does need a lot more processing power, though.

I'll explain some other things, like simple walls and 'floating' platforms (where you can walk underneath and stand on top of them) tomorrow.

BTW: The FallSpeed variable can also be used for an other application than falling: jumping. Set it to something negative, and the player will go up, decellerate, accelerate again towards the floor, and stop when it hits the floor. By setting this to a large negative value, the player will fly up really high.