Omnimaga

Calculator Community => Completed => Major Community Projects => nDoom => Topic started by: DJ Omnimaga on February 23, 2011, 04:04:42 pm

Title: Post nDoom bug reports here.
Post by: DJ Omnimaga on February 23, 2011, 04:04:42 pm
I think it would be a good idea to have a bug reports thread for nDoom so it's easier to find them as they are in one place.

In my case, under OS 2.0.1 with Ndless 2.0, TI-Nspire Clickpad, after 4 minutes of gameplay, game will freeze out of nowhere. By then I am around stage 2. I used the official WAD file included with the game, because with the nspire one it froze 3 minutes earlier like in my video.
Title: Re: Post nDoom bug reports here.
Post by: jbaem on February 25, 2011, 04:32:37 pm
ok, well:
i tried to play on os 1.7.xxc with ndless 2.0 for 1.7, but the following errors occur:

1." FUCK! W_InitFiles: no files found"

2."FUCK! Couldn't allocate lumpcache"

and when i try to open it again, my calc crashes and reboots...
Title: Re: Post nDoom bug reports here.
Post by: apcalc on February 25, 2011, 04:34:07 pm
I don't think nDoom works on OS 1.7; I got the same bugs, but everything works fine in OS 2.0. :(
Title: Re: Post nDoom bug reports here.
Post by: DJ Omnimaga on February 25, 2011, 09:12:58 pm
New bug report under Ndless 2.0 beta (OS 2.0.1): Game freezes if you shoot while moving.
Title: Re: Post nDoom bug reports here.
Post by: Mrakoplaz on February 26, 2011, 07:48:26 am
OK, this is getting weirder and weirder... I have no idea where the hell are all these bugs coming from! I haven't seen a single crash while testing on my calculator...

Hmm, now that I think about it, I think I've compiled the executable with a slightly older revision of Ndless (definitely not the beta revision!). Could someone check if you get different/less crashes depending on what revision of Ndless you are running?

I wonder if this is also the source of the "crash on 1.7" bug... since the Ndless for that version would have been different again.
Title: Re: Post nDoom bug reports here.
Post by: ruler501 on February 26, 2011, 08:26:39 am
I get bugs when I try to play a custom wad files. I renamed it doom2.wad.tns When I tried to load your original program it popped up a strange error message and my calculator rebooted. Is there currently support for custom wad files?
Title: Re: Post nDoom bug reports here.
Post by: jbaem on February 26, 2011, 02:18:58 pm
@Mrakoplaz: couldn't you try to compile it with the latest version of ndless again??
and then upload it in one package along with the version of ndless you used to compile it?? that'd be rly helpful, but nevertheless, awesome work!
Title: Re: Post nDoom bug reports here.
Post by: DJ Omnimaga on February 26, 2011, 02:39:33 pm
Yeah ExtendeD told people to re-compile with the latest version.

However, I suspect different hardwares or something. You would need to have someone go through the entire source to help spotting bugs, I think.
Title: Re: Post nDoom bug reports here.
Post by: Mrakoplaz on February 28, 2011, 01:54:43 pm
OK, I've recompiled with the latest version of Ndless. Unfortunately, I won't be here until next week, as I'll be taking part in the Model European Council in Varese. I do hope that this will fix it, and am hoping it really isn't different hardware, which would be really annoying, to say the least.
Title: Re: Post nDoom bug reports here.
Post by: fb39ca4 on February 28, 2011, 04:21:38 pm
ok, well:
i tried to play on os 1.7.xxc with ndless 2.0 for 1.7, but the following errors occur:

1." FUCK! W_InitFiles: no files found"

2."FUCK! Couldn't allocate lumpcache"

and when i try to open it again, my calc crashes and reboots...

Nice error messages lol!

I am getting the random freezes on my calc like DJ has, but on the emulator, it doesn't freeze. Both are running Os 2.0.1.60
Title: Re: Post nDoom bug reports here.
Post by: sodium.777 on February 28, 2011, 06:28:59 pm
will halodoom.wads work on this?
i cant wait to pwn some elite with master cheif on my calc :D
Title: Re: Post nDoom bug reports here.
Post by: DJ Omnimaga on March 01, 2011, 03:14:34 pm
Unfortunately WAD support isn't present yet. I tried renaming a Mario WAD to the same as the default one and it froze on the loading screen.

Anyway I'll try the new version soon Mraklopaz. Can,t wait for your return. :D
Title: Re: Post nDoom bug reports here.
Post by: sodium.777 on March 02, 2011, 09:00:50 pm
bug on ti nspire cas with the round wheel (i think this is clickpad)
running os 2.0.1 game runs fine no freezes anything
the problem is when i quit thegame
the key is ENTER, and since you pressed enter to get into the game, it just goes into it again. the only way i can get out of this loop is to press up or down immediately after quitting the game. it still opens whatever document the file viewer has below or above the ndoom file
Title: Re: Post nDoom bug reports here.
Post by: Scipi on March 02, 2011, 10:00:15 pm
bug on ti nspire cas with the round wheel (i think this is clickpad)
running os 2.0.1 game runs fine no freezes anything
the problem is when i quit thegame
the key is ENTER, and since you pressed enter to get into the game, it just goes into it again. the only way i can get out of this loop is to press up or down immediately after quitting the game. it still opens whatever document the file viewer has below or above the ndoom file

I can add on to this, after a few times rerunning the game for me, it freezes at the loading screen.
Title: Re: Post nDoom bug reports here.
Post by: Maizesmagikarp on March 03, 2011, 09:12:36 am
I just upgraded to ndless 1.7, and whenever I try to load nDoom, it cuts to the metal texture screen with the clock, then a black screen until I pull out the batteries and reset.

Great job! But I can't wait until I can actually play Doom...
Title: Re: Post nDoom bug reports here.
Post by: Scipi on March 03, 2011, 04:25:36 pm
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.
Title: Re: Post nDoom bug reports here.
Post by: DJ Omnimaga on March 04, 2011, 02:04:56 am
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.
Title: Re: Post nDoom bug reports here.
Post by: SirCmpwn on March 04, 2011, 07:46:53 pm
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 :P)
Title: Re: Post nDoom bug reports here.
Post by: momrocker on March 06, 2011, 02:50:32 am
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 ;D). However, I did find that I can't move while looking at the map. Was that intended?
Title: Re: Post nDoom bug reports here.
Post by: fb39ca4 on March 06, 2011, 09:43:32 am
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 :P)
Odd. My calc just freezes whenever I try to move forward and strafe at the same time.
Title: Re: Post nDoom bug reports here.
Post by: DJ Omnimaga on March 09, 2011, 03:16:25 am
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 :P)
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 ;D). 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
Title: Re: Post nDoom bug reports here.
Post by: Munchor on March 09, 2011, 05:19:10 am
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
Title: Re: Post nDoom bug reports here.
Post by: momrocker on March 09, 2011, 05:51:49 pm
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.
Title: Re: Post nDoom bug reports here.
Post by: Munchor on March 10, 2011, 03:26:22 pm
It works pretty awesome on the Touchpad, no crash, good speed, +- visibility, I loved it.

Thanks much, it's the flag, button, peeerfect!
Title: Re: Post nDoom bug reports here.
Post by: momrocker on March 11, 2011, 11:28:17 pm
Thanks much, it's the flag, button, peeerfect!

No problem mate.
Title: Re: Post nDoom bug reports here.
Post by: Mrakoplaz on March 14, 2011, 12:48:49 pm
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 :P)
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 :banghead:. 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).
Title: Re: Post nDoom bug reports here.
Post by: DJ Omnimaga on March 14, 2011, 03:11:27 pm
DOOM 2??!??!!?!?? O.O O.O O.O O.O

Anyway welcome back, sorry to hear you're sick :(
Title: Re: Post nDoom bug reports here.
Post by: fb39ca4 on March 14, 2011, 05:30:50 pm
Doom2??? O.o!
Well, the engines are almost the same so why not.
Title: Re: Post nDoom bug reports here.
Post by: Crozone on March 16, 2011, 06:25:44 am
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.