bd: breaking a "wall with diamond" with a pneumatic hammer results in the diamond "falling" into place

[ncrecc]

diamondhammer.gif (56.8 KiB) Viewed 155 times

i presume since the animation engine sees the diamond as being created by the jackhammer object, it animates the diamond as emerging from where the jackhammer was. it would look better if the diamond simply appeared in place where the wall was.

[TheOnyxGuy]

Even stranger, by the way, the key appears where it's supposed to appear, because it doesn't move. So I'm assuming that's just engine's actual behavior.

[Holger]

Fixed with version 4.4.2.1.

[filbo]

I am curious whether the fix in 4.4.2.1 is purely cosmetic; or whether the described / displayed behavior affected game logic. The shown images look like the falling diamond would block a monster arriving at a precise time, whereas if the diamond just magically appears in the dug-away cel, the monster wouldn't be blocked. So some saved tapes would likely behave differently.

[ncrecc]

I am curious whether the fix in 4.4.2.1 is purely cosmetic; or whether the described / displayed behavior affected game logic. The shown images look like the falling diamond would block a monster arriving at a precise time, whereas if the diamond just magically appears in the dug-away cel, the monster wouldn't be blocked. So some saved tapes would likely behave differently.

if you look closer, you can see that when rockford is using the jackhammer, the jackhammer is in a different tile than rockford. this tile is a fully solid tile that goes away when the jackhammer animation is finished. so the tile that the diamond emerges from was already blocked.

even then, since this is the BD engine, the animation of the diamond falling does not actually reflect game logic. it is a purely visual feature that can be toggled with the "smooth movement" setting in Setup->Game Engines->Boulder Dash. the reality of the matter is that the diamond always existed solely on the tile it eventually "falls" into, as, behind the animations, Boulder Dash is strictly a grid-based game where all elements are tiles on a grid.

[Holger]

even then, since this is the BD engine, the animation of the diamond falling does not actually reflect game logic. it is a purely visual feature that can be toggled with the "smooth movement" setting in Setup->Game Engines->Boulder Dash. the reality of the matter is that the diamond always existed solely on the tile it eventually "falls" into, as, behind the animations, Boulder Dash is strictly a grid-based game where all elements are tiles on a grid.

Exactly true.

I cannot add much more here, just in my own words: The change is purely graphical, no changes to the BD engine at all.

As ncrecc already wrote, the BD engine works 100 % synchronous, and all game tiles are always at exactly one position on the grid. Everything else (especially the "smooth movement") is just visual sugar I added to let it look more like the other game engines -- the BD engine in R'n'D (and the original BD game) internally does not know anything of what looks like a game element moving from one tile to another.