I can't do much gaming in school. The network isn't secured or anything, but all computers there are way to slow to make playing any game enjoyable. this is the only kind of security that's impossible to hack.

Oh nice a new 3D game. I hope it is still being worked on though.

Yes, there's still worked on, but progress is going really slow: I had much problems with this that needed to be solved like a problem with the resolution causing a crash on MAC's, model import scripts that suddenly stopped working, shaders not working correctely etc.

But as soon as this is all fixed and there is already some gameplay, I will release a demo.

BTW: the screenshot is already outdated. Instaed of one big model of the intire world, the world would be made out of multiple terrains(those are a special type of models that take up a lot less memory than normal models), and separate models of buildings which can be used multiple times.

It looks like you need to optimize your code to do grayscale, but it should be doable. There is a grayscale maze game for the 83+ line of calcs. I think it's called maze3D.

But anyway: nice to see a new first person shooter. I like gemini, but when you have many programs, the VAT is to large to run it. Goot to see that's fixed.

I've tried marioland on it, and it works great. But when I turn on the sound, I heared that the backgroung music is really slow (1 note every 5 secs), while the effects (like smashing a block) are still at the correct speed. Is that the way it is on a real gameboy, or a bug in ti-boy?

BTW: this is on a 1 year old calc, so it hasn't got the extra ram pages.

If you only need to do simple lighting, then you only need to find out the angle between the direction the light hits the surface and the normal vector.

EDIT: I checked it: it's the cosine of the angle between the normal and the light direction. That's all you need if you just want the most simple concept of lighting.

This one's great: take a screenshot of the desktop with all the icons, use that image as the background, then, hide the icons. Then, if you click one one of the icons, nothing happens because the're just images.

It depends on the situation. When there isn't very many polygons, sorting is faster, but past a certain number, (I think around a hundred) the sorting algorithm becomes too slow and z-buffering wins. Also keep in mind only z buffering is able to correctly show intersecting polygons.

I know z buffering is only able to correctely show intersecting polygons, but also: one byte isn't accurate enough for polygons close to each other, so I need two byter for every pixel on the screen, so that would make 1228 bytes, which is really much, and I'm wondering if it's worth it to use that many bytes for only the graphical part.