3.4.0 Release Candidate is available

[fizzix]

Not sure if anybody else is having this same problem, but when trying to use Shockbolt's tiles on my Windows XP system, I frequently get an error message upon starting up the game that says it cannot read the 64x64 png file. When I restart my computer, it works again, but always happens again at some point after exiting the game and then starting it up again. I haven't been able to figure out what circumstances this happens under, but I can say that it always seems to work fine the first time after restarting my computer. Also, I haven't experienced this problem on my laptop which has Windows 7... so far the issue has only occurred on Windows XP.

weird. I never came across this bug on XP. I did a lot of shockbolt tile testing too...

[tg122]

weird. I never came across this bug on XP. I did a lot of shockbolt tile testing too...

So I did some testing and finally figured out how to make it happen on command. It seems that any time I either a)log off to switch users in windows xp, or b)the computer goes into standby mode, the issue will happen where it can't read the tileset. The only way I've been able to resolve it so far is by restarting my computer. After I restart my computer, I can then start the game, quit, and restart the game as many times as I want, but as soon as I log off to switch users or the computer goes into standby mode, the issue will happen. I'm not sure if this is a general issue with XP or if there is something funny about my computer that's causing it to happen.

[ekolis]

Something similar happened with fonts in some variants; apparently it involved the OS locking the files and not releasing the lock properly?

[fizzix]

So I did some testing and finally figured out how to make it happen on command. It seems that any time I either a)log off to switch users in windows xp, or b)the computer goes into standby mode, the issue will happen where it can't read the tileset. The only way I've been able to resolve it so far is by restarting my computer. After I restart my computer, I can then start the game, quit, and restart the game as many times as I want, but as soon as I log off to switch users or the computer goes into standby mode, the issue will happen. I'm not sure if this is a general issue with XP or if there is something funny about my computer that's causing it to happen.

I tested going into standby on my XP computer and I had no trouble loading up the tileset. I didn't try switching users, but I can try that later. We'll get some other XP testers for this.

[buzzkill]

Something similar happened with fonts in some variants; apparently it involved the OS locking the files and not releasing the lock properly?

If it's a locked file problem, then this might help to diagnose, or hack-repair short of a reboot. I use it all the time to delete stuff that windows doesn't want me to.

[jujuben]

This bug should be fixed in the next nightly builds. If you can, please verify that the game no longer crashes for you here.

Hrm.. not sure if rephial isn't updating the RC, or if the bug is still there, but I just downloaded the latest from the nightlies page, and nothing changed.

[Magnate]

Hrm.. not sure if rephial isn't updating the RC, or if the bug is still there, but I just downloaded the latest from the nightlies page, and nothing changed.

Can you press shift-v in game and tell us the version string?

Thanks.

[myshkin]

Hrm.. not sure if rephial isn't updating the RC, or if the bug is still there, but I just downloaded the latest from the nightlies page, and nothing changed.

The latest from the nightlies page is indeed not the latest. We'll look into it. In the mean time, could you try out this disk image, which should include the fix?

[jujuben]

Seems to work now. I get ? - unknown symbol. Thanks.

Now that I've got a version that doesn't crash when I get distracted, downwards I go...

[myshkin]

Seems to work now. I get ? - unknown symbol. Thanks.

Now that I've got a version that doesn't crash when I get distracted, downwards I go...

Excellent. Thanks for the bug report! Let us know if you find anything else. (The One Ring counts as anything else.)

[PowerWyrm]

Not sure if anybody else is having this same problem, but when trying to use Shockbolt's tiles on my Windows XP system, I frequently get an error message upon starting up the game that says it cannot read the 64x64 png file. When I restart my computer, it works again, but always happens again at some point after exiting the game and then starting it up again. I haven't been able to figure out what circumstances this happens under, but I can say that it always seems to work fine the first time after restarting my computer. Also, I haven't experienced this problem on my laptop which has Windows 7... so far the issue has only occurred on Windows XP.

I have the same problem with both 32x32 and 64x64 tilesets. It seems that both tilesets have color glitches which are detected in the ReadDIB2_PNG() function (readpng.c) when SetDIBits() returns -1 and in this case the function fails to load the tileset. To fix that, I have recompiled the source code so that when SetDIBits() returns -1 for one line, the previous line is used instead and the function doesn't fail.

[jujuben]

Played a few times, leaving a string of corpses through the dungeon, none of them particularly deep yet. However, I don't seem to be generating any high scores. On the death screen I get the following: "Failed to create lock for scorefile, not writing."

[Magnate]

Played a few times, leaving a string of corpses through the dungeon, none of them particularly deep yet. However, I don't seem to be generating any high scores. On the death screen I get the following: "Failed to create lock for scorefile, not writing."

Ah, I think this is because we've moved the default savefile location for OSX ... myshkin?

[jujuben]

Another minor bug - visual only, no gameplay effect. Screen center on, running, and hitting a trap gives 2 @s until the trap effect message clears.

[Magnate]

Another minor bug - visual only, no gameplay effect. Screen center on, running, and hitting a trap gives 2 @s until the trap effect message clears.

A much-loved and ancient bug - ticket #362.