Boulder Dash 2

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Andrew Davie

To reinforce the above, here is a close-up detail of sparkling diamonds - rendered at 25% speed. You can see the interleaved ChronoColour in action but also the facets of the diamond flashing - at least as I have tried to draw them. You can further slow down or swipe back/forth with the YouTube controls.


Bomberman94

Imagination is everything - I mean it in a positive way! Never thought of that because right and bottom edge do not have the same length (but that doesn't matter). Simply put THAT diamond on the instruction and box - you automatically will recognize it in the game😉

Andrew Davie

Quote from: Bomberman94 on 14 May 2024, 11:42 PMImagination is everything - I mean it in a positive way! Never thought of that because right and bottom edge do not have the same length (but that doesn't matter). Simply put THAT diamond on the instruction and box - you automatically will recognize it in the game😉

My thoughts exactly. See the icon and your brain immediately knows what it is.

Andrew Davie

A review of the animations for diamonds (code below)...

static const unsigned char AnimPulseDiamond0[] = {
    CH_DIAMOND,ANIM_RNDSPEED,
    CH_DIAMOND_PULSE_0, 5,
    CH_DIAMOND_PULSE_1, 4,
    CH_DIAMOND_PULSE_2, 3,
    CH_DIAMOND_PULSE_3, 2,
    CH_DIAMOND, 2,
    CH_DIAMOND_PULSE_4, 5,
    ANIM_LOOP
};

This was written when I first started development and all we had was "ChronoColour". Line triples (I called "trixels") which represented 8 colour variants/pixel. When I added the "interleaved ChronoColour" (iCC) system, I rolled these colours through the three scanlines (chronologically) to give a much more solid (but shimmering) display. This means that to work effectively, trixels must be displayed for a multiple of 3 frames (otherwise we will see only 1/3 or 2/3 of the trixel colour on the last time slice, so to speak). The colours won't be solid - or even the right colour.  This means that I should have rewritten the animation code (above) to be multiples-of-3 for the delays (e.g., CH_DIAMOND_PULSE_0, 5, displays for 5 frames - whoops).  So, although in this video I'm running the animation too slowly (9/6/6/6/6/6) whereas the next option is (6/3/3/3/3/3)... well, it gives a much more solid feel to the faceting and leverages the iCC system properly.

So I'm glad we've revisited this topic.


Andrew Davie

And here, in all its glory, is a refined/improved version. Looks great to me.


Andrew Davie


Bomberman94


Andrew Davie

Can't leave it alone. OCD. I've tried to give the top of the diamond a clear visual and facted look.

diamond.jpg

crt_composite_CDFJBoulderDash_20240517_001048.jpg

Andrew Davie

Found/fixed a MAJOR bug which caused spontaneous creation of diamonds!  It was probably a fairly recent addition, as I'd been working on code there or thereabouts recently. Obscure sequence of events - fortunately for me the Gopher debugger allowed me to step back and forth frame by frame and watch exactly as it happened.

Andrew Davie

Here's a study/view of the diamond sparkly animation. I made some changes to the graphics - particularly in putting a line of white across the 'top' of the diamond, and reviewing the facet animation carefully. To my eye it looks pretty good - a big improvement on "big triangles".  Does anyone else see "diamond" now, instead of "triangle", I wonder.  Video probably best viewed full-screen to be able to see the detail.


Andrew Davie

Here's the same, but in ChronoColour mode - remarkably good!
I may have to do another pass on the palette colours to try and improve the white contrast. Not an easy task, but some improvements might be possible. This particular video shows excellent contrast. Some of the palettes you can barely see the difference between white and (say) yellow.


alex_79

They look good! Highlighting the top helps in recognizing the shape of the diamonds (albeit I'm now a bit biased because I've seen the icon you postewd earlier and, as discussed above, may brain is "trained" to see that ;D )

Andrew Davie

In the short remaining time, I'm polishing the last remaining items on my do-list. Here I've reworked the boulder "rolling-off" action by adding an in-between frame (consisting of two half-boulders) so that I have double the horizontal resolution. It works better than I expected, and now the boulders rolling look very good!


Andrew Davie

Here are a few SECAM "screen grabs" from the Gopher emulator.  SECAM's interesting. It has an extremely limited 8-colour (including black) palette of garish, bright, colours. Despite that, the interleaved ChronoColour (iCC) system manages to blend these together to produce (a completely different set of) 8 colours that work well for Boulder Dash.  The emulation of SECAM isn't quite perfect; the real SECAM TVs display slightly different colours on each scanline. But it's not too bad, and these images show that the SECAM version is working nicely.

secam1.jpg

secam2.jpg

secam3.jpg

secam5.jpg

secam4.jpg

Andrew Davie

During the Zeropage Homebrew show featuring Boulder Dash Demo, someone made an aside comment that they would like to see a star swipe (instead of the circle swipe). I know this was probably tongue-in-cheek, but I thought it would be an interesting challenge and so I had a go at doing it.  This is really just a quick attempt and if you look carefully you can see it's a bit shabby and leaving a few pixels here and there. Relatively easy to fix, but I've done enough to satisfy myself that the algorithm works fine and I can revert back to my circle-swipe.