Weird, I am using FireFox 27.0.1, and am currently seeing this problem on Windows 8 (not 8.1).

Some random optimizations I saw when looking at your code.

At the beginning, you have (among other affectations)
0→B
0→G
which can be optimized as 0→B→G

Below, you have
Repeat (getKey) and (getKey(9))
 If getKey(15)
  Goto END
 End
End
which can be written without external parentheses around "getKey", and I also think that
While 1
End!If getKey-9 and (-6→r1)
!If r1
 Goto END
End
works the same but is better.

If A>4000
0→A
0→B
End
can be written
If A>4000
 and 0→A→B
End
because A>4000 equals one if we enter the If, and 1<256 so A>4000 and 0 equals 0.

If getKey(9)
B--
Else
B++
End
can be written getKey(9)?B--,B++ to be more readable, but that doesn't save any space once compiled. But I am sure something like getKey(9)*2-1*~1+B→B can be done. I didn't try though. Note that "~" is the "little minus" sign.

If C=~16 saves space if written !If C+16.
Same for If D=~16.

I am pretty sure that If (C>65527) or (C<19) is the same as If C+9<28.

(A/5)<(F+31) is the same as A/5-F-32<0 but this one doesn't have to save a calculation to recall it later.

In this,
r3/10→r3
End!If r3
You don't have to put "r3" after "End!If".

Return
Return


I didn't try this one (same for the others in fact ) but I think that [/tt]{Y1}-G<0[/tt] is more optimized than G>({Y1}).

Here,
If G>({|Y1})
 SCORE(41,49,G)
Else
 SCORE(41,49,{|Y1})
End
DispGraph
If G>({|Y1})
 DelVar "|vIrnPants"
 GetCalc("|vIrnPants",14)->r1
 G->{r1}
 Archive "|vIrnPants"
 GetCalc("|vIrnPants",|Y1)
Else
 Pause 1000
End
DispGraph
You put two times the same If. Either get everything in one, or at least save the result of the calculation in a var and make on If with the calculation, the other one with the var.
I also don't get why there are two DispGraph, both outside all If.

That's all I saw
And once again, I didn't try them, so don't put them all at once, try them one after each other, separately, and be sure that one has not broken anything before trying another

I also noticed that, at the very beginning:
...
A y value
B accel
C counter 1
D counter 2
E pipe 1
F pipe 2
G score
...
You know, you can use variables with custom names in Axe. You just have to do pointer_to_two_bytes_ram_area→°Name_of_var, like for example
L5→°Acceleration
L5+2→°Speed
and then you can do Acceleration+Speed→Speed and whatever you want (just be sure in that case to clean L5 at the end of your program, with a ClrHome).
You can also do °E→°Pipe to rename the E var into Pipe (and then, if you do Pipe after a 1→E, you'll get 1).

If you do it as an app and you want to change the Pic1 var while runtime, you'll need to store to some other variable, like, e.g. A instead.

Pic1 is not a var, it's a pointer. Which is why you "can't" change what it points to when you compile as an app, it points to a byte in ROM. So you'll have to copy what it points to to some place in RAM then you'll be able to modify the content of the copy, but still not what Pic1 points to. And doing Pic1→A is not copying what Pic1 points to "in" A (I don't even know what that would mean), it just gets A to point to the same place as Pic1 points to (so if you compiled as an app, A points to ROM too).

{R} points to an appvar. Or does R its self point there? Gah! Syntax!
Ok now its

Code: [Select]

asm (EFE542)→O
{R}-O→T
T÷1000→NBut it still doesnt change the display of O.
Edit:
Im useing output(4,5, {R}▶Dec
Edit... again:
I switched {R} to O, and you know what it worked!

If you made a GetCalc(...)→R, then R points to an appvar, and not {R} which is the first byte in your appvar, so storing in the appvar indeed looks like →{R}, except when you have two bytes to store, which is likely if you have more than 255 bytes of free RAM, and in that case you have to use →{R}^r (and be sure that your appvar has a length of 2 at least, and that you won't store anything else in {R+1}).

Many people already made their version of a Flappy Bird clone. So I thought "why not me too ?"
I think it is useless for me to explain the gameplay, it's in every other topic. So I guess it's just screenshot time (6MHz, as usual).


As you can see, collision detection is missing and the game needs a menu and such things so no release for now. I'd also like to optimize it a bit so you'll have to wait
Anyways, tell me what you think of it

Download here

Haha ! Bulbasaur Lvl 35 in Pallet Town

Does this require a specific (as in "not too old") revision of Ndless ? Because I can run nCraft but not crafti ("not supported").
And yeah, I have a really old revision

edit Indeed, works with r914.
However, I only figured out part of the controls, and my calc froze at some point

Great job other than that