3.2 release candidate is upon us!

[d_m]

Originally Posted by Nomad

Incidentally, while I see that the code for my new tile set has been implemented and all seems to be working fine, the actual BMP files aren't included in the zip at the moment.

Sorry about that! This may be a problem with the autobuilder.

Since I don't normally play the windows port (I run it through WINE) can you be specific about which files you expect to see where in the zip file?

Thanks!

[Nomad]

Originally Posted by d_m

Sorry about that! This may be a problem with the autobuilder.

Since I don't normally play the windows port (I run it through WINE) can you be specific about which files you expect to see where in the zip file?

Thanks!

There should be an "8x16.bmp" and "mask8x16.bmp" going into the \lib\xtra\graf directory.

[Lord Fell]

How quickly are bugs being traced and squashed with the 3.2 candidate? Will you post to the thread when a reported bug is fixed?

Also, I'm wondering if my tinkering with yeeks & harpies as playable races will be affected by the 3.2 changes, or if the edit files will keep the same format.

[PowerDiver]

I downloaded, ./autogen.sh, ./configure --with-no-install, compiled, ran, and immediately got an assert error after I "Press any key to continue". A quick look suggests that the problem might be that with no savefile, there is no stack of previous commands. However, I don't see how the money bug described above could happen if the code dies before the birth process.

Is there any likelihood this could be platform specific? Where does that mean I should look? I've never looked at the command code before, so I'd appreciate a hint where to start looking.

angband: game-cmd.c:270: cmd_set_arg_choice: Assertion `game_cmds[idx].arg_type[n] & arg_CHOICE' failed.

[takkaria]

Originally Posted by PowerDiver

I downloaded, ./autogen.sh, ./configure --with-no-install, compiled, ran, and immediately got an assert error after I "Press any key to continue". A quick look suggests that the problem might be that with no savefile, there is no stack of previous commands. However, I don't see how the money bug described above could happen if the code dies before the birth process.

Is there any likelihood this could be platform specific? Where does that mean I should look? I've never looked at the command code before, so I'd appreciate a hint where to start looking.

angband: game-cmd.c:270: cmd_set_arg_choice: Assertion `game_cmds[idx].arg_type[n] & arg_CHOICE' failed.

Could you compile it with CFLAGS+=-g, run it in gdb and paste the backtrace?

[PowerDiver]

Originally Posted by takkaria

Could you compile it with CFLAGS+=-g, run it in gdb and paste the backtrace?

I should have mentioned I got the code with git clone as per rephial.

Reading symbols from /home/eddie/Angband/nightlies/angband/angband...done.
(gdb) run
Starting program: /home/eddie/Angband/nightlies/angband/angband 
angband: game-cmd.c:270: cmd_set_arg_choice: Assertion `game_cmds[idx].arg_type[n] & arg_CHOICE' failed.

Program received signal SIGABRT, Aborted.
0x0012d422 in __kernel_vsyscall ()
(gdb) trace
Tracepoint 1 at 0x12d422
(gdb) backtrace
#0  0x0012d422 in __kernel_vsyscall ()
#1  0x002ad651 in raise () from /lib/tls/i686/cmov/libc.so.6
#2  0x002b0a82 in abort () from /lib/tls/i686/cmov/libc.so.6
#3  0x002a6718 in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#4  0x08065ddb in cmd_set_arg_choice (cmd=0x8117444, n=0, choice=1) at game-cmd.c:270
#5  0x080ca6ad in get_birth_command (wait=true) at ui-birth.c:841
#6  0x08065393 in cmd_get (c=CMD_BIRTH, cmd=0xbffff0f8, wait=6) at game-cmd.c:234
#7  0x0804dd87 in player_birth (quickstart_allowed=false) at birth.c:1075
#8  0x0805d5f0 in play_game () at dungeon.c:1746
#9  0x080e558f in main (argc=1, argv=0xbffff4b4) at main.c:468
(gdb)

[Magnate]

Originally Posted by Dean Anderson

Reading through the change log, I'm actually very pleasantly surprised by it.

I'd got the impression - a false impression it now seems - from reading what people have been saying about the nightly builds that there were big changes happening on an almost daily basis.

But that change log looks nicely conservative (I think Vanilla should change only incrementally, and leave radical stuff to the variants; only after something big is tried and tested in a variant and reasonably universally liked should it be back-ported to V).

So - how long do you guys reckon it will take to go from a release candidate to an actual 3.2 release?

Personally I think 3.2 will be out before the end of the year, though there may well be a 3.2.1 in Jan/Feb with fixes.

Yes, those few lines about code changes (bitflags, parsers etc.) conceal a colossal amount of refactoring. The code looks very different from the 3.1.x series.

I think the issues with changes in nightlies is not that they are large (as you observe, there aren't many of those over the lifetime of a new release), but that they are immediately noticeable, even if small. Since nightlies appear much more quickly than the length of the average game, people have to cope with changes mid-character. I think that's harder than anybody likes to acknowledge.

[Chud]

Hmm. I just created new Gnome Mage in the most current nightly (revision d1a64ee55c, Windows) and she came up with no gold AND no equipment. This might be a challenge initially...

[Chud]

I see the gold issue is already addressed in another thread - sorry, please disregard.

[PowerDiver]

Originally Posted by PowerDiver

I downloaded, ./autogen.sh, ./configure --with-no-install, compiled, ran, and immediately got an assert error after I "Press any key to continue". A quick look suggests that the problem might be that with no savefile, there is no stack of previous commands. However, I don't see how the money bug described above could happen if the code dies before the birth process.

Is there any likelihood this could be platform specific? Where does that mean I should look? I've never looked at the command code before, so I'd appreciate a hint where to start looking.

angband: game-cmd.c:270: cmd_set_arg_choice: Assertion `game_cmds[idx].arg_type[n] & arg_CHOICE' failed.

FWIW I commented out the assert and then startup went smoothly.