13 ms·
A Great Old-Timey Game-Programming Hack
- forktheif 13y agoAnother possible way to get around interrupts overwriting your screen, would be to turn them off and update the audio after every line or two.
- goldenkey 13y agoAren't the interrupts for DMA, buffer empty and other similar signals? If you do it manually I think performance suffers.
- vidarh 13y agoOr do most of the game logic in the interrupt handler. Many C64 games would do this, as it allowed precise timing of when updates would happen so as to for example not need double buffering at all - hanging everything off the raster interrupt meant you could trivially ensure you updated the screen when the graphics chip was not processing that part of the screen.
- acqq 13y agoIt can be that then the points where the new audio information comes wouldn't be properly spaced to produce pleasant sound. The solution described in the article is really beautiful: you let the interrupts happen, just make sure that the as soon as the interrupt returns the task continues but "covers" all the tracks that the interrupt happened, even if there was no separate stack area at the time the interrupt happened. Really cool.
- royjacobs 13y agoDepending on the DAC you need so many interrupts "every line or two" is already too slow. Not sure if this was the case on the Tandy, though.
- acqq 13y agoSo it was Tandy Color Computer 3 (CoCo 3). Thanks royjacobs. Wikipedia has one more interesting detail about CoCo 3: http://en.wikipedia.org/wiki/TRS-80_Color_Computer#Color_Computer_3_.281986.E2.80.931991.29 http://en.wikipedia.org/wiki/TRS-80_Color_Computer#Color_Com... "Previous versions of the CoCo ROM had been licensed from Microsoft, but by this time Microsoft was not interested in extending the code further.[citation needed] Instead, Microware provided extensions to Extended Color BASIC to support the new display modes. In order to not violate the spirit of the licensing agreement between Microsoft and Tandy, Microsoft's unmodified BASIC software was loaded in the CoCo 3's ROM. Upon startup, the ROM is copied to RAM and then patched by Microware's code."
- ChickeNES 13y agoOr do what the original Macintosh did, have the sound buffer consist of a block of memory at the end of each line in the framebuffer. So each scanline would give the audio hardware new data to process.
- asselinpaul 13y agoGood read.
- royjacobs 13y agoHaving just spent a good chunk of my weekend reliving my Commodore 64 assembly coding days, this was an excellent way to top it off!
- jds375 13y agoI'm almost a bit disappointed I missed out on those days. Having to code like that probably would've taught me several useful lessons.
- royjacobs 13y agoWell, you can still relive some of this by writing code to target an emulator or, more modern, an ARM chipset. Also, the quality of tools nowadays is so much better than what you would've used back then. So much so, in fact, that these old machines could even become pretty useful as a learning tool since they're (relatively) simple and allow much easier testing and debugging since they can be used effectively as some kind of VM.
- teddyh 13y agoWhat computer and game could this be? Looking at Wikipedia reveals that the Motorola 6809 was not used for many computers, and not any that I recognize as being very popular.
- tluyben2 13y agoHmm "The 6809E was featured in the TRS-80 Color Computer (CoCo), the Acorn System 2, 3 and 4 computers (as an optional alternative to their standard 6502), the Fujitsu FM-7, the Welsh-made Dragon 32/64 home computers," I know and have/had almost all of them. Maybe more popular in Europe?
- henderson101 13y agoThe Dragon was basically a CoCo clone. Don't recognise those Acorn computers (assuming this is the UK Acorn, those were all named "BBC Micro Computer" and had model names like "A", "B", "Master" etc), I'm pretty sure the Acorn used 6502, but it did have the option to interface to other processors (e.g. Z80) so 6809 would not surprise me.
- jrabone 13y agoThe Acorn System computers are rack mounted computers that pre-date the Acorn Atom - http://fjkraan.home.xs4all.nl/comp/atom/history/index.html http://fjkraan.home.xs4all.nl/comp/atom/history/index.html
- acqq 13y agoroyjacobs recognized that first here in his comment to forktheif's top: it was Tandy Color Computer 3. The article author answered that question in the comments.
- fit2rule 13y agoI used to spend my afternoons waypoint'ing all the computer shops I could access with a single days bus pass. This was a regular jaunt in the late 70's, early 80's, and .. at the time .. was a great way to prove ones chops. When you only had 20 minutes to type something in, it better be funky. (Coz the sales guy/gal is either going to let you save it to their "DEMO" floppy, or kick you out of the shop.) Until you come back and decide to buy something, and suddenly .. it mattered which CPU you chose. Z80, 68xx, the rumoured 68k, and .. so on. It was a bewildering time. (Thankfully, the still-functioning, embedded Video Game Arcades were able to provide some relief. I knew a few arcade owners, lets just say.. ;) Anyway .. there was a Tandy shop, and I had a CoCo section in my (long-lost) notebook. There were some funky things, no? But still .. in the Amstrad invasion, the Atari megalith, the Commodore death spiral.. Tandy kind of lost the plot. Strangely so. The CoCo were somehow 'tainted' in my mind, back then, because of the TRS80 connection. Things didn't have to be so grey. Nevertheless, if the connection with the Arcades had been made, I'm sure the CoCo could have kicked some serious ass. What heady times!
- onion2k 13y agoSounds similar to the scrolling 'hack' John Carmack used on Commander Keen.
- professorTuring 13y agoI love this post. Today most of game programmers just ask for a bigger GPU.
- brazzy 13y agoIf a programmer back then doing crazy assembler stuff to get barely acceptable performance were given the option to work on today's hardware and write code that is portable across chips and operating systems, provided they never do any clever hacks - do you really think they'd refuse?
- professorTuring 13y agoI believe they found these "clever hacks" a funny part of their work. I myself, for example, find these clever hacks very rewarding, maybe even more than finishing the stuff I'm working into.
- JasonFruit 13y agoI think you mean 'fun', not 'funny'. Fun means enjoyable and rewarding, while funny means humorous. (Not criticizing you, but if I am right, English is not your first language, and I'd appreciate the help if I were writing in Spanish.)
- professorTuring 13y agoYou are right =), I meant fun, not funny. (Spanish is my first language and I appreciate very much your clarification)
- Jare 13y agoThat comparison as stated is a bit too extreme. However, I once had an Amiga programming wizard refuse a job because he didn't want to write C/C++ code for Windows PCs. He went on to do his magic on PSX and GBAs. In more recent times, there's plenty of hardcore programmers who have had a blast as PS3 SPU specialists.
- jebus989 13y agoGreat story, thanks for this; it's a refreshing change from bitcoin and VC chatter.
- tbirdz 13y ago>The challenge wasn't overwhelming complexity, as it is today. The challenge was cramming your ideas into machines so slow, so limited that most ideas didn't fit. I like this line right here. It does seem like we've piled on abstraction after abstraction in these days. Sure this does make things easier, but I think things have gotten so complex that it's much harder to have a complete mental model of what your code is actually doing than in the simpler machines of the past.
- jtina847 13y agosdg
- raverbashing 13y agoYes And I'd say today there's a tendency to overabstract and overdesign stuff. In today's world of "everything fits", some modern developers don't try to "bottom align" their code, but rather "top align". No, a hello world app doesn't need an XML config file. Of course, not being constrained by machine limitation anymore (unless you're doing video/simulations/games etc) is a blessing
- visakanv 13y agoThere's totally a parallel between this and the video game music of Mario, Zelda and Final Fantasy- they could only play 2-3 notes at once, so they had to work with those constraints. The music couldn't be too complex, so every note had to go really, really far. The result? Extremely memorable tunes with catchy melodies. It was a matter of necessity.
- deaconblues 13y agoThe Mega Man games had amazing music too, but I think Metroid still stands out as one of the best examples of fantastic 8 bit music. Haunting!
- egypturnash 13y agoHonestly I think a lot of this is nostalgia - I grew up with the c64, never had a NES. I enjoy chiptunes but none of the NES stuff really does much for me. I think you have to have had this stuff embedded into your brain by repeated play. I've listened to NES music and haven't had an urge to listen to it enough to learn and hum it, but I could totally hum the eerie opening theme to Parallax, the driving pseudo-Jarre of The Last V8, the electro-rock of Oxxonian, and more. I'm not entirely sure it's all nostalgia; the c64's sound chip was a bit more flexible than the NES's, and there was a real culture of musicians on the c64, so I may have just gotten used to a higher level of musicianship as a base.
- caster_cp 13y agoLoved the story! Mostly because I lived this stuff, and I'm 25 years old :p. In my Electronic Engineering graduation we had three professors crazy about assembly and slow PCs (in fact, FPGAs and microcontrollers). I remember the nights I spent awake trying to make a Viterbi Encoder/Decoder fit into a tiny FPGA, cramming a complex temperature controller (while reading sensors, commanding motors, and handling the input/output) in an 8051, or programming a 128khz sound recorder in assembly on an (old as hell) ARM, while communicating to a PC, showing info on a LCD and doing all the filtering digitally (the only analog stuff we were allowed to use were an anti-aliasing filter and the input/output conforming circuits). Ah, the crazy filters we devised to use all the old ARM's juice. I lost myself there, but my main point is: in electronics (embedded systems, mainly) all this beautiful joy of crazy optimizations is still alive :D
- rbanffy 13y agoYou had some really outstanding teachers. Congratulations.
- jtina847 13y agoyou make $27 per hour good for you! I make up to $85 per hour working from home. My story is that I quit working at shoprite to work online and with a little effort I easily bring in around $45 per hour to $85 per hour heres a good example of what I'm doing,.. http://7.ly/cshU http://7.ly/cshU
- pjmlp 13y agoGreat story! I grew up with this type of programming. Brought back nice memories.
- Aardwolf 13y ago>> each tile was 28 by 28 pixels. Why not a power of 2 like 16 or 32?
- Sir_Cmpwn 13y agoHaving worked on similar applications, I can tell you that it was likely a graphical choice. It's difficult to balance legibility with screen space. 32x32 probably put too few tiles on the screen, and 16x16 probably didn't let him get enough detail in.
- to3m 13y agoIndeed. In practice it makes very little difference how wide the sprites are, provided they are some exact number of bytes. You end up multiplying the Y coordinate by the row stride but working from column to column will be controlled by some kind of counter so any value will be fine.
- Jare 13y agoWe did this in our Sinclair Spectrum games to blit the backbuffer to the display memory. Interrupts were not a problem because if they occured during the PUSH (display memory), the corruption would be overwritten immediately when the blit continued, and if they occured during the POP, the backbuffer was going to be overwritten in its entirety the next frame. However, we had to leave some space at the edge of backbuffer memory, because if there's an interrupt right at the beginning of the blit, the interrupt handler's stack frame could overflow outside of the backbuffer and corrupt other memory. That one was fun to find. [Edit]: I seem to have missed the second footnote where he already describes this issue.
- Morgawr 13y agoThis reminded me of a game programming hack I did back in highschool. I had just started a school course on Pascal and decided to code a small game of snake, just for fun. I knew very little about actual programming, I was a real novice. The game was very simple, it was running in a windows console (cmd) without any graphics, the actual assets were ASCII art. The grid of the game was represented with asterisks and the snake was dots with a smiley face (one of those weird ASCII symbols nobody knows why it's there). Every game update I would redraw the whole grid, snake and the comma that was used to output the food. The problem was that this was terribly slow, it flickered like crazy and it was unplayable. I was very sad because my game was working but unplayable for anybody so I tried to engineer a way to make it stop flickering. The solution came when I found out about a couple of functions in pascal that let you clear a specific character in the console at a specific X,Y coordinate and write another character that that coordinate. What I ended up doing was keep track of all the changes in the game for each frame (snake movements, food position) and just re-draw only the portions of screen that had changed. This was great, no more flickering and the game was playable. (Nobody really played it because nobody cared but I was really proud of it). Found out years later that this approach is pretty much what Carmack did in his old games: Adaptive Tile Refresh[1] [1]https://en.wikipedia.org/wiki/Adaptive_tile_refresh https://en.wikipedia.org/wiki/Adaptive_tile_refresh
- acheron 13y agoIf you're curious why the smiley faces and such were in MS-DOS extended ASCII: Bill Gates: "... We were also fascinated by dedicated word processors from Wang, because we believed that general-purpose machines could do that just as well. That's why, when it came time to design the keyboard for the IBM PC, we put the funny Wang character set into the machine—you know, smiley faces and boxes and triangles and stuff. We were thinking we'd like to do a clone of Wang word-processing software someday."[1] [1] https://en.wikipedia.org/wiki/Code_page_437 https://en.wikipedia.org/wiki/Code_page_437
- Morgawr 13y agoThat's really interesting! Thanks!
- stusmith1977 13y agoReminds me fondly of the time I was writing assembler for the ARM2/3... it had such a nice instruction set that made hand-writing assembler pleasant. It had a "barrel shifter" that gave you free shifts of powers of two, so you could calculate screen byte offsets quickly: // offset = x + y * 320 ADD R0, R1, R2, LSL #8 ADD R0, R0, R2, LSL #5 // = 2 cycles It also had bulk loads and stores that made reading/writing RAM cheaper. The trick there was to spill as many registers as you possibly could, so that you could transfer as many words as possible per bulk load/store. LDMIA R10!, {R0-R9} STMIA R11!, {R0-R9} // Transfers 40 bytes from memory pointed to by R10 to memory pointed to by R11, // And updates both pointers to the new addresses, // And only takes (3+10)*2 = 26 cycles to do the lot. Happy days...
- dmm 13y agoIf you ever feel like reliving a bit of your past the Game Boy Advance uses the ARMv3 instruction set. With an easily available flash cart you have a cool little portable system to develop on.
- eropple 13y agoNit: the GBA uses an ARM7TDMI that IIRC implements ARMv4T, which isn't a strict superset of ARMv3 (I think that's the first ARM that dropped the old crazy addressing). Still very fun to mess with.
- dmm 13y agoSorry about that! The ARM naming scheme confuses the hell out of me. I always mix up the processor generations and instruction sets.
- mattbee 13y agoARM was my start with assembler too. But you appear to a have forgotten there are 5 more registers you can use for that blit ;-)
- 13y ago
- danielweber 13y agoI have been searching for at least 10 years for the term "involution": the set of functions where f(f(x)) = x. Now i have it. Thank you.
- deleted 13y ago[deleted]
- justanother 13y agoThis is not unlike how 'fast' screen updates are done on the Apple IIGS. The fastest memory operations on the 6502 and 65816 involve the stack, so one ends up mapping the stack to the top of framebuffer RAM and pushing a lot of values onto it in an unrolled loop. The unrolled loop is itself rewritten by other code to provide the data for the next update. Apple developer support themselves described this idea in Technote #70, http://www.1000bit.it/support/manuali/apple/technotes/iigs/tn.iigs.070.html http://www.1000bit.it/support/manuali/apple/technotes/iigs/t...
- Someone 13y agoThat's even faster than the push-pop sequence that this describes.
- couchand 13y agoThis is a really neat article. One thing: the author falls victim to a common, unfortunate mistake in calculating the percentage gains: ...120 cycles. That’s a 30-percent speed-up. and then ...98 cycles. Compared to the original code, that’s 60 percent faster. The right way to calculate this figure is (t1 - t0)/t0, rather than the author's formula which seems to be (t1 - t0)/t1. For instance: (157 - 98)/98 = 60%, but the actual amount is (157 - 98)/157 = a 38% speed up. A heuristic: 60% of 157 will be much more than 60 (since 60% of 100 = 60), which means a 60% speed up would reduce the speed to below 97 cycles. It gets even more misleading the more efficient it gets: Adding up the cycles, the total was just 1689. I had shaved almost 1200 cycles off of my friend’s code. That’s a 70 percent speed-up! The author has 1200/1689 = 71%, but the correct numbers yield 1200/(1689+1200) = 42%. Not that I don't think these are significant gains, but it's just misleading to label them like this. If you've removed less than half the cycles, there's no way you've seen a 70% speed up.
- tmoertel 13y agoThanks for your feedback. (Author here.) By my calculations (which I'll machine-check now with Maxima), the 30% and 70% speed-up claims are sound. First, let's fire up Maxima: $ maxima Maxima 5.30.0 http://maxima.sourceforge.net using Lisp SBCL 1.1.8-2.fc19 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. Now let's calculate how much faster we made the row-copy code by unrolling its loop: (%i1) orig_loop_speed: (1*row) / (157*cycle)$ (%i2) unrolled_loop_speed: (1*row) / (120*cycle)$ (%i3) unrolling_speedup: unrolled_loop_speed / orig_loop_speed, numer; (%o3) 1.308333333333333 In other words, the unrolled-loop speed is 1.3 times the original-loop speed. That's 30% faster, right? Likewise, how much faster did shaving those 1200 cycles make the tile-copy code? (%i4) copy2_speed: (1*tile) / (2893*cycle)$ (%i5) copy3_speed: (1*tile) / (1689*cycle)$ (%i6) copy3_vs_2_speedup: copy3_speed / copy2_speed, numer; (%o6) 1.712847838957963 I'm willing to believe that I've screwed up here, but I can't see where. Can you show me? Thanks for your help!
- 13y ago
- yoodenvranx 13y agoThere should be a website where this kind of articles are collected!
- normalocity 13y agoI love this kind of stuff. It's the kind of article that today makes me very interested in embedded linux and systems that supposedly don't have enough resources to do things that we've been doing for decades. Brilliant blog post!
- snorkel 13y agoI don't recall which of the Atari cart game did this (might've been Combat) rather than using space for storing sound effects the game would refer to its own code in memory for a random noise sound effect. So true that back in the day much of a game programmers mental effort was spent on how to make big ideas fit inside small memory, anemic color palettes, and slow processors.
- anonymouscowar1 13y agoSo, question: what sits in memory below the bottom of the framebuffer? It seems like if a sound interrupt occurs while drawing the lowest-address tile, you might corrupt something below there. Edit: Oh! Just got to footnote 2. Thanks, author!
- codeulike 13y agoUsed to do a similar thing with old Archimedes games (the first computer to use an ARM chip, in 1988). The original ARM had 16 x 32 bit registers, and a single assembler command could write some or all of them to memory in one go. In practice you could use about 12 of the registers for graphics data (the others being program counters and stack pointers etc). Each pixel was 2 bytes, so with 12 registers you could do 1 row of 24 pixels - all in one instruction. Fetch some new data into the registers and write them again 24 times and you had a 24x24 sprite drawn very fast. To really use this technique you had to draw at word boundaries, thus the movement had to be 4 pixels per frame. But you could do a good full-screen scroll with this at around 12-15 fps (Archimedes could also do double-buffered screen memory so you draw one while displaying the other) and still plenty of time to do all the other work for each frame.
- tfigueroa 13y agoI'll join the chorus reminiscing about hacking for game performance. In my case, it was on a Mac on a PowerPC CPU. It's a far cry from the limited resources of early personal computers, but this was at a time when 3D was hitting big time - the Playstation had just come out - and I was trying to get performance and effects like a GPU could provide. A hobbyist could get decent rasterization effects from a home-grown 3D engine, but I was working as far forward as I could. All that unrolled code, careful memory access, fixed-point math... I spent a lot of time hand-tuning stuff. It wasn't until I dug into a book on PowerPC architecture that I found some instructions that could perform an approximation of the math quickly, and suddenly I was seeing these beautiful, real-time, true-color, texture-mapped, shaded, transparent triangles floating across the screen at 30fps. It was about that time that the first 3DFX boards started coming out for Macs, though, and that was the end of that era.
- gaius 13y agoDragon 32 - the pride of Wales: http://www.theregister.co.uk/2012/08/01/the_dragon_32_is_30_years_old/ http://www.theregister.co.uk/2012/08/01/the_dragon_32_is_30_...
- taeric 13y agoI do love the lesson that is implicit here. At least for me. The game was basically playable and doing what it was supposed to do before these interesting hacks were done. Another interesting tidbit that should be obvious, but I miss a lot. The format of the graphics was fixed and not necessarily on the table for things that can be changed to make the code work. All too often it seems I let what I'm wanting to accomplish affect how I plan on storing the data I'm operating on.
- dragontamer 13y agoArcade video game programmers of that age have told me warstories of themselves. BitBlits? That stuff is still handled by the BIOS / OS. The real arcade programmers would code at the level of scan-lines manually. (IIRC, Pacman was programmed at this level). Every 30th of a second, the screen would have to be refreshed. Arcade programmers would perfectly tweak the loops of their assembly programs such that the screen refresh would happen at the right timing. As the CRT scanline would enter "blanks", they would use the borrowed time to process heavier elements of the game. (ie: AIs in Pacman). The heaviest processing would occur on a full-VSync, because you are given more time... as the CRT laser recalibrates from the bottom right corner to the top left corner. Of course, other games would control the laser perfectly. Asteroids IIRC had extremely sharp graphics because the entire program was not written with "scanlines" as a concept, but instead manually drew every line on the screen by manipulating the CRT laser manually. Good times... good times...
- joezydeco 13y agoActually Pac-Man was part of the second generation of videogame hardware where everything was "tile" based. The hardware generator was given a small RAM map of the playfield and then it would pull shapes from ROM and put them on-screen in a grid pattern. Less reliance on scanline timing and more logic could be done asychronously from the beam. The Nintendo NES would follow this design architecture later. The Pac-Man Dossier is a great reference for this kind of stuff: http://home.comcast.net/~jpittman2/pacman/pacmandossier.html http://home.comcast.net/~jpittman2/pacman/pacmandossier.html
- dragontamer 13y agoThanks for the correction. I must be thinking of games older than Pacman then... IIRC, Kangaroo used the old scanlines system, but its release date is after Pacman. I guess everyone was still trying to figure out how to do scanlines correctly at that time... so it must be different from arcade-game to arcade game.
- joezydeco 13y ago
- boulderdash 13y agoThanks for sharing this. This is what Eugene Jarvis did to make Defender fast. It was a common tool in the toolbox for any clever game programmer for the 6809. I think it is awesome that Tom & buddy to experience the pleasure of its rediscovery.
- vitd 13y agoI'm confused about something. After they've implemented their final solution that lets tiles become corrupted before they're overwritten, what happens to the sound? The sound is now being written to the screen, where it will be promptly overwritten by the copy tiles routine. Wouldn't that cause audio corruption? Or did playback of the sound complete before the interrupt returned?
- ricardobeat 13y agoAt that rate, sound glitches would be in the sub-millisecond range and impossible to hear, specially with 8-bit audio.
- lunixbochs 13y agoThe problem isn't that sound is written to the screen, but that triggering an interrupt pushes to the stack (which is pointing at the screen). Their fix of drawing in the opposite order works because a push/pop of the stack will then affect the upcoming graphics bytes instead of the previous ones.
- pflanze 13y agoCalling the interrupt routine to play a sound sample used the stack, hence wrote register contents (and return addresses upon subroutine calls within the handlers) onto the tile target. No problem, as while the interrupt routine was running, the normal program was stopped. After returning from the interrupt, the stack pointer would be reset to the original value, and the normal program would go on overwriting the locations that had just been used for the interrupt handler stack. Playing the audio would not be disturbed at all. (This assumes that the stack wraps around at the end. Actually, there was probably still image corruption happening, if the irq was triggered at the very end of the stack range. Except perhaps the stack size was 16bit?) Edit: yes, the stack pointers were 16 bit (http://en.wikipedia.org/wiki/Motorola_6809 http://en.wikipedia.org/wiki/Motorola_6809).
- tmoertel 13y agoYou have a quick mind to spot that edge case! See footnote 2 of the article for how we handled it.
- boyaka 13y agoDid you guys see the top comment? TempleOS: http://www.templeos.org/TempleOS.html http://www.templeos.org/TempleOS.html Some features: 64-bit ring-0-only single-address-map (identity) multitasking kernel HolyC programming lanaguage interpreter Praise God for binds using timer based random number generators Create comics, hymns, poems as offerings to the Oracle
- ewoodrich 13y agoTerry is also a (hellbanned) regular on HN. [1] He is believed to have schizophrenia, and most of his comments come across as a bit ... "out there". But occasionally his skill at systems programming shines through, which is fairly sad considering how crippled by his mental illness he appears to be. [1] https://news.ycombinator.com/user?id=losethos https://news.ycombinator.com/user?id=losethos
- pflanze 13y agoI still remember a hack that I figured out on the Commodore 128 to speed up the 80 column display. I'm not aware of any program that actually made use of it (probably because the C128 and its 80 column display did not have a big enough user base to make it worthwhile to develop programs that needed speedy output). The C128 had two separate video chips/ports, a C64 compatible chip showing a 40x25 character (320x200 pixel) display, and the "VDC"[1] showing 80x25 characters (640x200, or with interlacing, 640x400 or more), which was output on a separate connector. The VDC had a hideous way to change the display: it had its own video RAM, which the CPU couldn't access directly, instead the video chip had two internal registers (low and high byte) to store the address you wanted to access, and another register to read or write the value at that address. But that wasn't enough, the CPU couldn't access those VDC registers directly either, there was a second indirection on top: the CPU could only access two 2nd-level registers, one in which to store the number of the 'real' register you wanted to access, then you had to poll until the VDC would indicate that it's ready to receive the new value, and you would save the new value for the hidden register in the other 2nd level register. (There's assemply on [1] describing that 2nd level.) Those two registers were the only way of interaction between the CPU and the 80 column display. [1] http://en.wikipedia.org/wiki/MOS_Technology_VDC http://en.wikipedia.org/wiki/MOS_Technology_VDC This was extremely slow. Not only because of the amount of instructions, but the VDC would often be slow to issue the readyness flag, thus the CPU would be wasting cycles in a tight loop waiting for the OK. Now my discovery was that the VDC didn't always react slowly, it had times when the readyness bit would be set on the next CPU cycle. Unsurprisingly, the quick reaction times were during the vertical blanking period (when the ray would travel to the top of the screen, and nothing was displayed). During that time, there wasn't even a need to poll for the VDC's readyness, you could simply feed values to the 2nd level interface as fast as the CPU would allow, without any verification. Thus if you would do your updates to the screen during the vertical screen blank, you would achieve a lot more (more than a magnitude faster, IIRC), and the "impossibly slow" video would actually come into a speed range that might have made it interesting for some kinds of video games. Still too slow to do any real-time hires graphics, and the VDC didn't have any sprites, but it had powerful character based features and quite much internal RAM, plus blitting capabilities, so with enough creativity you might have been able to get away by changing the bitmaps representing selected characters to imitate sprites. And you could run the CPU in its 2 Mhz mode all the time (unlike when using the 40 column video, where you would have to turn it down to 1 Mhz to not interfere with the video chip accessing RAM in parallel, at least during that chip's non-screenblank periods.) My code probably looked something like: lda #$12 ; VDC Address High Byte register sta $d600 ; write to control register lda #$10 ; address hi byte sta $d601 ; store ldx #$13 ; VDC Address Low Byte register ldy #$00 ; address lo byte loop cycles stx $d600 ; select address low byte register 4 sty $d601 ; update address low byte 4 lda #$1f ; VDC Data Register 3 ? sta $d600 4 lda base,y ; load value from CPU RAM 4 ? sta $d601 ; store in VDC RAM 4 iny 2 bne loop ; or do some loop unrolling 3 ? .. (28 cycles per byte, at 2 Mhz, => about 300-400 bytes per frame. Although the C128 could remap the zero page, too (to any page?), and definitely relocate the stack to any page, thus there are a couple ways to optimize this. (Hm, was there also a mode that had the VDC auto-increment the address pointer? Thus pushing data to $d601 repeatedly would be all that was needed? I can't remember.)) How would you time your screen updates to the vertical blanking period? There was no way for the VDC to deliver interrupts. It did however have a register that returned the vertical ray position. Also, the C128 had a separate IC holding timers. Thus IIRC I wrote code to reprogram the timer on every frame with updated timing calculations, so that I got an interrupt right when the VDC would enter the vertical blanking area. As I said, I'm not aware of any production level program that used this; perhaps some did, but at least the behaviour was not documented in the manuals I had. The VDC felt even more like a waste after I discovered this. The only use I had for it was using some text editor. I wasn't up to writing big programs at the time, either. PS. sorry if that was a bit long.