Rocks'n'Diamonds

When playing back one tape on this level usually results in a bad tape that fails one way. But one time after playing some other levels, and going back it's tape playback kept doing a different bad tape playback(same one everytime?) than it's usual playback of this bad tape. I hadn't actually played this level this R'n'D run, but I might have done a regular bad tape playback of it earlier[not sure]. Upon restart of R'n'D it went back to it's normal playback of this tape. I've only seen this happen this one time, so maybe this itself isn't so bad, but I thought mentioning it might help find/fix the bad tape bug(s).

This description is, um, pretty fuzzy...?

You say 'this level', but do not mention a level. Were you talking about some specific level / levelset where you've observed this?

I also wonder about the nature of the bad playback. Typical RnD bugs with playback look sort of like: the playback starts out OK, the level gets about half-solved, when things suddenly go wrong. The player dies because timing was slightly off; or their motions stop making sense because one attempted move was blocked by a thing that was in the way, so now all subsequent motions are relative to the wrong location.

On the other hand, if you were to take a tape from a completely different level and try to play it back, you would get completely nonsensical behavior from the very beginning.

I guess there is also a third class of 'wrong playback', in which everything is as expected up to some point, then activity ends without actually going nuts; i.e. a truncated (but otherwise accurate) tape.

So:

- which levels / levelsets?
- what sort of 'bad playback' behavior?
- was this just once, or repeatable (or, most likely: semi-repeatable, like, you've seen it a few times but cannot pin down the formula to trigger it at will)?

I must admit that I do not understand what this is all about!

If there is something (besides the well-known, notorious "broken tapes" issue) that does not work as expected in R'n'D, please consider the following points when describing the problem:

- what exactly did you do (including R'n'D version and operating system)
- what did you expect to happen (which you think is correct behavior)
- what happened instead (which you think is wrong)

Then I might be able to help!