Boulder Dash 2

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Andrew Davie

This is a play-through of cave A/2 -- I am trying to see if it's possible to collect ALL the diamonds ("a perfect run") in the available time. I'm not good enough to be able to play this level and not get killed AND get all the diamonds, so I have collisions disabled. You might notice a few times I should have been killed, but that's the fun of being the developer - I can say "nah!".  Anyway, although I didn't get ALL the diamonds (some areas are quite tricky), this play-through was good enough to demonstrate to my satisfaction that a "perfect" run is possible. Just.

video looks quite jerky; a function of my screen capture I think. Playing, it's quite smooth.



Andrew Davie

#61
I've added a "perfect" bonus. When you get all possible diamonds in a cave, you get a bonus. This bonus is displayed as a count-up along with the time bonus and diamond bonus. The video shows the sequence in ChronoColour and iCC modes.


Andrew Davie

#62
The insanity/madness of cave C5 - but it's actually do-able. In the video I completed it with 1 second spare!  I've figured out I get way better video capture if I play in a smaller window. Makes sense; my laptop isn't quite up to running Gopher AND doing large-window 60Hz video capture at the same time.


Andrew Davie

This is a play-through of Cave A2 (v2).  I've introduced the concept of a "perfect" sequence - if you get ALL of the diamonds on a level. Normally you don't have to get them all, and you get ponits per diamond up to the required number (e.g., A1 has 26 diamonds but you only need to collect 20 to open the door).  If you get all of the diamonds, you have a "perfect" run on that lvel, and you're awarded a bonus. The bonus is 500 points (=1 life), but I implement with a "score multiplier".  When you complete a perfect level, the score multipler is incremented. If you don't have a perfect run, score multiplier is reset to 1.  So if you complete (say) two levels in perfect fashion then your score multiplier becomes 2x, so playing the next level is much more points-worthy.  But, I digress -- getting a perfect level is sometimes incredibly difficult. This video shows the first "successful" run I did on level A2 where I had a "perfect" run. You can see getting to some of the diamonds is really tricky. In fact I was playing this with cheat mode on and my timng wasn't quite right in a couple of places - so I would have been killed. But only because I was a tad slow - the video shows in-principle that a perfect run on A2 is indeed possible. Incredibly tricky, but possible!

Warning: spoiler alert in video!!  Don't watch if you don't wanna see the secrets :)


Andrew Davie

Because I'm short of ROM space, I've put a few features on conditional swithces so that I can easily disable them. Here's a brief summary of some of those features and their costs...

DEMO MODE = 365 bytes
RAGE QUIT = 1508 bytes
"SNOW" ON TITLE = 136 bytes
SERIAL NUMBER = 76 bytes
RAINBOW SCREEN SUPPORT = 280 bytes
"PERFECT" SCREEN BONUS = 384 bytes
TIME SHORT PULSE = 40 bytes
CDFJ DRIVER (cannot remove) = 2048 bytes

Total ROM available = 32768 bytes

Bomberman94

Quote from: Andrew Davie on 14 Apr 2024, 12:56 AMBecause I'm short of ROM space, I've put a few features on conditional swithces so that I can easily disable them. Here's a brief summary of some of those features and their costs...

DEMO MODE = 365 bytes
RAGE QUIT = 1508 bytes
"SNOW" ON TITLE = 136 bytes
SERIAL NUMBER = 76 bytes
RAINBOW SCREEN SUPPORT = 280 bytes
"PERFECT" SCREEN BONUS = 384 bytes
TIME SHORT PULSE = 40 bytes
CDFJ DRIVER (cannot remove) = 2048 bytes

Total ROM available = 32768 bytes


I love the "perfect" animation of Rockford and the time short pulse is very cool, too. I think the RAGE QUIT doesn't add so much to the actual game play and the serial number is obsolete after finishing the game.

Andrew Davie

#66
RAIN = 560 bytes
SECAM SUPPORT = 145 bytes

Andrew Davie

Quote from: Bomberman94 on 14 Apr 2024, 02:15 AMI think the RAGE QUIT doesn't add so much to the actual game play and the serial number is obsolete after finishing the game.

I've been thinking along these lines, too. It's a shame because it's such an awesome effect/sequence.
If/when I need to gain space, I guess that will be the first to go. BBG may not approve it anyway.


The serial number is to allow me to track if people distribute the game against the "rules" whatever they may be. For example, if I do a demo version I may make a uniquely serial-numbered version for each person requesting it. With an agreement that the binary would not be distributed.

Andrew Davie

#68
The game is essentially character-based. Characters are 4 pixels wide and 21 pixels (7 iCC "trixels") deep. This video shows a rework of the rain collision algorithm. Previously it would detect a "hit" on something on a character-basis - so for example a diamond without dirt around it, the rain would "splash" above the diamond itself. It wasn't really noticeable, but it bothered me. I figured a way to quickly determine to a pixel-perfect accuracy the collisions on rain/background and so this video is just showing that in action. For example, rain now falls past the left point of a diamond without collision - whereas previously it would stop at the very topmost pixel of the diamond character, with a visible gap there.  Probably I'm the only one in the world who would notice this/care. But anyway, it's fixed.


Andrew Davie

Abandoned selection grid concept for choosing cave/level at the menu.
I want to somewhow be able to intuitively enable accessibility as you progress through each.

crt_composite_CDFJBoulderDash_20240424_013438.jpg

Bomberman94

Maybe an idea for a second screen? There you can see your progress in the game (cave level just won / perfect won / whole cave mastered etc.). Let's call it ,,Boulder DashBoard".

Andrew Davie

#71
I found a (relatively) cheap way to re-implement the circular swipe. It happens at the start of a life, as shown several times in this video. Essentially it just incrementally draws larger and larger circles into a mask buffer, which is then applied to the already-drawn screen. That way I can use an increadibly cheap/easy circle algorithm, as shown in https://www.cs.helsinki.fi/group/goa/...

Despite the severe lack of spare processing time in overview mode, the swipe functions in all three view modes, as shown in the video. The total cost of the code is about 430 bytes. The circle can expand at whatever speed I wish; it's controlled by a speed variable.



Here's the essentials of the code... drawCirclePoints draws 8 points of the circle based on x,y

    int x = circleRadius >> 8;
    int y = 0;
    int d = 1 - x;

    do {
        circleComplete |= drawCirclePoints(x, y);
        y = y + 1;
        if (d < 0)
            d = d + 2 * y + 1;
        else {
            x = x - 1;
            d = d + 2 * (y - x) + 1;
        }
    } while (x >= y);

Andrew Davie

When I rewrote the circle swipe (see last video), I made it so that I could specify the center position of the circle, the speed of swipe, and also direction (negative or positive circle).  In other words, I could uncover or cover over - effectively.  This video shows all of that in action - I rejigged a couple of caves so I could complete them quickly and then put the swipe through its paces. For example, at about 1:05 you see the circle center is top right of screen. I also get killed, then show the after-death transition.   It all looks rather effective to my eye, and I'm quite pleased with it. 


Andrew Davie

#73
The end of level bonus sequence involves adding a "perfect bonus" if you get all possible diamonds, as well as extra points for time remaining and excess diamonds collected. This is shown with text drawn over the screen, and up until now it's been serviceable, if uninspiring.

Previously I'd used a solid black background behind colour-cycling text to try and distinguish text from the background graphics it was laid over. Workable, but not what I wanted.

I've been working on enhancing the visuals in this sequence, and have managed to put highlighting and drop-shadows on the text (and dropping the solid black background). Simply by drawing three times; first in "white", then offset down 6 scanlines (=2 trixels) in black, and finally in a mid-colour positioned down 3 scanlines (=1 trixel) from the white. It gives a nice 3D effect - somewhat subtle but way better than the pulsing colour I had in earlier versions.

There appears to be enough processing time to handle this. At least in emulation.
Here's a couple of screenshots...


crt_composite_CDFJBoulderDash_20240430_110056.jpg

crt_composite_CDFJBoulderDash_20240430_110052.jpg

Andrew Davie

The new "GAME OVER" -- hopefully will not time-overflow on actual hardware.

crt_composite_CDFJBoulderDash_20240501_025702.jpg