Is this still full axe? and does the speed drop a lot when you add more walls?

Also, will there be objects like plants, trees, chairs, ... to pretify the levels?

yea, but I think this program/patch/watever it'll be is meant to convert or run the programs which were only released for the 83+ series, and their author has been unactive for a while so you can't just ask him to port, and also for the programs compiled by axe parser. But for axe parser, I wonder if programs compiled for ion would run on a ti-83. When you transfer them to a computer, they are saved in .8xp format.

I think you made a mistake with posting the pictures of the XOR gate: It's twice the same one.

BTW: what texture pack are you using?

calc84 has clearly said in his ti-boy project thread that it's an emulator, not a convertor. The main problem with a convertor is finding the difference between data and code. If you convert data, or leave parts of code untouched, you may have some nasty results. One way of doing this would be to create a very simple 'emulator', that starts reading the program from it's start, and that knows which sequences of bytes represents jumps, calls (and ret's) and bcalls. Also code in the size of optcodes so that it won't recougnize a jump or bcall in what is actually just the end of one optcode and the beginning of an other one. Then you need a boolean array. Use one boolean for every byte of the program. These should all be false at start and mark if a byte is read. Then, 'emulate' the program. At every byte you pass, mark the byte as read (set boolean to 'true'). When you encounter a call instruction, push the position of that instruction to a stack, and continue emulating from where the call points to (substract $9D93 from the label behind the call to get the number of bytes from the start of the program). When you encounter a ret instruction, continue emulating from the location in the stack, or if the stack is empty, stop the emulation. When you come across a jump instruction, check if it's conditional or not. If conditional, save it's location to an other stack than the one used by calls. Then just continue emulating from the location the jump points too, just as you would do with normal jumps. If you encounter a bcall, replace the label with the corresponding ti-83 label. If the bcall isn't supported by the ti-83, replace it by a call to a routine that does the same and that you add at the end of the program (and make sure you don't add it multiple times.) Befoire 'emulating' the next instruction, check if it was already read. If not read, then continue emulating normally. Else, continue emulating from the location stored in the relative jump stack. If that stack is empty, stop emulating, show the user that the conversion failed and terminate the program.

If it exited correctely because of a ret, then add some code at the start that sets up free, useable RAM memory at the standard 83+ locations (when nessicary). Keep 3 bytes free at the end of this one and save the location. At the end of that routine, add an other routine that cleans up that ram and formats it in the way that the ti-83 OS suspects it, and add a ret to the end. Now replace the 3 bytes you kept free with a call to the start of the program (thus to the end of the 2nd routine). Save the program in the proper 83p format, and show the user a message that it finished converting and that he has to try it on an emulator first, backup his data, and that you're not responsible for any damage to calculators caused by this program, ...

This should work on any program (not app) that doesn't use a shell, jump tables or SMC.

It's not really transparency, but in this picture, the texture was rendered before the wireframe, which means that everything that is white on the texture looks transparent in the final result. If the texture is rendered after the wireframe, white on the texture will be fully white.

also, to give an impression of the resolution of the textures: the tick border is 3 texels (pixels of the texture) wide.

Yould you please ask your ops to don't randomly kill players with a rain of TNT? (the 'may death fall upon them' thing) I enjoyed the server untill then: I lost every single item that I had, and a lot of those items are really valuable (one of them was a superenchanted diamond sword).

you can redownload those at ti's website if you would ever need them again (which is very unlickely).

By the way, does blender support .md3 files? The models I am using are .md3 files.

not by default, but you should be able to find a python script for that.