Hey guys,

Seeing the challenge TheMachine02 shamelessly sent me (), I wanted to try and do some 3D, but this time without defining any vertex by advance. So this came out.

What it features :

• 3D graphing of any function that only involves integer maths (8.8 maths are coming, maybe) on the [-6,6] range (13*9 = 117 dots)
• Dynamic movement around the graphed function : translation, rotation around the Y axis and zooming in/out
• Dots and grid view
• Clipped line routine !
• Support for animated functions. More on that below
• All of that in less than 2400 bytes of pure Axe !

So yeah, it's not really useful, but I found that it would be cool to try and do such program.

Small precision : the graphed function doesn't give exact results. I mean, there's no such thing as units. The only point of that is making good-looking results on-screen, it's not a mathematics tool.

How to use it : by default, prgmDOTSURF (Noshell executable) will graph the 2x² function. You can move around the graphed function with the arrows, zoom in with + and out with -, rotate left with [Y=] and rotate right with [graph], switch between dots and grid view with [mode] and exit with [clear].

You can also define your own function for the program to graph. To do that, just edit prgmFUNC3D. While I'm speaking about a "function", this is actually Axe code that you'll have to compile. I want to make this into a more user-friendly way, but I still have to figure how. Here're instructions on how you can define your function :

• The graphed function is f(x,z) = y. X and Z of the current point are passed respectively in r₂ and r₃, from -6 to 6 and -4 to 4 respectively. You are free to use these, but they must remain the same value at the beginning and the end of your function. They are used for the drawing code. Also, store the resulting Y coordinate into r₆. Do not use Return.
• You cannot edit any of the following variables, meaning that they must have the same value before and after your function : r₂, r₃, r₄, A, B, C, D, E, F, H, V, Y, Z, ?. Also, you can't use any of the bytes from L₁ to L₁+702, nor the 256 first bytes of L₃.
• If you want to use trig, do not use Axe's sin/cos functions, but type Sin() and Cos() instead. Those are way faster, LUT-based routines that I made. Remember that this will destroy r₁, unless you call it with sub(Sin) or sub(Cos) and writing the value right before it. Those functions still returns the same output as Axe's ones. Also, Y holds the current Y rotation angle.
• You can write animated functions : the O variable is a timer that gets incremented by 16 every frame. You are free to use it.

Remember that grid mode will lag a lot at 6MHz, since the program has to draw a line between each of the 117 dots.

So, I think that's all. For those who don't know Axe but want to try anyway, I give you some functions that you can copy in prgmFUNC3D (that will also be an example for those who want to write their own ) :

The default 2x² :
r₂*r₂*2?r₆

One of my favourite functions (also, one that demonstrates well the clipped line routine), the good old x³ :
r₂*r₂*r₂?r₆

Some animated sinusoidal function :
Sin(r₂*16+O)//4?r₆

More animated sinusoidal function to demonstrate the use of both X and Z coordinates to generate Y :
Sin(r₂*16+O)+Cos(r₃*16+O)//4?r₆

Here's a little screenshot that describes the process of drawing 2x² and navigating around the graphed function (at 6MHz of course) :



Don't be horrified by the how-so non-user-friendly interface, I'm working on it

prgmFUNC3D is the program you have to edit to write your own function, prgmSINE3D is the source to compile, and prgmDOTSURF is the executable (here, it contains the 2x² default function).

Feel free to make functions, share them with others if you want, and don't hesitate to ask if you have questions

Idea: Try to collect data from TI variables (like lists or matrices), and parse them for a better experience. I would see a Basic routine that would make the data and the Axe one to show them!

Yes, but IF you manage to parse the data in a variable, you could avoid stocking pretederminated functions/results and rcompiling for each function!

^That was I thought.

Very good job Matrefeytontias. If you switch to 15 MHz projects one day, will Super Mario 64 be next?

Yeah true lol. I wonder if in a few years his classes will ever switch to newer models, especially now that the 82 Stats.Fr got discontinued? The 83 Plus.Fr that is now sold in stores has 84+ hardware. Or does he live in a very poor area of France? Over here, when I went to hi school until 2003, many people still had TI-80s or the old rectangular TI-82's.

Bump :

Who said it was hard to write an equation parser ?

This is 6MHz :



And this is 15MHz :



I don't release anything for now because I want to get number parsing working first.

Well, it does the same thing but less good