Gigatron Hackers

Your Gigatron looks great, well done!

I've updated the DropBox .GT1 repo with a bunch of cool stuff posted by many of you over the last 6 months or so, if I have missed anyone's projects or you would like something I have added to be removed, please just DM me, cheers.

Lots of fun and very slick graphics, the only thing I noticed was that if you spam the A button you can bring the game to a crawl.

P.S. With your permission I'll add all your contributions to the Dropbox folder that is stickied here: https://forum.gigatron.io/viewtopic.php?t=248

See here:
https://github.com/at67/ROMvX0/issues/35

There's some low hanging fruit that you can try: 1) DIM statements will create 16bit word arrays by default, if your array only needs values between 0-255 then use the % modifier on the variable name to create 8bit byte arrays. 2) If you have an array of strings and the array is constant, i.e. read ...

It was an absolute art-form back in the day, something that doesn't happen much anymore, (except in embedded or tiny-demo programming).

The next release will have compressed, scrollable and screen to screen blits which should help a lot in this area.

There isn't, SPRITE's are designed to emulate real hardware sprites as much as possible, i.e. they are capable of restoring any background, static, dynamic, other sprites, blit's, bullets, etc. If you want a sprite that doesn't redraw/refresh based on spatial state, (i.e. movement), then just use a ...

You need to LOAD the SPRITE's before the BLIT's. most likely what has happened is that the BLIT's have taken some of the SPRITE's memory. Also, with the 64k model the maximum number of rows for all SPRITE's, is 120 + 128; have you exceeded this number?

There's no need to do that, the BLIT routine will automatically split up the image into contiguous chunks of whatever you specify, obviously it will become a little more inefficient as more individual native calls will need to be made internally to get the full image on screen; just set the number s...

Sprites are hard coded to use the offscreen segments of both pages of memory, this means from 0x08A0 to 0x7FA0 for page 0 and 0x80A0 to 0xFFA0 for page 1, this means that the maximum number of combined rows of data in your sprites is 120+128, (not including PATTERN's, just LOAD SPRITE commands). It ...