Here is today's build. I've fixed level transition (however, level 2 has a big bug in the rendering, so this fix isn't very useful yet), added controls for contrast (plus/minus), an experimental alternate mapping for the Clickpad (I don't have one, so I have no idea about the ergonomics), and also changed the loader so that it looks for the WAD files in the current folder, and not necessarily the root.
I've also fixed another bug with the textures (which I accidentally introduced while debugging the last texture problem ), and the game looks even better now. Also, switches are no longer invisible:



Unfortunately, the reboot-on-quit bug ("Error at PC=FFFFFFFE: J mode is not implemented" in the emulator console) is still present - that, along with the rendering bug of level 2, are the top priorities for the next release. Hopefully I'll also have time to improve the HUD, so that you can tell the difference between picking up an item and taking damage.

For experimentation, I've also swapped the strafe/turn keys around. I'm not sure if it's an improvement in ergonomics or a step back, though.

Quote from: DJ Omnimaga on January 04, 2011, 03:54:09 pm

I checked the new screenshot and it's awesome. How many levels of gray do you use by the way now? In the screenshot I only see 4 or 5 but I'm not sure if it's due to CalcCapture, low contrast or something else.

Thanks - it's supposed to use all sixteen shades, but I still have to shuffle the palette around a bit to spread the colours out and such. I think I screwed up on a couple of values while typing out the 256 bytes manually in hex...

PS: Yay! I just noticed I can upload files now. Both source and compiled version included

What formula are you using to convert the colos into grayscale?
Ive used 5/16 green and 3/16 for red and blue.

I've been looking into the crash-on-quit bug and it's driving me crazy. It always seems to crash after main() returns, which might indicate a fault with Ndless, but no other programs (that I know of) crash on exit, making it obvious that the problem is related to Doom in some way. Problem is, in what way? I've been looking at the Ndless sources, but still don't understand most of them, especially the assembly bits, so I can't really help there, sorry.

It might be related (or not) to what Mrakoplaz has reported previously, but I've got something interesting.
mViewer is quite stable with Ndless 1.7, on non-CAS calculators, or even with Ndless 2.0 on non-CAS calculators.
I've got problems with the same binaries with Ndless 2.0 on a CAS ClickPad.
After exiting mViewer, the calculator does freeze or reboot very often (which does not happen on the non-CAS).

Now that is interesting. Could it be to do with the sheer amounts of memory required by the programs? I mean, mViewer can load quite large .bmps and similar, can it not? Whereas Doom allocates more than six megabytes to itself...
Also, it crashes on my Touchpad 100% of the time as well, so it's not related to you using a Clickpad.

And sorry about the file uploads restriction, this was to protect the forums from spambots that uploaded adult material.

Hey, most forums don't let you upload files at all, so I view this more as a bonus than a limitation.

What formula are you using to convert the colos into grayscale?
Ive used 5/16 green and 3/16 for red and blue.

I've used the dumb-dumb idiot formula - take screenshot of game palette, load it into picture editor, click "make grayscale" button, select the "colour picker" tool, hover mouse over each field of the palette, type result into array. One of the dumber things I've done, but hey, it was the first time doing something like this, and it seemed to work

Quote

Actually, for all the Nspire stuff, it would be ideal to have an svn host dedicated to hosting Nspire. Such as someone here setting up their webserver for that.

What would you think of this? http://nspforge.unsads.com/

Sounds like a good idea, but unfortunately I absolutely despise all sorts of version control, from SVN to Git (Git more than the others, though). I agree they are critical for team projects, and that the only reason I don't like them is because I don't understand them... but that doesn't change the fact I hate them. I do backups manually, I track bugs with one .txt file, and progress/goals with a second one (whee! I am not even in university and already old-fashioned!).
Since they are very useful for about everyone else, however, good work! This will probably make it easier for others to start/track development.

To everyone else, I'm sorry but there's been no progress - I've been trying to track down the rendering issues in level two as well as the crash on exit, but found nothing so far. Also, further progress will slow down as holidays are ending. Hopefully though, nDoom will be in an acceptable state soon - apart from the rendering issues of level 2 and incomplete interface, it seems relatively playable.
I must point out though, my thanks to everyone for such encouraging feedback! I am not sure I'd be willing to spend twelve hours tracking down rendering bugs if it wasn't for this welcoming community; Since I only have an Nspire (and no TI84 keyboard), I can't really try many of your projects (and I've seen some really epic ones here, especially considering the relative simplicity of the hardware!), for which I apologize. Yet, this community has been so welcoming that I feel obligated to stay and somehow repay that... don't worry, I'll figure something out.

Also, while playing on the real calculator, I've noticed how the blurry display forces a very different playstyle on you; Instead of the good ol' run-and-gun of the original, you instead are slowly advancing, checking behind each corner, darting from cover to cover, etc. Interesting how the hardware changes things so much.

PS: Anyone tried the Clickpad controls? Are they absolutely horrible, or just subpar? Since I don't have one, I was working off a blurry picture of the keypad and couldn't do any practical tests.

mViewer is quite stable with Ndless 1.7, on non-CAS calculators, or even with Ndless 2.0 on non-CAS calculators.
I've got problems with the same binaries with Ndless 2.0 on a CAS ClickPad.
After exiting mViewer, the calculator does freeze or reboot very often (which does not happen on the non-CAS).

So may be there is a wrong address for a 2.0 CAS syscall, I'll try to find it. Tell me if you happen to have an idea on which one it could be.

Please excuse my ignorance, but will 1.7 programs work on 2.0, because I'd love to try this, but I want to use gbc4nspire as well.

Win.  Once I get my nspire back, I'll definitely be upgrading.

A

Quote from: apcalc on January 06, 2011, 06:22:47 pm

Quote from: SirCmpwn on January 06, 2011, 05:21:07 pm

Please excuse my ignorance, but will 1.7 programs work on 2.0, because I'd love to try this, but I want to use gbc4nspire as well.

Yep!

All Ndless 1.7 programs are compatible with Ndless 2.0, with the reverse of this also being true (unless the touchpad keypad is being used; this may cause some problems with Ndless 1.7 programs with Ndless 2.0)!

Are you sure ndless 2.0 progs work on 1.7? I just get a reboot when I run ndoom.

I think it's that 1.7 progs work on 2.0, reverse order

at least I think that's what he meant.

Read carefully, and you'll notice apcalc said "the reverse is also true"