2936: You spend 25 hours per day programming on your calc.

2938: this because programming causes RAM Clears that kills your clock, so you see 25 hours pass

2935: You know QMET

Assume that the SORTD subroutine sorts data in descending order.
I also want to correct something:

Code: [Select]

Data(100^r,90^r,80^r,70^r,60^r,50^r,40^r,30^r,20^r,10^r,0^r)->GDB1HS
.later...
S->{GDB1HS+10}
sub(SORTD,GDB1HS,11)
.assume SORTD is a subroutine. # of items is 11.


But then, a ^r is missing after the S->{GDB1HS+10}
Moreover, no need to make a routine if it is only used once. What I suspect is that you wrote sub(SORTD,GDB1HS,11) to say "you must sort it" without giving the proper code

I personally do it the other way round in MisterOops!
I check how many scores the current score beats, shift them, then insert the new highscore

Yeah I wasn't sure if he was officially switching to a sprite, since the most recent gif still showed a 3D car. I brought it back up in case.

I think that he first works on the hardest parts of his game (making the 3D engine work perfectly) before working on easy parts (make the player a sprite). This would be why the player is still a cube

A sprite would actually be better I think since even Nintendo 64 games used sprites for Mario Kart and the like.

ben, I go with DJ that you should just change the car to a sprite.

I might make the player a sprite, so then it should be possible to show a different sprite when an arrow is pressed

Strange, I use Ndless r632 too and Critor's program works

There is already a similar topic here.

One of my friend had this problem too with his black 83+. So if your 83+ is black, maybe it is a hardware problem.
Now the stupid question I'll ask seems less stupid: What color is your 83+ ?

Also hopefully the standard PRIZM calculator keypad makes the game easier to play than on a TI-Nspire (clickpad/touchpad controls were annoying and the numpad, which was an alternative, was too far at the bottom of the calc)

It depends on how you play with it. Personally, I put my Nspire on a table and then, the touchpad is very easy to use. But I agree that if the calculator is not on a table, it is impossible. Keys are too centered to be easily accessible*.
But playing with a clickable touchpad allows to run normally and to run faster when clicking

(* Is the correct word accessible or accessable ?)