What you can do is "inflate" the value to get more accuracy.  256 is a great number since it's very optimized in both division and multiplication.  Since Axe variables hold 16-bit numbers, you can use the lower byte as the decimal and the higher byte as the number.  9.8 can be represented by 9 + 205/256.  You get your inflated number by multiplying by 256 so that's 9*256 + 205 = 2509 == 9.8 as an inflated decimal.  You can treat this number like any other number.  If you add 1 to it, you're really adding 1/256th and adding 256 is like adding 1, etc.  When it comes time to display the point, just divide by 256 so that you recover the integer part for the pixel.  So you're doing math with the precision of 1/256th and then just drawing it to the nearest pixel.

EDIT: Damn!  I knew I'd be ninja'd

but wont it wrap around to 65536 since Axe is 16bit?

But axe variables are 16bit by nature

Code: [Select]

.AA
ClrDraw
47->X
5->Y
0->V
Rect(0, 60, 96, 4)
For(A, 0, 200)
DispGraph
V-9.8->V
Y+V->Y
Pxl-On(X,Y)
Pause
If Y+2V>60
-V->V
End
End

Just wanted to point out some other things that you might want to change.  First off, there is no Implied multiplication in Axe, so things like 2V dont wok.  You need to do 2*V.  Secondly, there is no PEMDAS, everything is evaluated left to right.  So Y+2*V is really (Y+2)*V.  You should change it to V*2+Y.

Also, note that your initial velocity is 0, and then you Subtract 9 from it, making it negative.  This moves your pixel *up*, not down.  And whats more is that it will keep moving up indefinitely because you are waiting for it to go below the screen, but it just went off the top.

As for gravity, how it is done is simple.  There is a variable for velocity for each object, and ever frame, the position is incremented by the velocity, and the velocity is incremented by the acceleration.  For a deeper explanation you might want to check out my tutorial on Gravity and Acceleration over here: http://ourl.ca/4279

What you want is the initial conditions 47*256→X and 32*256→Y, and then use code like the following:

While 1
X+U→X
Y+V→Y
Pt-On(X/256, Y/256, Pic1)
End

I think I'll revive this thread...  with a new question!

I've tried using 'input' on Axe 0.4.4, but it keeps spewing this weird string of characters at the start.  I've attached a gif that shows what I'm talking about.
This is my code:
.INPUT
ClrHome
input->A
Disp A,i            //The i is the imaginary i for newline
Repeat getKey
End

What am I doing wrong, and how can I get rid of that string at the start?

That shouldn't be happening.  Is anyone else getting that?