I can see about maybe attempting to document the features of the lib better, if I ever get around to testing it myself. I may use it for a flying camera Rubik's cube sim for the 83+SE... It's very promising and extremely impressive. I wish Axe was for the CSe, too...

First of all, sorry for the late reply, I promised this post over a week ago, but something came inbetween and after that, I kinda forgot about it...

Anyway, I'll start with the final platform, the one you can walk under. It's basically the same as the previous one, but with an added condition:
if(X >= Floor.Xstart && X <= Floor.Xend && Z >= Floor.Zstart && Z <= Floor.Zend && Y <= Floor.height && Y > Floor.height-Floor.thickness){
    FallSpeed = 0;
    Y = Floor.height
}
This will give you a platform with the top at floor.height, and it isn't infinitly thick anymore. It is reccomended to give each platform a thickness of AT LEAST the terminal velocity (or the maximum speed the player can fall in that area of the level), otherwise, it is possible for the collision detection to 'miss' this platform, causing the player to just fall trough it.
If you don't add anything to this collision detection, it will act as a 1-way platform, which means that if you jump while you're beneath it, you will go trough and land on the top. If yoou don't want this, you can add a 2nd collision for the bottom, or a 2nd platform right beneath it, which on collision only sets the fall speed and doesn't set the Y-coordinate.

Before we start with walls, there's still something platform-related that may also be usefull for some games: ramps and tilted platforms.
It's actually quite simple: Where you first used a fixed value to determine the height of the platform (in the example: Floor.height), you use a simple calculation based on the X and/or Y coordinates. So, if you want a ramp with a 45° angle around the X-axis, you check if Y<Floor.geight+Z, where Floor.height is the lowest part of the ramp. If you want a different angle, you can divide the Z by a number, if you want it more steeph, multiply the Z by a number (multiply Z by the tangent of the angle, if you like angles better). You can also use a different axis than the Z-axis, and you can also use other functions than simple linear ones, but keep in mind that more complex functions take longer to compute.
Also, this is still simple, vertical-only collision detection, not a physics simulation. It wil allow you to walk up any ramp, no mather how steep, but it won't let you slide down a ramp.
If you want to use this for tilted platforms, it's often best to use the same function for both the top and bottom of the platform, to give it the same thickness everywhere.

If you still want some other kind of platform, feel free to ask, and I'll look into a way to code it.

Now, the walls. They are pretty simular to the platforms, just using other axes and you don't have to mess with the fallspeed.
Let's start with the most simple kind, as we did with the platforms:

World borders
This one is basically the same as the first 'platform', as it is an infinite plane and it's impossible to walk trough. The only practical use is 'locking' the player in a certain area. It might seem rather useless at first, but considering the limited hardware of the calc, overflows will occur if the player moves to far from the center of the world, so you might want to keep him close to the center.
The code is very simple:
if(X > Xmax){
    X = Xmax
}
This makes sure that the player can't move beyond Xmax on the X-axis. You can use 4 of those walls to define the uncrossable world borders.

single-sided walls
Because walls with infinite thickness are rather useless, we'll move straight to single-sided walls.
The code is quite similar to that of the one-way platform:
if(X > wall.X && X < wall.X+wall.Thickness && Z >= wall.Zstart && Z <= wall.Zend && Y >= wall.Ystart && Y <= wall.Yend){
    X = wall.X
}
You can leave out the part dealing with the Y-axis if you don't need walls with a particular height. It's reccomended to do this if you don't have an open space above or below the wall.

This will create a wall alligned to the Z-axis. To allign it to the X-axis, replace all Z's by X's and vice-versa. The thickness of the wall should be at least the (max) walk speed of the player, to avoid the player walking trough it. To avoid graphical glitches, offset this wall slightely from the graphical wall.

double-sideed walls
Simular to the platform, the single-sided wall will only stop players comming from the right way. If you need a full solid wall, you have to use two walls, like this:
if(X > wall.X && X < wall.X+wall.Thickness && Z >= wall.Zstart && Z <= wall.Zend && Y >= wall.Ystart && Y <= wall.Yend){
    X = wall.X
}
if(X < wall.X+wall.Thickness && X > wall.X && Z >= wall.Zstart && Z <= wall.Zend && Y >= wall.Ystart && Y <= wall.Yend){
    X = wall.X+wall.Thickness
}
This creates a wall that is solid from two sides, but if you walk into the ends, you'll ennd up at one side of the wall, instead of stopping there. If you want to stop there, add single sided walls at the ends, alligned to the other axis than the main wall.

You can make the top and/or bottom of a wall tilted, or follow a function, in the same way as with the platform. If you want to use walls as sides of a platform with a non-level top, it's reccomended to do so. And if you're dealing with a ramp, don't add a wall where the tilted edge connects to the ground, and if you make the walls of the triangular side stop a bit in front of that angle, then you don't have to walk up the ramp from the edge where it connects to the ground, but you can then also walk onto it from the sides where it is still low.

This ends the walls part. If you have any questions or if you want me to look into an other type, feel free to ask.

This looks great, and it seems to be fast too.

However, sometimes, there seem to be glitchy horizontal black or white lines. Does this happen on a real calc as well or is it because of the screen capturing software?

BTW: does this already work for all polygons or only solid black ones?

Mais ton clipping ne marche pas en hauteur ca vient aussi de ca le bug non ?

sorry i can't say this in english ^^

Do you use a rom-dumped rom for wabbit? If not, do it, the others have some wierd bugs.

So yeah, looking awesome

Update of the main lib !!  (the readme is not finalized, so please refer for the moment to the tuto)

*multiple camera handling
*vertex shader
*better system in general
*lot of optimisations

EDIT fixed version !!! shader now work proprelly, and file is clean : This is the final version =)

Is GCORE fully functional and finished now ?

Well there will have just some little modification in the shader code, but this is almost nothing  (and if I find optimization, I'll made update)
So, we can consider the GCORE as fully functionnal, yes

ui, that is looking awesome! How come you are so amazing