v0.995

new features:
pause function

changes:
restructured a lot of internal code flow/addresses
horizon line bug and invisible cube bugs fixed
score increments by 1 as opposed to 2

screenies show difference between the speed at 2000 and at the beginning (I think DJ, you wanted to see this?) This will probably be changed as the current difficulty curve is a little...flat...

I try.

Well DJ, in the next update you'll have to divide all your scores by 2 since I took ztrumpet's suggestion and made the score increase by 1 per frame instead of 2

I tried the alternate pause idiom, and the difference in the grayscale quality is negligible. I also went as far modifying the engine to use only L1 and using interrupts to try and get the gray better, with no luck

The gray is acceptable quality imo, especially since they are only squares. Just think of it as a dithered gray as opposed to a true gray

edit:

I suggest always keeping the number of DispGraph^rs per iteration to be an odd number.  For example, look at the source to my Axe Snake.  The variable I use to control my For( loop is R.

There are actually 2 dispgraph^r's per frame. It looks better this way I think (not sure though) that this is because since everything moves every frame, I have it dispgraph^r twice per frame for the proper gray effect.

or maybe the european pepole weren't supposed to announce it yet....?

yeah, sircmpwn suggested that earlier. I didn't feel like it helped a whole lot, but that was with the 4 lvl gray. I think someone said earlier (or in another thread) that the 4 lvl gray timing is weird or something.

I'll look into it.

Horizon line glitch....hmmm. yeah fixable. just a program flow flaw

Another rotated frame....
Possibly...tbh putting in the single rotated frames was actually really annoying (this is why it took so long for this update )
but now that that part of the engine works adding a second set of frames shouldn't be too difficult.
By 15 degrees do you mean a less-rotated-than-the-current-rotated sprite?

This is 83+ speed 6MHz with a :Pause 100-(score/20) built into the loop

Pause: sure
Score by 1: perhaps...but yeah, probably
Source in 1.0: yes

Quick question: Is this:
min→{L1+A}
While {L1+A}<max
{L1+A}+1→{L1+A}
<code>
End

faster than:

For(Var, min, max)
<code>
End

?