And I have no idea what you mean by "C64 had awkward graphics." It integrated ideas already present in the Atari computers, with some advantages and some disadvantages. Both those platforms utterly crushed the primitive graphics and "sound" available on the Apples, with their hardware sprites, fine scrolling, redefinable character sets, and multichannel sound. The Ataris also used intelligent, daisy-chainable peripherals.
Calling Atari and Commodore graphics "awkward" in the scenario you describe sounds like laziness in learning and taking advantage of new graphics hardware. The sole "awkward" thing on the Atari was that, for some reason, the sprites were as tall as the screen and therefore the only way to achieve vertical movement of a sprite was indeed to move it through memory. But you could do this even in BASIC by setting the sprite data up in a character string and using the fast string functions to move it.
Both the Atari and Commodore made graphics programming decidedly non-awkward by providing automated collision detection between the sprites, and also with the background. Moving sprites around during screen refresh was common on both platforms. On the Atari, the technique (called a display-list interrupt) could also be used to put 256 colors on the screen at once and simulate multi-color sprites.
An innovative use of display-list interrupts gave rise to this cool effect that was called (by LucasArts if I recall) "altered-perspective scrolling." Check it out here in BallBlazer, a soccer-type game written for the Ataris: https://youtu.be/_tkwWD_BWWQ?t=631
I don't know what your deal is with the word "awkward." As someone who wrote a lot of games on Apple, C64, and one each on the PC and Amiga, I've earned the right to use whatever innocuous word I want to describe a vague feeling that I have. Mind you, all that more than 35 years ago. Perhaps I am misremembering how non-awkward it all was. I did not do anything with the Atari. I was merely told by my boss and friend Dale Disharoon how strange he found it.
Yes, we liked the C64 collision detection. The main awkwardness about the C64 was, at the time I was first working with it, that it was all undocumented. I just think it's awkward to call information to get the phone number of a writer of a magazine article in Toronto to find out how to work the vertical blank interrupt, since there was no reference manual at that time. The Amiga manuals were full of errors when they first came out.
I suppose I am a lazy learner. As you can read all about in my book about being a high school dropout, published by Simon and Schuster (get your copy in Korean today!). Also see page 60 of this issue of Compute Gazette (https://archive.org/details/1983-11-computegazette/page/n59/...).
I don't remember a lot either and am searching for this now. It looks like the Apple IIe added a bit at $C019 for detecting vertical retrace, but the II+ and earlier didn't have it.
Also: The sound of a planet blowing up on an Apple resembled someone spilling a bowl of pistachio shells.
I sense that you are too young to have first hand knowledge of these things, but if you do then your memories are just as faded as mine. I remember that we didn’t have flicker. And I was in the industry at the time developing games for the Apple II.
The Atari graphics were awkward, too, or so I was told by my boss at the time who did the Atari versions of our products. Good though. What I mean by awkward is just that I was surprised, as someone with no training in computer engineering, how many little quirks you had to work around. Apple graphics were primitive compared to the others, using a seven bit architecture for pixels and the high bit used for color information. At least the C64 had all eight bits for pixels, which made rendering a little faster. C64 sprites were interesting, but like the OP said we had to do tricks with interrupts to reuse them as the screen rastered.
I guess another reason I said awkward is that we had to do every trick we could to squeeze the art into memory. Alphabet Zoo was shipped as a 16k cartridge. I did an entire game with art in 16 kilobytes! I used nine bytes to encode my name, then later I needed those nine back again… so no easter egg for me.
But, moving 16bit words was a huge improvement compared to the C64 for obvious reasons.
The one thing the C64 missed was full screen hardware scrolling. I don’t mean the pixel shifting.
I’m aware there’s a clever hack to get full screen scrolling - even at Sonic the Hedgehog rates.
This game leverages that: https://m.youtube.com/watch?v=ldo2ewLBt3Y
Because the Ataris and Commodores had redefinable character sets, you could create graphic elements as characters and build huge maps and scroll around them smoothly with ease.
You really can’t do that ‘with ease’ which is why c64 games typically divide up the screen so the scrolling area is smaller.
At some point I got clued into shape tables, plotted one out, and then called upon it in a program. It was no faster than a sequence "drawto" statements. At that point, I had my answer: You don't; at least not on an Apple.
I seem to recall we could flip between two different high res screens and so we drew on the hidden one and then flipped to the other one when the vertical blank interrupt occurred. Also, we rarely had to update the entire screen all at once.
Both the Apple and C64 had awkward graphics, but graphics speed was not a concern. The issue was more often disk storage and access speed, and of course memory limitations.
The thing I am most proud of as a programmer is I wrote an emulator of AppleII graphics for the C64 so we could reuse the art from the Apple version of the game. It was just barely fast enough.