Cool ^^

Also, anybody tell me if you reach 60 seconds, because then c gets real

Thanks, I hope to have much of it

Also, I took an actual screenshot of the gameplay for ticalc :

Yeah, I wanted it to be enjoyable while remaining a small project that I don't want to spend more than a month on challenge successful, yeah ?

Release time !

So instead of talking to describe it, I'll just post it and you try it but you still get a screenshot of the new title screen.



Here you go for now, while it gets approved at ticalc : http://www.mirari.fr/PJ06

Even if it's true, don't do that. That's horrible.

I meant, are they drawn as many, many lines too ? Because at that point, filling a polygon would probably be faster.

Even the big walls at 1 minute in the video ?

I planned to send him one for Axagon, I can mention + link yours in it too if you want.

Congratulations, it looks awesome also, you see you're using a 25 MHz CPU when you have an actual polygon filling routine. One has yet to be written for the 83+, and I don't think the performances would be that good.

TI-Nspire, Casio and HP support is absolutely impossible (different CPUs mean different ASM languages). Actually, I'm sorry but nearly 0% of what you proposed is even conceivable. Though, there could be a way to make Axe programs compatible with the CSE without too much work (it's still much work, but you're not rewriting the whole app). Basically, when compiling for the CSE, the following has to be taken care of :

• BCALLs addresses vary between models.
• RAM areas base addresses too.
• DispGraph and friends have to be rewritten entirely for the CSE, and a special screen initialization and clean-up code must be put at the beginning and the end of the program. Fortunately, all of this already exists in a 100% usable form in the CSE version of KnightOS (here's what I'm talking about : setLegacyMode, resetLegacyMode and fastCopy respectively).
• Z-Interval changes behavior and scrolls the screen horizontally. Of course, it needs to be rewritten. Actually, it's probably best left unsupported since the 96*64 virtual screen won't fit in the whole 320*240 physical screen, so it's gonna be ugly if the whole physical screen scrolls.

No other change should have to be done unless I forgot something. The areas used through L1-L6 on monochrome calcs still exist on the CSE AFAIK.

The only real difficulty would then to make the app choose between monochrome and CSE versions of certain routines which needs platform-specific code. I say it's a difficulty because the two pages Axe takes are getting pretty full already.

Yeeee let's do a featuring one day

Need I say more ?

Alright, apparently there's that trend of introducing yourself over and over

I'm matrefeytontias, also known as matref since people can't write my full name right. I'm French, 17, and I started programming at 10 (it's going to be my job, I guarantee you) with C and later C++. One day I stumbled upon that Axe tutorial by Kindermoumoute I later helped redacted, then I decided to wait for highschool and buy an 83+ to do Axe 'cause it's awesome. Hell I did. Later I started programming for the TI-Nspire with C/C++ for Ndless. I like to believe I'm quite good at Axe and ASM for the 83+/84+ and C/C++ for the Nspire.

You might know me for having written games such as Jetpack 8x+, Gravity Walls, Super Crate Box (only the calc version duh), IkarugaX, nKaruga, nSpeedX 3D and some other little things ; and utilities (mostly axioms) such as AxeJh3D, AxeDCS and WiredWorks. 5 of them were featured on ticalc, and all of them can be found there on my profile page.

So yeah, let's see what you guys have got. 

Dammit, one more week before results

So yeah, back on topic. Collisions are implemented, next is scoring. Aaand I actually want to bring it a little further afterwards, so we'll see about that when the time comes :3 (I also have to do a titlescreen first).

Well yeah, that "angle" is called a polar coordinate. I'm applying this technique, because everybody would.