Rocks'n'Diamonds

Tried to solve impassable level, found some bug(s)

Looks like DISPLAYED data broken(real level data stay ok),
when use F2 to load checkpoint NOT 1st time since the start of the game

Then, the more you repeat loading, the more data broken and
at some point it gets into the stored data
by overwriting saves
? or even at simple saving but not all cases.

Tried test this at tutorial levels, behave even more buggy than classic.

attached some screens:
1.Loaded previously saved data (RnD game just launched or restarted).
Results: OK
(no screenshot, because it seems ok and does not matter and 3 attachments only, )

2.Loaded 2nd or more times.
Results: corrupted displayed data

3.Corrupted saved data or not properly loaded then saved (RnD game just launched or restarted)

4.Corrupted saved data or not properly loaded then saved (Loaded 2nd or more times)


Downloaded version 3.2.3 from bd-fans.
Looks like version 3.2.3 don't has this bug.

Unfortunately cant find another version(between these two) to test.
I will be grateful if you tell me where I can get other versions.

p.s.:
Another small bug detected: rarely enough, ENTER does same as ALT+ENTER
seems occurs when finished level and pressing ENTER some times to go for next level.

Some questions:
By the way, automatic level advancing is possible?
same question for automatic play next tape.

I found it earlier, but it's other situation.

Camera focussing

Hello ZX-Dash, hello Eizzoux,

could you please describe the bug in a bit more detail? Which level did you play when you encountered the problem?

Eizzoux, as you mentioned in a PM that this bug does not appear in version 3.3.0.1: Could you please also check in which version of the game this bug was introduced? Is it already there in version 3.3.1.0 (after the long break; there were quite some changes in this version), or did it show up in one of the last minor releases (3.3.1.1 or 3.3.1.2)?

So far I haven't encountered this bug, so it would be best to have a step-by-step description on how to be able to reproduce this bug.

Holger wrote:could you please describe the bug in a bit more detail? Which level did you play when you encountered the problem?

I'll try...
As it turned out, many levels, but i think, maybe ones that have large sizes or complex structure.

1.
"Light" bug version.
example: loaded, failed, then loaded again = corrupted representation.

description what i mean by "light":
when you still can get properly displayed level data.
to get this - restart game then load checkpoint
(works only first time, next loads lead to incorrect displayed data)

For attached tape:
level 82 (classic_boulderdash),
1. start game (clear)
2. load by F2, run to left - seems all clear..
3. load 2nd time by F2, run to left - see artifacts

2.
"Hard" bug version.
It when you CANT get properly displayed level data, even if restart game for further load.
Can be obtained on couple of save/loads operations when trying to solve some maze

Newly tried to get bug... Done.
Started (rnd_tutorial_aaron_davidson), go for level 6,
0. do actions,
1. saved (by F1),
2. do actions,
3. failed,
4. loaded(by F2),
5. do actions,
6. saved (by F1),
7. do actions,
8. failed,
9. loaded(by F2).
Results on attached screen (and normal screen for comparison):
Seems like some saving(or loading) process sometimes doing something wrong.

I suspect it's the same bug as this, but in that case I was actually looking through the specific contents of the tape file.

Another variant of this bug

load,
fail,
load
result: rocks don't fall

but still dangerous to push some of them upward

tape attached,
animated gif:




P.S.: some issues when posting this:
it says up to 2mb, and when i recorded 2mb file, then it says 256kib
grrr..

Two ways to reduce the inconvenience of broken tiles bug.

1. Just move back a little, until broken tiles get off the screen
Then come again - now they are normal.
(video at 0:07-0:14, 0:56-1:05)

Unfortunately, in many levels is not possible to do it,
so the second solution:

2. Use quicksave, then immediately quickload, to clear tiles.
(video at 0:22-0:34, 0:38-0:45, 0:48-0:53)

http://www.youtube.com/watch?v=ew8TS1aLeaM
(turn on annotations if still need some clarifications)

Thanks a lot, ZX-Dash, for the detailed description of this bug and for the very helpful YouTube video demonstrating the bug.

This bug is fixed in the current Git version (by commit 9ea8b203a29569f4d2ed059d33def627ff2b17aa, already some time ago).

Hope the fix will be available in a release version soon.