I suppose because there would still be a lot of detail required and calc 3D is pretty limited in complexity. But still worth a shot.

Small update

All drawing commands now takes an additional argument : 0 for black drawing, 1 for solid white. This makes solid display possible for you guys

Also, if you can think of any functionality that you'd like to see in the axiom, please tell us because I'm a bit out of inspiration

Textures will come later (they'll come ), but yeah I forgot about clipping I'll take care of that, even if it's not a functionality.

Bad news ...

I can't write a proper clipped triangle. I don't know why, but this just doesn't want to work. I re-read the code many many times and still can't see the error. If you guys wanna help me with this, here is the complete AxeJh3D code at pastebin.

Actually, clipping works perfectly with y < 0, y > 63, x > 95 but not with x < 0. I also attached a small Axe program to test the routine, if you want to see what's wrong or to fix it.

I need to explain some things related to the way I draw the triangle. First, I constantly use 3 variables : startX1 and startX2, two 16.8 numbers, which refers to the left and right pixels of the line to draw (because I draw the triangle with horizontal lines), startY, which is the Y coordinate of the line. I also constantly add two 8.8 variables to startX1 and startX2, namely dx1 and dx2, which are the slope of each side (dx1 is updated during the process to the slope of the 3rd edge of the triangle). I did it that way because with only 8.8 startX*, the triangle went too fast from 127 to -128, making the triangle being drawn wrongly. So by doing that, my goal was to fix that error, since it's harder to go from 32767 to -32768.

EDIT : with help from Runer112 on IRC, we made it that the triangle is properly clipped when x < 0 ; but the 127→-128 thing still appears, so the problem is not solved yet.

Since you are clipping triangles in 2D, you will need to see if the length of any slice is > 128 and dont draw if this is so. This usually means that the triangle is ultra close to the viewer anyway so should be ok.

If you are wanting to make an indoor room however, you might need to look at 3D clipping techniques.

You need to add an offset to {L1+4}r (150 works fine) so that the point doesn't project right at your eyes, but a little further. I'm very glad to finally see someone trying to use the axiom ^^

You're welcome keep us informed about your work ! I'd love to see moar 3D stuffs coming up !

Quad( will need the inputted vertices to be ... inputted as follows :
1---------2
|         |
4---------3Rotated in any way of course.
You use the function in that way :

Quad(OFFSETS, TABLE, COLOR)

OFFSETS is a pointer on 41-bytes values, which are multiples of 6 : they will be added to TABLE, which is a pointer on a table of 6-bytes vertices (don't forget to rotate them before drawing). COLOR is 0 for black and 1 for solid white. Example :

Quad(Data(24,48,6,12), GDB1ROT, 1)

Will draw a white quad out of the 4th, 8th, 1st and 2nd vertices of the vertices table situated at GDB1ROT.

EDIT : not sure about the multiples of 6, I guess you can just test it. Maybe in the example it's just Data(4,8,1,2), I don't remember