Post nDoom bug reports here.

[Scipi]

New bug report under Ndless 2.0 beta (OS 2.0.1): Game freezes if you shoot while moving.

On the same OS I found that it only freezes if you are moving forward. Backwards, strafing, and turning are all fine.

[DJ Omnimaga]

Really? I guess it might be because I was moving forward everytime.

Hopefully he can manage to fix this when he returns, or maybe someone else could help with the code.

[SirCmpwn]

Using several means of input at once has unforeseen consequences.  For example, strafing right while moving forward loads the quick save (which pissed me off quite a bit when it happened )

[momrocker]

The new re-compile won't allow me to change the contrast on my calc.

Other than that, everything seems normal.

Just noticed you have to press the button over and over again to change, instead of just holding the button down (like in gbc4nspire ). However, I did find that I can't move while looking at the map. Was that intended?

[t0xic_kitt3n]

Using several means of input at once has unforeseen consequences.  For example, strafing right while moving forward loads the quick save (which pissed me off quite a bit when it happened )

Odd. My calc just freezes whenever I try to move forward and strafe at the same time.

[DJ Omnimaga]

Using several means of input at once has unforeseen consequences.  For example, strafing right while moving forward loads the quick save (which pissed me off quite a bit when it happened )

Lol I didn't even realize Quicksave was implemented. By several means of input at once do you mean how the game supports both clickpad and touchpad and have multiple keys assigned to each command?

The new re-compile won't allow me to change the contrast on my calc.

Other than that, everything seems normal.

Just noticed you have to press the button over and over again to change, instead of just holding the button down (like in gbc4nspire ). However, I did find that I can't move while looking at the map. Was that intended?

Yeah I remember wondering about that too. I remember in gbc4nspire contrast changing was ridiculously fast, though. In half a second I could go from lightest to darkest contrast. X.x

[Munchor]

Everything works fine in my calculator except for saving.


How is saving? I press the library button in the third level and then I leave and when I come back I'm in level 1, I don't know how to work this out :S

[momrocker]

How is saving? I press the library button in the third level and then I leave and when I come back I'm in level 1, I don't know how to work this out :S

You click the flag button to load your game. Works like a save state.

Also, I can confirm the crashing glitch on the clickpad. I recently installed ndoom on my friend's clickpad and after about 15 seconds it crashed. Also what was weird was that the intro screen that "bleeds" out lagged a bit, but really that would be the last thing I would think to lag... It required a battery pull afterwards.

[Munchor]

It works pretty awesome on the Touchpad, no crash, good speed, +- visibility, I loved it.

Thanks much, it's the flag, button, peeerfect!

[momrocker]

Thanks much, it's the flag, button, peeerfect!

No problem mate.

[Mrakoplaz]

Yay, I am finally back! Apologies to everyone for this long absence - I actually returned from Varese last Saturday, but first caught an annoying sickness, and then was completely swamped with work (in fact, it's not quite over yet, but at least most of it is now gone - on Sunday, I literally had 6 hours of homework, and that's already having done 2 hours on Saturday).

As for the random crashes on Clickpads and 1,7... I have no idea where on Earth they're coming from. "Couldn't Allocate Lumpcache", for example, is an error that should NEVER happen, since it's just a straightforward malloc(). The random crashes after pressing certain keys, sometimes in combinations, are also very puzzling; There's nothing there that could possibly crash it! It's just straightforward code for shooting and moving!

Sorry for the exclamation marks, but I am rather annoyed by this; Simple code that words perfectly both on the emulator (both in Clickpad and Touchpad modes) and my own calculator, but crashes mysteriously on others. I am quite literally lost, since nothing I myself have, not even the emulator, experiences these bugs.

Using several means of input at once has unforeseen consequences.  For example, strafing right while moving forward loads the quick save (which pissed me off quite a bit when it happened )

Hmm, that's certainly strange, and should not be happening. I thought Nspire keypads were free from these kinds of hardware key conflicts? I certainly haven't experienced anything like that even with the silliest of button combinations.

However, I did find that I can't move while looking at the map. Was that intended?

Actually, that was intended, since there were some minor bugs. I put in a quick hack to disable movement; Moving with the map on doesn't really make sense anyway, since you can't see enemies, and new walls that you haven't previously seen don't get discovered.

And as for "ENTER" being the quit key, and re-running the game after exit?
EPIC FAIL . No other words describe it sufficiently. I'm not quite sure what I was thinking when I made that choice; Or even if I was thinking at all!
Does anyone know how gbc4nspire accesses the ON key? Because being able to use that would be just ideal...

There's a lot of posts, so I apologize if I missed someone (speak up if I did). Please keep the bug reports coming in, especially the random crash ones... maybe eventually, we'll get a pattern to appear.

PS: I'll be adding custom WAD support, and hopefully fixing the Doom2 crash bug next release, as soon as I get the time (although I've gone through the worst of it now, there's still an insane amount of work this year, every single week... add non-calculator activities, and many days there just isn't any time for programming at all).

[DJ Omnimaga]

DOOM 2??!??!!?!??

Anyway welcome back, sorry to hear you're sick

[t0xic_kitt3n]

Doom2??? O.o!
Well, the engines are almost the same so why not.

[Crozone]

Having an interesting bug. I'm on OS 2.1 for the extra clock speed, and nDoom runs far too fast. I have to downclock it with nover to get it to run at the right speed. Any chance of putting in a speed/framerate limiter to a) fix the speed issues and b) help prevent the screen blur?

Also, I'm getting the glitch where you exit and it instantly reloads. You have to hit enter really fast to exit. Anyway, awesome job on this, haven't had any crashes at all!

EDIT: Just tried to strafe and move forward and the game froze....the first time, pressing ENTER returned me back to the menu, and I reloaded nDoom and tried strafe forward again. The second time the game froze, hitting ENTER caused the calculator to reboot. I am on the CAS Clickpad OS 2.1.0.631 with Ndless 2.0 beta.

EDIT 2: Figured out that the problem only occurs when strafing left and moving forward (esc and forward on clickpad). This key combo, for some reason, loads the quicksave. However, if you don't have a quicksave, the key combo crashes the game. I don't even.