NESpire general discussion thread

[Goplat]

Here's a new version. With touchpad support (I can finally play it on my own calculator ) and source code included.

[momrocker]

Sweet!

Any new features other than touchpad support?

[Goplat]

No, that's all for now.

[momrocker]

Sounds good. Also nice that I can finally play this on my calc, always been jealous of my friend with his clickpad

[Deep Toaster]

Here's a new version. With touchpad support (I can finally play it on my own calculator ) and source code included.

You couldn't even play with your own program?

This is a great update, though! It's been a long time since I've updated, but I'll get this as soon as I get nspire_emu working

[DJ Omnimaga]

I'M glad this is not dead Goplat.

[ase1590]

and source code included.

Nice!

[aeTIos]

That is not emulating, that is a built-in 3d, a raycaster. That is even done on a 84+

welcome here, though! hope you enjoy your stay!

[Builderboy]

That is not emulating, that is a built-in 3d, a raycaster. That is even done on a 84+

Well, its a port, so not quite emulating, more like running the same code on the nSpire (with a few modifications).  And that isn't a raycasting engine Doom uses, its a different engine that would definitely not be able to run on an 84 at full speed with textures.

[DJ Omnimaga]

Heya welcome here macweirdo! And yeah emulating another processor takes a considerable amount of CPU power, so this is why 3D emulation would be hard. For example, the SNES Doom would run slower on the TI-Nspire than the TI-Nspire port.

[fb39ca4]

There is SNES Doom? Or are you talking about SNES Wolfenstein?

[mSuman95]

  Nice App. This is truly amazing. +1 Internets to you.

  I seem to have an issue with the frame limiter, though. Games seem to be running slower than usual (50-65% speed?) with it on; whilst suppressing the "x" key to turn it off makes it way (250-300%) too fast. Is there we could change the value of this with a hex editor, or directly to the newly recovered source code?

  Once again, this app is brilliant!!! I have yet to find any bugs at all. Keep up the good work.

[Goplat]

It seems to run at the correct speed for me. What OS version are you using? Does the problem still happen if you reboot and don't run any other Ndless programs before running the game?

[mSuman95]

Hey Goplat.

I'm currently running TI-OS 2.1.0.631, the latest if memory serves me right. As per your advise, I'd rebooted the OS entirely, via a prolonged removal of battery power. Despite my supposed labeling as a TI newfag, "turning it off and on again" had solved my tedious speed problem entirely.

Although a reboot had solved this, It was after-all, only temporary. Running differing ndless applications (as you had mentioned) prior to NESpire, including mViewer and GBC4Nspire, had left NESpire subject to terrible speed problems afterwards (or at least in my current trials). Could I assume that NESpire uses a DO, LOOP function (or its C counterpart) to limit frames, as opposed to a time based one such as SLEEP; applications had most likely been running unclosed in the background, or alternatively left a large portions of data to eat away my RAM.

Thanks for the reboot suggestion, by the way. It works wonders! 

PS: Sorry for the late post. I've just returned from dinner.

[Goplat]

I use the 900D0000 timer, which the OS sets to 100Hz (well, actually more like 99.3Hz). Running 3 frames every 5 timer ticks gives a speed close to the NES's 60.1Hz.

I suspect some program is changing the timer speed and not putting it back.

EDIT: Yep, it's gbc4nspire. Use this program to restore the timer speed after running it.