I'm writing a clone of the iphone game Line Runner. It works but I'll need to implement and improve a lot of things, for example better graphics. The CX isn't supported yet because I don't have one to test and I didn't have time to read everything about how to use the ndless functions for this.

Does anyone know why the nspire emulator gets a totally different speed if I use idle()? And even more different if I let the fast timer run? On calc it's too fast and on emulator it's so slow you can't play.

newest version

The only way to make it blur less on the old Nspires is to reduce the framerate to under 15 fps. There,s no way to remove the blur itself and framerate has to be reduced to keep the game playable.

I should give this a try to see if it works.

Am I right that I can't use the emulator to emulate a cx without boot1?

Right, TI found it smart to make the CX (and probably CM) series' boot2 not entirely executable after decompression.

it's not finished right? it only shows 3 blocks to jump over, and 1 to get under... then there's nothing

oh, and there's an error each time i exit the program, here's a pic: (cx cas)


and maybe it might be more useful to use up and down instread of left and right, it will be more intuïtive..

Ok, new version:

• -Up and down are also supported. Do you think I should remove left and right?
• -I've put a lcd_incolor() at the end of the code, maybe this fixes Nick's issue
• -The level is more varied (I think that the only 2 blocks problem was that there was only empty space for a long time after, since it was randomly generated)
• -Changed rolling
• -Added simple score

idle() puts the CPU into idle mode until the next interrupt. If you change to timer's frequency, idle()'s execution time will change.
But with throttle mode on, the experience should be the same on nspire_emu and on real hardware. Maybe you should post the source code if you want someone to review the code to check what could be wrong.

It was the same experience with throttle mode off, else it was far too slow. I think now it's better, but I can't test it on my calc because the batteries are empty. Is it a good idea to use set_cpu_speed(CPU_SPEED_90MHZ) to slow it down (I restore it at the end)?

The source code is included in the zip file. But it's not very well commented.

Do I have to use lcd_incolor() at the end if I have lcd_ingray() at the beginning?

Edit: It should be less blurry now since I skip half of the frames on monochrome nspires.

Wow the exit glitch was quite scary (see video attached to post below). The game seems kinda nice so far, though. More speed like in The Impossible Game (I lost) would be nice, though.

I think I've fixed everything except the blur in this new version:
- removed set_cpu_speed()
- removed direct use of timers
- changed rolling again
- faster, more difficult
- getting faster when you reach certain points

I don,t think you can do anything about the blur. Blame TI for that.

I wonder if you will add variable platform heights, with hills and stuff, along with holes?