Commander X16

Few more suggestions:

1. Since there's a lot of unused screen space, use a lower-res screen, if possible.
2. Use that large empty space for the control descriptions, eliminating the need for a separate screen.
3. Include keyboard-control option.

unartic wrote: ↑Fri May 17, 2024 5:09 pm A quick demonstration of how to draw a bmx image to the screen in assembly.

It would be more accurate to say this demonstrates the speed at which the image is drawn as there's no "how to" attached to it.

Gerry wrote: ↑Wed May 15, 2024 6:05 pm I don't want to burn you out asking a thousand minor questions

Yeah, somebody already beat you to that job.

DragWx wrote: ↑Mon May 13, 2024 7:03 am The first method relies on non-existent RAM reading back as $A0 due to bus capacitance

I'm not familiar with that.

I noticed that the displayed square waves were a bit distorted, as if they were trying to morph into a triangle wave. Is this intentional or an inaccuracy of the player?

Wow, this takes me back to the golden days of ST fandom ('70s-'80s) when I was a hard-core ST fan of everything technical. I miss those days.

LL&P! \\//

The UG is only partially complete. The "garbage" text is known as "lorem ipsum" and is just placeholder text until chapters can be written. Perhaps, instead of using random text, how 'bout something like "[-----WIP-----]" or "[-----Undocumented-----]", etc. c...

How does doing the same thing in 12 lines make it more elegant than doing it in six?

I played a ton of FPSs back in the day, and I always used a mouse+KB, so it felt pretty natural to me. And just for S&G, I tried going diagonal using key combos like WD, AS, etc., and it worked while still aiming the turret independently.

Djehuti wrote: ↑Wed May 01, 2024 5:04 pm And for music I was just going to use a bool...

What's a bool?