Looks nice

MGOS, did you plan to add transitions when passing the corners ?

And Art_of_camelot, beware the double-posting

Well, if you look at ant of my other posts, you'll see me keep asking if someone can help me >.<

So let's say it again : there indeed is a problem in the actual game engine (by that I mean not in the menu). The program has different behaviors depending on the execution method, and always occuring after the exit : compiled as an app, it leaves weird characters on the homescreen ; compiled in Noshell, it messes with the random-related functions and makes them display huge numbers (it starts at 10³² and slowly go back to their initial range as you run it again and again), and moreover it displays a random ERROR:something 1 time out of 3 ; and compiled for MirageOS, it constantly crashes.

I can't release the actual source (I'm on a phone) but I have them on my computer, so I'll upload them tomorrow (it's 11:06 pm here).

Yeah, I was thinking of this one, but still I'm not sure it'll be possible, excepting maybe with a hell-optimized ASM raycaster. I'm pretty sure that polygon- or vertices-based engines can only be too slow for a game like that on handhelds like the z80 ones.

I'm deciding to port VVVVVV to the TI-84! (The Portal clone is currently on standstill, but it SHOULD be back in progress soon!)

Only to 84+ ? And what Portal clone ?

The steps are as follows :

• Create your appvar using GetCalc(appvarName,size), where in this case size should be 768 since you want to store L₁ which is 768 bytes large. The GetCalc function returns a pointer on the appvar, so keep it in a variable.
  Example : you want to create the appvar called LIST which is 768 bytes large and to store his address into P. You'll do something like :GetCalc("appvLIST",768)→P. Don't forget that "appv" must not be typed by hand, but by pressing [2nd] [8].
• Use Copy(pointer1, pointer2,size) to copy the 'size'th first bytes starting at 'pointer1' into the 'size'th first bytes starting at 'pointer2'.
  In this case, since you want to copy the first 768 bytes from L₁ to your appvar P, you'll do Copy(L₁,P,768). But if you don't specify any size, Axe will automatically make it 768, so you can also optimize this line by Copy(L₁,P).

That's all, if you don't understand something just ask

Heya people,

Yesterday, I was working on Super Crate Box again, and all was good until I saw that I forgot to write something on the really last line of the biggest program (which was 481 lines long). So I got lazy and thank about how to go to the bottom of a program with one key.

And I found : this small hex program installs a key hook that will make the cursor go at the very last character of the current editing session (also works with the homescreen) by accessing the Link menu ([2nd] [x,t,Θ,n]). Don't worry about the menu being inaccessible, you can still disable the hook by accessing the Calc menu ([2nd] [trace]). To re-enable it, just execute the program once again.

:AsmPrgm
:21A99D
:110080
:011900
:EDB0
:210080
:3E01
:EF664F
:C9
:83
:FDCB0156
:C8
:FE41
:2006
:EF5D49
:3E00
:C9
:FE3B
:C0
:EF6F4F
:3E00
:C9



Share comments

@DJ_O but it wasn't that great of a surprise,was it ?

@Keoni29 forget about it. I don't remember who made it, but only filling the entire screen with the same color (and not doing anything else in the loop !) allows for a maximum of 6-7 fps. If a game like that were to be made on the 84+CSE, it would most likely only take half or a quarter of the screen to have a correct speed.

Metroid fusion to calc ? o_o'

Might be pretty hard, but hoooow much fun to play it