v1.1 is out. It has full compatibility with the 83+BE. (At least I hope it does, my current version of wabbitemu can't load apps. So I couldn't test it.) It also is perfectly timed with the music.

Anyways, to give you an idea of how long till I make v2.0. I am 93% of the way through beat level 2 and 69% through level 3. So a few more days

v1.1 is out. It has full compatibility with the 83+BE. (At least I hope it does, my current version of wabbitemu can't load apps. So I couldn't test it.) It also is perfectly timed with the music.

Anyways, to give you an idea of how long till I make v2.0. I am 93% of the way through beat level 2 and 69% through level 3. So a few more days

Nice to hear! I'll try 1.1 soon. Can't wait for 2.0. Glad you're back into coding

I think that's DCS-related, and not specifically thepenguin77's fault.
Will play

Just as a heads up, I am starting on 2.0. From the looks of it, it should work on 83+'s. At 33 fps and 6,500,000 Hz, thats 200,000 t-states per frame. The screen will steal 60,000 and with my new system of drawing the screen (sprites vs. just pure shifting), it should take 20,000 to render. That leaves me with 120,000 to mess around with, meaning that I should definitely be able to make it work.

I think that's DCS-related, and not specifically thepenguin77's fault.

Lol, I am like DCS's worst nightmare. This is the third time I have made it glitch with this program. First it was the crash on exit (extra ram related), then it was the upside down screen (memory usage differences), and now it is the stats screen crashing (something to do with mirage's fastLine I assume). Oh well, kerm needs something to work on.


Btw, I never finished level 3. I got to 93% several times. The problem is that at 84%, there is a section that has only one frame that you are allowed to jump from. That coupled with this being the hardest level ever have stumped me. Oh well, mine will have more than one frame of success.

sounds good. 1.0 is already a classic around my campus =D
btw, was there some specific reason that you werent using sprites before now?

btw, was there some specific reason that you werent using sprites before now?

I wasn't using sprites because the way sprites are typically done, I thought it would have taken too long to draw all of them to the screen. I originally thought it would have to run at 50 fps also which makes sprites impractical. The way I'm doing them this time though is to have separate code for each possible alignment on screen. This configuration will take up 260 bytes in ram vs none, but the result is about twice as fast.

hmm, i did much the same thing for several smooth scrolling xlib games. playability on the 83+ is definitely worth a few extra bytes.

Agreed

Mhmm maybe it's due to the LCD blur or something, or collision detection is out-of-sync with the display