Masters of Doom is a great book on the history of id software, which includes the origins of the development of smooth scrolling by Carmack and Romero, which was groundbreaking at the time on PC.
The underlying mechanics of Carmack's technique is very similar to the full screen smooth scrolling effect on C64 at any speed and distance. It is nowadays referred to as DMA delay.
ELIF: You trick the CPU to display screen data at a different starting point than as designed by the hardware. This is tricky and need to be executed cycle exact.
Here is the explanation in detail together with all major top notch effects. The article is a legend and kind of the bible of doing the most sophisticated effects on C64. Some effects have since then even more and better explained and exploited due to cross platform development possibilities and better tooling, but understanding all mechanics here is a necessity to play a role in the Champions League of C64 demos, besides and also being able to implement the techniques mentioned here:
https://www.zimmers.net/cbmpics/cbm/c64/vic-ii.txt
> ELIF: You trick the CPU to display screen data at a different starting point than as designed by the hardware. This is tricky and need to be executed cycle exact.
heh, is there a new meaning for ELIF? im not sure that there are many 5 year olds who would understand that ;-)
I was going to say, smooth scrolling is one place where VGA was fairly simple to work with, since it didn’t have to deal with chunky graphics/bitplanes or specific timing tricks.
In fact, Carmack specifically states that packed pixels were the impetus for id’s side scrolling experiments that led to Commander Keen and its ilk.
It should be noted that John Romero released his own book, Doom Guy, a few years ago which contradicts some of the accounts in Masters of Doom. MoD is probably the more thrilling read and I enjoyed both books, but some of the stories need to be taken with a grain of salt.
I also think Doom Guy is worth a read because it gives a lot more insight into what happened at Ion Storm and how the Daikatana project fell apart. And some important context about the infamous "John Romero's about to make you his bitch" ad (mainly that he really didn't want to publish it at all). But I digress.
I would recommend the audiobook - John Romero actually reads it so it seems a lot more personal.
I did feel that Romero skipped a load of stuff, at least int he audio version. There was no real mention of Stevie Case, just one passing name check. That was really odd. I was expecting him to at least mention her.
I've also both read and listened to Masters of Doom (read by Wil Wheaton no less) and it is a great book too. The audio version is really good.
Yeah that's confirmed in Masters of Doom as well - sounds like Romero was a bit hesitant about it but Mike Wilson, the marketing guy, pushed him into it.
One thing I was sus from the book and which this post didn't clarify for me was whether Carmack truly invented side scrolling for the PC. He claimed to have done so, and even pitched it to Nintendo for a Mario port that never took off.
Also, the idea that it hadn't been done yet by 1990, when consoles were well in the game, suggests the PC market was behind popular gaming in a big way.
The consoles at the time had dedicated sprite video RAM and hardware and dedicated hardware instructions for background scrolling. The NES for instance had up to 64 sprites (independently moving 16x16 or 32x32 pixel images) supporting up to 8 of those sprites per scanline. The NES background layer was a relatively simple tile map that supported smooth scrolling. All of which was managed by a dedicated hardware Picture Processing Unit [1].
PCs were designed to be general hardware and it didn't seem to make sense to create a generic "PPU" for the PC, so instead game engines at the time (and many game engines to this day) had to emulate one entirely in software. The video RAM of EGA and VGA is just one big blob of pixels, or perhaps two if your system supported double-buffering. At the hardware level it doesn't have concepts like sprites or scrolling backgrounds.
Carmack was one of the first (if not the first; Commander Keen was also among the first commercially successful attempts) to get a software "PPU" renderer on the PC working reliably in real time. Another notable achievement for side scrollers on the PC in that era was Cliff Bleszinski managing to software render the parallax effects similar to Sega's "Blast processor" PPU (notable for "gotta go fast" Sonic games) for Jazz Jackrabbit (in 1994).
It has sort of long been the arc of PC development of eventually doing entirely in software what consoles and arcades were doing with dedicated and/or one-off hardware. (Right up until about the invention of the modern GPU when suddenly the PC was leading graphics hardware in a different way.)
I've been following the Japanese early gaming scene, which had a lot of parallels to the west. They had NEC PCs running DOS, and there were a lot of games for the systems. Some of them had smooth scrolling. Did they come later? Did they copy ID Software's approach?
Lovely book. Skimming through it. One thing that might help contextualize it is a brief discussion of the how contemporary hardware like the SNES rendered sprites so efficiently compared to the PC hardware at the time. It's not obvious to modern readers why a PC with significantly more powerful compute capabilities would struggle to keep up with significantly slower Nintendo hardware at the time for sprite rendering.
>It's not obvious to modern readers why a PC with significantly more powerful compute capabilities would struggle to keep up with significantly slower Nintendo hardware at the time for sprite rendering.
To put it briefly, 4th generation and earlier games consoles saved on expensive RAM by not having frame buffers [0]. The CPU wrote a description of how to construct the scene using tiles and sprites to a smaller video ram, then dedicated video hardware converted this to the video signal one line at a time. The whole frame gets rendered from scratch every video refresh, so there's no need for tricks like Commander Keen's adaptive tile refresh. Scrolling at 60 fps (or 50 fps for PAL hardware) is as cheap as changing a single value in video memory. It's like the famous "racing the beam" of the Atari 2600, except less flexible and done by dedicated hardware so you don't tie up the CPU.
On the PC, the CPU writes the actual graphics to a frame buffer, then the graphics card outputs the contents of the frame buffer as the video signal. The naive approach to scrolling requires rewriting the entire frame buffer, so tricks to avoid redundant writes are highly beneficial.
[0] Except for the Atari Lynx, which was a portable system with a screen resolution of only 160×102. I can't think of any other exceptions, but maybe there are more.
I get what you're saying, but the comparison to "racing the beam" is maybe a little misleading, because the point is that you aren't "racing" the beam. Rather, the system is operating in perfect lockstep with the beam. From the software perspective, you set the scene up and then sit back while it draws. And then in the abstract and from the hardware's perspective it's not even one line at a time, it's one dot at a time.
>Rather, the system is operating in perfect lockstep with the beam.
That's the same as the Atari 2600. It just occurred to me that the name "racing the beam" is misleading because you can't be too fast either. "Matching the beam" would be a better name. My point is the graphics hardware in both the 2600 and in tile+sprite consoles assembles the graphics just before it's sent to the video output without buffering the whole frame. The main difference is the 2600 graphics hardware is typically reconfigured every line while the later consoles' graphics hardware is typically reconfigured every frame (although re-configuring between lines is usually also possible, and some games left it unchanged on some screen refreshes to save CPU time at the expense of lowering frame rate).
>from the hardware's perspective it's not even one line at a time, it's one dot at a time.
Mostly true, but I tried to make the description generic to as many systems as possible, so "line" is IMO more broadly accurate because a line is composed of dots. The Neo Geo is a tile + sprite system too, and it renders to line buffers.
It's basically a case of hardware acceleration. Most games consoles and fancier micros have some of dedicated graphics chip that handles the heavy lifting of generating graphics. So for basic game graphics the CPU largely acts as a manager adjusting things like tilemaps and their viewport offsets, and sprite locations (possibly updating things several times mid frame, for fancier effects). The exact setup differs between systems, tilemaps and spites like the SNES is common, though you also have setups with some sort of framebuffer and a Blitter to speed up drawing to it instead.
A traditional IBM PC has a "dumb" framebuffer, where everything is done by the PC. Simply scrolling the background by 1 pixel basically means redrawing a lot of the screen, and you have to keep track of what graphics behind sprite would need to be redrawn after they move etc. As a bonus, on early consumer level 386 and 486 machines you have a mighty processor, but the graphics card is often still on a 16 bit 8MHz(ish) ISA bus. The PC does have an advantage that it's more flexible, so stuff like 3D was easier to do than on a tile-and-sprite setup (especially once we had stuff like VESA and PCI).
the Gameboy, not the SNES, but this talk is very very good at going in detail about a bunch of internals. The graphics stuff is 29 minutes in but I love the whole video. Very much a high level guide to building a "retro-y" fantasy console for people into that stuff
I had no idea you could still get it. This brings back memories! My first and favourite game as a kid. I'd get home from school, boot up the DOS machine and type 'keen.exe' to start it up.
"...I discovered Fabien Sanglard’s website and began reading his Game Engine Black Books on Wolfenstein 3D and Doom. Inspired by those works, I wondered whether I could do something similar for Commander Keen: open up the source code, explore the files, and piece together a picture of the overall architecture and the clever tricks used. The style, dimensions, and structure of this book are intentionally similar to Fabien’s Game Engine Black Books, as an homage to those masterpieces. To give it a personal twist, I inverted the title and cover to white."
How do you feel about this book mirroring your prior art in both format and structure? Were you consulted beforehand?
[EDIT] - I see in the Keen book's source git commit logs that you reviewed and assisted with proof reading beforehand, so may we assume that this is all above board and sanctioned by you?
I suppose there's still Quake 3 Arena and DOOM3 to complete the full "John Carmack" early 90s to early 2000s technical overview series.
Or maybe something with the Sega Saturn. I heard the Sonic X-treme team worked so hard to make a 3d Sonic game for that platform in the mid 90s that multiple team members had to go on medical leave!
This quote is attributed to Oscar Wilde, but it seems like he never said it. In fact, there is no direct source for this particular quote by anyone. Even the shorter version "Imitation is the greatest form of lattery" is much older than Oscar Wilde. The full quote apparently did not appear on the internet before 2012.
I think it's a really cool homage, but that the site could be a little clearer that it's not Fabien's work. When I first clicked through and saw a different name, I was hopeful that someone had started a publishing house dedicated to high-quality dissections of classic games.
It appears the author is leveraging Fabien's branding by copying not only the style of post but more importantly the formatting and style of Fabien's books. Even structurally the book appears quite similar.
If you didn't double check the author while skimming this Keen book, you may well be mistaken that it was written by Fabien.
I took a quick skim of the content, it looks great - tempted to purchase a copy to support the author for their efforts (and have it sit on the bookshelf next to two other very similar looking books...) but need to sit on this for a while.
Maybe I'm overthinking this. Would like to hear Fabien's take on the situation.
[EDIT] It looks that the Keen book author copied and pasted direct sections[1] out of Fabien's book's TeX[2].
[EDIT] The git commit history has comments that indicate that Fabien reviewed the book, e.g. "updated all chapters after feedback Fabien" and "Proofread Fabien Sanglard en hardcopy review", so perhaps this is all sanctioned.
I received early draft from bas. While I encouraged him to finish his book, I also told him, in no uncertain terms, that I had released the source code to inspire people and give them a kickstart, but not for them to copy the content.
As months passed, I asked repeatedly to remove whole paragraphs he had copy/pasted as is, and drawings he had also copy/pasted. Later, as A.I became more powerful, I used it to compare Wolfenstein 3D and Keen book and noticed a lot more that was verbatim. At which point I told him I no longer wanted to help him in his project.
It is cool that someone documented Keen thanks to my framework. But I have only myself to blame for opensourcing the code of my books/website and thinking people would use it as intended.
PS: I commented it was a "good idea" to change the cover because originally this was going to be the "Game Engine Black Book: Commander Keen". I did not like that his work could have been mistaken for mine (he also elected to use the same style as my website for his website which only adds to the confusion).
Thanks for the clarifying the situation. Something did feel a bit off but I didn't want to jump to any premature conclusions.
The author has clearly put quite some investment in writing their book, it's a shame and hard to understand that someone would self sabotage by plagiarising the work of others - Especially to someone donating their own free time to initially help out.
> But I have only myself to blame for opensourcing the code of my books/website and thinking people would use it as intended.
Even if you had not, perhaps this scenario would have still eventuated.
Keep up the good work. Any new books planned on the horizon?
... Well, we do at least have OpenTyrian... (Edited to add; And OpenTyrian2000)
> Epic Pinball
Best I can find for Epic Pinball is an old thread on Pinball Fantasies [0] but I think it almost counts cause there was shared dev work between the two...
> Halloween Harry
TBH that one would be fairly interesting, especially compared to Duke Nukem 2 (Part of me thinks they might be similar/same engine)
> Jill of the Jungle
That one honestly WOULD be a fun one to look at... Best I can find is Xargon [1] but part of me always got a vibe that Xargon was some semi-upgraded Jill engine...
> Duke Nukem
TBH Duke Nukem '1' would not be that exciting to me. AFAIR it's mostly an adapted CK1-3 engine, letter-boxed with status window to make it easier to calc the redraw.
Duke Nukem 2, is far more interesting since it's a different, more powerful engine (VGA, digital audio support, but AFAIR only required a 286).
IIRC (from being a kid) Harry was 256 color and DN2 wasn’t quite. Also it felt like it had much better frame rate. But I’m sure that could be engine evolution too. Interesting, I hadn’t ever thought of the connection before.
Though the “hot babes stuck in alien pods” from Harry showed up as a central plot point in DN3D.
I mean, I could be wrong as far as Harry and DN2 sharing an engine, OTOH Apogee did a -lot- of engine reuse (Bio-Menace used a CK4 variant, Monster Bash using an evolved FAST..)
Although, mea culpa, DN1 engine is not necessarily CK but the programmer has credited Carmack in helping with the drawing assembly...
Harry was written by an Australia, John Passfield, on his own and published by apogee (I forget but apogee might have provided some art support). John is still making games today!
I also think the story of Duke Nukem 3D (1996) and the development of the BUILD engine by Ken Silverman would also be a really interesting technical read.
Given its open source in latex format, it should be pretty easy to render it in any format that isn’t asking for significant decision-making on how to structure and format it.
Ie. Rendering to PDF or HTML would be pretty straightforward. Rendering to video, audio, or as a chocolate bar would require more authorship. Would epub be much more work?
I can understand the feeling of loyalty to a widely admired figure (and deservedly so!) but this isn't a great way to respond to someone else's work. Unless there's some evidence of ill intent, why not just classify it as an homage?
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
"Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith."
Fabien's site is an invaluable resource, but I think I've read it all over the years and he one has post specifically on Commander Keen, and that's focused on just the adaptive tile refresh (https://fabiensanglard.net/ega/). This book is 211 pages on the entire game.
On the first page this author credits Fabian's excellent analysis of Doom and Wolfenstein as the inspiration to attempt the same for Commander Keen.
> "Fast forward to 2021, I discovered Fabien Sanglard’s website and began reading his Game
Engine Black Books on Wolfenstein 3D and Doom. Inspired by those works, I wondered
whether I could do something similar for Commander Keen: open up the source code, ex
plore the files, and piece together a picture of the overall architecture and the clever tricks
used. The style, dimensions, and structure of this book are intentionally similar to Fabien’s
Game Engine Black Books, as an homage to those masterpieces."
Just skimming so far, but this book looks like a valuable contribution to the genre of retro game code analysis. Obviously, it will build on the work of others who've done adjacent research. In a page 87 footnote the author refers readers to Fabien's site for detailed instructions on installing a DOSBox and Borland C++ dev environment.
First, shallow dismissals are against HN guidelines, for a good reason.
And I fail to make the connection. This content-heavy but minimal design is not unique.
Text inside a centered element, text-heavy but also packed with images, exists from the times of formatinng websites with `<table>` tags in DreamWeaver or Microsoft Frontpage 98.
If you're talking about the highly detailed article, can we not gatekeep this? I want more of that on the internet, not less.
From the preface:
> Fast forward to 2021, I discovered Fabien Sanglard’s website and began reading his Game Engine Black Books on Wolfenstein 3D and Doom. Inspired by those works, I wondered whether I could do something similar for Commander Keen: open up the source code, explore the files, and piece together a picture of the overall architecture and the clever tricks used. The style, dimensions, and structure of this book are intentionally similar to Fabien’s Game Engine Black Books, as an homage to those masterpieces. To give it a personal twist, I inverted the title and cover to white.
Yeesh, until I saw your comment I thought this was Fabien. I'm sure it's not intentional but this goes beyond "homage" and into "deceptive". The replies to this claiming to not see what the issue is are inexplicable to me.
The work on the book itself looks fantastic, so it's a shame about the site design.
It's often helpful not to immediately assume bad faith without further enquiry. It appears that Fabien had reviewed the book beforehand and he has reposted John Carmack's tweet[1] linking the book.
Understood. It's reasonable to call out potential conflict while also being unclear on intention. Something as simple in the Keen book author acknowledging the proofreader would put to rest the ambiguity central to the discussion point in contention.
Eh, it's not so clear cut. LLMs have definitely killed a lot of fun in reverse engineering old games by making it trivial to solve riddles that in the past would have been interesting problems to work on.
But the field still offers many mysteries that need human brains to be solved.
Whether LLMs are a net positive here depends if one is result-oriented (e.g. wants to rewrite an old game in a modern language) or process-oriented (is there for the investigation work and the intellectual challenges).
It's a shame that the author both erased their own writing style using ChatGPT, and wholesale copied sections of the content from another author.
https://news.ycombinator.com/item?id=48550425
It looks like a complete rip-off. Both the design of the website and the book cover.
Masters of Doom is a great book on the history of id software, which includes the origins of the development of smooth scrolling by Carmack and Romero, which was groundbreaking at the time on PC.
Fun fact for C64 guys:
The underlying mechanics of Carmack's technique is very similar to the full screen smooth scrolling effect on C64 at any speed and distance. It is nowadays referred to as DMA delay.
ELIF: You trick the CPU to display screen data at a different starting point than as designed by the hardware. This is tricky and need to be executed cycle exact.
Here is the explanation in detail together with all major top notch effects. The article is a legend and kind of the bible of doing the most sophisticated effects on C64. Some effects have since then even more and better explained and exploited due to cross platform development possibilities and better tooling, but understanding all mechanics here is a necessity to play a role in the Champions League of C64 demos, besides and also being able to implement the techniques mentioned here: https://www.zimmers.net/cbmpics/cbm/c64/vic-ii.txt
> ELIF: You trick the CPU to display screen data at a different starting point than as designed by the hardware. This is tricky and need to be executed cycle exact.
heh, is there a new meaning for ELIF? im not sure that there are many 5 year olds who would understand that ;-)
ELI5: explain like I'm five,
ELIF: explain like I'm forty.
explain like i'm fifteen, surely (:
Fifty? Fungified? Faded? Fading? Foreign? Fabulous? Explain like I'm face-palming/fainting?
F is 15 in hex :)
To clarify, it does not need to be executed cycle exact on the IBM PC, only on the C64.
I was going to say, smooth scrolling is one place where VGA was fairly simple to work with, since it didn’t have to deal with chunky graphics/bitplanes or specific timing tricks.
In fact, Carmack specifically states that packed pixels were the impetus for id’s side scrolling experiments that led to Commander Keen and its ilk.
It should be noted that John Romero released his own book, Doom Guy, a few years ago which contradicts some of the accounts in Masters of Doom. MoD is probably the more thrilling read and I enjoyed both books, but some of the stories need to be taken with a grain of salt.
I also think Doom Guy is worth a read because it gives a lot more insight into what happened at Ion Storm and how the Daikatana project fell apart. And some important context about the infamous "John Romero's about to make you his bitch" ad (mainly that he really didn't want to publish it at all). But I digress.
I would recommend the audiobook - John Romero actually reads it so it seems a lot more personal.
I did feel that Romero skipped a load of stuff, at least int he audio version. There was no real mention of Stevie Case, just one passing name check. That was really odd. I was expecting him to at least mention her.
I've also both read and listened to Masters of Doom (read by Wil Wheaton no less) and it is a great book too. The audio version is really good.
Yeah that's confirmed in Masters of Doom as well - sounds like Romero was a bit hesitant about it but Mike Wilson, the marketing guy, pushed him into it.
Ah I couldn't remember if that was only confirmed in Doom Guy. Regardless, it's still worth a read.
One thing I was sus from the book and which this post didn't clarify for me was whether Carmack truly invented side scrolling for the PC. He claimed to have done so, and even pitched it to Nintendo for a Mario port that never took off.
Also, the idea that it hadn't been done yet by 1990, when consoles were well in the game, suggests the PC market was behind popular gaming in a big way.
The consoles at the time had dedicated sprite video RAM and hardware and dedicated hardware instructions for background scrolling. The NES for instance had up to 64 sprites (independently moving 16x16 or 32x32 pixel images) supporting up to 8 of those sprites per scanline. The NES background layer was a relatively simple tile map that supported smooth scrolling. All of which was managed by a dedicated hardware Picture Processing Unit [1].
PCs were designed to be general hardware and it didn't seem to make sense to create a generic "PPU" for the PC, so instead game engines at the time (and many game engines to this day) had to emulate one entirely in software. The video RAM of EGA and VGA is just one big blob of pixels, or perhaps two if your system supported double-buffering. At the hardware level it doesn't have concepts like sprites or scrolling backgrounds.
Carmack was one of the first (if not the first; Commander Keen was also among the first commercially successful attempts) to get a software "PPU" renderer on the PC working reliably in real time. Another notable achievement for side scrollers on the PC in that era was Cliff Bleszinski managing to software render the parallax effects similar to Sega's "Blast processor" PPU (notable for "gotta go fast" Sonic games) for Jazz Jackrabbit (in 1994).
It has sort of long been the arc of PC development of eventually doing entirely in software what consoles and arcades were doing with dedicated and/or one-off hardware. (Right up until about the invention of the modern GPU when suddenly the PC was leading graphics hardware in a different way.)
[1] https://www.nesdev.org/wiki/PPU
I've been following the Japanese early gaming scene, which had a lot of parallels to the west. They had NEC PCs running DOS, and there were a lot of games for the systems. Some of them had smooth scrolling. Did they come later? Did they copy ID Software's approach?
Lovely book. Skimming through it. One thing that might help contextualize it is a brief discussion of the how contemporary hardware like the SNES rendered sprites so efficiently compared to the PC hardware at the time. It's not obvious to modern readers why a PC with significantly more powerful compute capabilities would struggle to keep up with significantly slower Nintendo hardware at the time for sprite rendering.
>It's not obvious to modern readers why a PC with significantly more powerful compute capabilities would struggle to keep up with significantly slower Nintendo hardware at the time for sprite rendering.
To put it briefly, 4th generation and earlier games consoles saved on expensive RAM by not having frame buffers [0]. The CPU wrote a description of how to construct the scene using tiles and sprites to a smaller video ram, then dedicated video hardware converted this to the video signal one line at a time. The whole frame gets rendered from scratch every video refresh, so there's no need for tricks like Commander Keen's adaptive tile refresh. Scrolling at 60 fps (or 50 fps for PAL hardware) is as cheap as changing a single value in video memory. It's like the famous "racing the beam" of the Atari 2600, except less flexible and done by dedicated hardware so you don't tie up the CPU.
On the PC, the CPU writes the actual graphics to a frame buffer, then the graphics card outputs the contents of the frame buffer as the video signal. The naive approach to scrolling requires rewriting the entire frame buffer, so tricks to avoid redundant writes are highly beneficial.
[0] Except for the Atari Lynx, which was a portable system with a screen resolution of only 160×102. I can't think of any other exceptions, but maybe there are more.
I get what you're saying, but the comparison to "racing the beam" is maybe a little misleading, because the point is that you aren't "racing" the beam. Rather, the system is operating in perfect lockstep with the beam. From the software perspective, you set the scene up and then sit back while it draws. And then in the abstract and from the hardware's perspective it's not even one line at a time, it's one dot at a time.
>Rather, the system is operating in perfect lockstep with the beam.
That's the same as the Atari 2600. It just occurred to me that the name "racing the beam" is misleading because you can't be too fast either. "Matching the beam" would be a better name. My point is the graphics hardware in both the 2600 and in tile+sprite consoles assembles the graphics just before it's sent to the video output without buffering the whole frame. The main difference is the 2600 graphics hardware is typically reconfigured every line while the later consoles' graphics hardware is typically reconfigured every frame (although re-configuring between lines is usually also possible, and some games left it unchanged on some screen refreshes to save CPU time at the expense of lowering frame rate).
>from the hardware's perspective it's not even one line at a time, it's one dot at a time.
Mostly true, but I tried to make the description generic to as many systems as possible, so "line" is IMO more broadly accurate because a line is composed of dots. The Neo Geo is a tile + sprite system too, and it renders to line buffers.
It's basically a case of hardware acceleration. Most games consoles and fancier micros have some of dedicated graphics chip that handles the heavy lifting of generating graphics. So for basic game graphics the CPU largely acts as a manager adjusting things like tilemaps and their viewport offsets, and sprite locations (possibly updating things several times mid frame, for fancier effects). The exact setup differs between systems, tilemaps and spites like the SNES is common, though you also have setups with some sort of framebuffer and a Blitter to speed up drawing to it instead.
A traditional IBM PC has a "dumb" framebuffer, where everything is done by the PC. Simply scrolling the background by 1 pixel basically means redrawing a lot of the screen, and you have to keep track of what graphics behind sprite would need to be redrawn after they move etc. As a bonus, on early consumer level 386 and 486 machines you have a mighty processor, but the graphics card is often still on a 16 bit 8MHz(ish) ISA bus. The PC does have an advantage that it's more flexible, so stuff like 3D was easier to do than on a tile-and-sprite setup (especially once we had stuff like VESA and PCI).
These videos do an excellent job at explaining how the SNES works:
https://www.youtube.com/playlist?list=PLHQ0utQyFw5KCcj1ljIhE...
the Gameboy, not the SNES, but this talk is very very good at going in detail about a bunch of internals. The graphics stuff is 29 minutes in but I love the whole video. Very much a high level guide to building a "retro-y" fantasy console for people into that stuff
https://youtu.be/HyzD8pNlpwI?t=1759
If you want to play it you can do that here: https://www.playdosgames.com/play/commander-keen-4
It's also on Steam: https://store.steampowered.com/app/9180/Commander_Keen/
I had no idea you could still get it. This brings back memories! My first and favourite game as a kid. I'd get home from school, boot up the DOS machine and type 'keen.exe' to start it up.
Someone ping Fabien Sanglard! Looks so much like his site!
Author's note from the book:
"...I discovered Fabien Sanglard’s website and began reading his Game Engine Black Books on Wolfenstein 3D and Doom. Inspired by those works, I wondered whether I could do something similar for Commander Keen: open up the source code, explore the files, and piece together a picture of the overall architecture and the clever tricks used. The style, dimensions, and structure of this book are intentionally similar to Fabien’s Game Engine Black Books, as an homage to those masterpieces. To give it a personal twist, I inverted the title and cover to white."
> To give it a personal twist, I inverted the title and cover to white.
That is a great idea.
How do you feel about this book mirroring your prior art in both format and structure? Were you consulted beforehand?
[EDIT] - I see in the Keen book's source git commit logs that you reviewed and assisted with proof reading beforehand, so may we assume that this is all above board and sanctioned by you?
I replied here: https://news.ycombinator.com/item?id=48550425
Imitation is the greatest form of flattery!
I suppose there's still Quake 3 Arena and DOOM3 to complete the full "John Carmack" early 90s to early 2000s technical overview series.
Or maybe something with the Sega Saturn. I heard the Sonic X-treme team worked so hard to make a 3d Sonic game for that platform in the mid 90s that multiple team members had to go on medical leave!
> Imitation is the greatest form of flattery
"... that mediocrity can pay to greatness" is the rest of the quote.
This quote is attributed to Oscar Wilde, but it seems like he never said it. In fact, there is no direct source for this particular quote by anyone. Even the shorter version "Imitation is the greatest form of lattery" is much older than Oscar Wilde. The full quote apparently did not appear on the internet before 2012.
https://shkspr.mobi/blog/2024/01/no-oscar-wilde-did-not-say-...
I think it's a really cool homage, but that the site could be a little clearer that it's not Fabien's work. When I first clicked through and saw a different name, I was hopeful that someone had started a publishing house dedicated to high-quality dissections of classic games.
> the site could be a little clearer
I agree.
Wow I assumed it was one of his books before I saw your comment. Thanks for pointing that out!
And his site looks like another thousand, as I'm sure he knows.
We consume his site for the content, not for the minimalistic design that exist since the inception of the universe.
It appears the author is leveraging Fabien's branding by copying not only the style of post but more importantly the formatting and style of Fabien's books. Even structurally the book appears quite similar.
If you didn't double check the author while skimming this Keen book, you may well be mistaken that it was written by Fabien.
I took a quick skim of the content, it looks great - tempted to purchase a copy to support the author for their efforts (and have it sit on the bookshelf next to two other very similar looking books...) but need to sit on this for a while.
Maybe I'm overthinking this. Would like to hear Fabien's take on the situation.
[EDIT] It looks that the Keen book author copied and pasted direct sections[1] out of Fabien's book's TeX[2].
[EDIT] The git commit history has comments that indicate that Fabien reviewed the book, e.g. "updated all chapters after feedback Fabien" and "Proofread Fabien Sanglard en hardcopy review", so perhaps this is all sanctioned.
[1] https://github.com/bsmits74/Keen_White_Papers/blob/master/sr...
[2] https://github.com/fabiensanglard/gebbdoom/blob/master/src/b...
> perhaps this is all sanctioned
In short, it is not.
I received early draft from bas. While I encouraged him to finish his book, I also told him, in no uncertain terms, that I had released the source code to inspire people and give them a kickstart, but not for them to copy the content.
As months passed, I asked repeatedly to remove whole paragraphs he had copy/pasted as is, and drawings he had also copy/pasted. Later, as A.I became more powerful, I used it to compare Wolfenstein 3D and Keen book and noticed a lot more that was verbatim. At which point I told him I no longer wanted to help him in his project.
It is cool that someone documented Keen thanks to my framework. But I have only myself to blame for opensourcing the code of my books/website and thinking people would use it as intended.
PS: I commented it was a "good idea" to change the cover because originally this was going to be the "Game Engine Black Book: Commander Keen". I did not like that his work could have been mistaken for mine (he also elected to use the same style as my website for his website which only adds to the confusion).
Thanks for the clarifying the situation. Something did feel a bit off but I didn't want to jump to any premature conclusions.
The author has clearly put quite some investment in writing their book, it's a shame and hard to understand that someone would self sabotage by plagiarising the work of others - Especially to someone donating their own free time to initially help out.
> But I have only myself to blame for opensourcing the code of my books/website and thinking people would use it as intended.
Even if you had not, perhaps this scenario would have still eventuated.
Keep up the good work. Any new books planned on the horizon?
> Any new books planned on the horizon?
I always have projects :) ! Whether I can go all the way and actually ship it is another story.
Maybe in the future hand crafting code with the help of books is going to be an art. I’m sure some people would love to pay to watch.
(Going to do that in 10-15 years when I reach 50/55 to semi retire)
He responds to this thread here: https://news.ycombinator.com/item?id=48546779
Of related interest:
Reconstructed Commander Keen 1-3 Source Code
https://pckf.com/viewtopic.php?t=18248 (https://news.ycombinator.com/item?id=46321982)
Great write up. Reminds me of Cosmodoc, which is similar source but analyzes Cosmo’s Cosmic Adventure instead of Commander Keen.
https://cosmodoc.org
Would love to hear about the other Apogee and Epic games, like Epic Pinball, Tyrain, Halloween Harry, Jill of the Jungle, Duke Nukem...
> Tyrain
... Well, we do at least have OpenTyrian... (Edited to add; And OpenTyrian2000)
> Epic Pinball
Best I can find for Epic Pinball is an old thread on Pinball Fantasies [0] but I think it almost counts cause there was shared dev work between the two...
> Halloween Harry
TBH that one would be fairly interesting, especially compared to Duke Nukem 2 (Part of me thinks they might be similar/same engine)
> Jill of the Jungle
That one honestly WOULD be a fun one to look at... Best I can find is Xargon [1] but part of me always got a vibe that Xargon was some semi-upgraded Jill engine...
> Duke Nukem
TBH Duke Nukem '1' would not be that exciting to me. AFAIR it's mostly an adapted CK1-3 engine, letter-boxed with status window to make it easier to calc the redraw.
Duke Nukem 2, is far more interesting since it's a different, more powerful engine (VGA, digital audio support, but AFAIR only required a 286).
[0] - https://news.ycombinator.com/item?id=28667945
[1] - https://github.com/dos-games/vanilla-xargon
IIRC (from being a kid) Harry was 256 color and DN2 wasn’t quite. Also it felt like it had much better frame rate. But I’m sure that could be engine evolution too. Interesting, I hadn’t ever thought of the connection before.
Though the “hot babes stuck in alien pods” from Harry showed up as a central plot point in DN3D.
I mean, I could be wrong as far as Harry and DN2 sharing an engine, OTOH Apogee did a -lot- of engine reuse (Bio-Menace used a CK4 variant, Monster Bash using an evolved FAST..)
Although, mea culpa, DN1 engine is not necessarily CK but the programmer has credited Carmack in helping with the drawing assembly...
Harry was written by an Australia, John Passfield, on his own and published by apogee (I forget but apogee might have provided some art support). John is still making games today!
I also think the story of Duke Nukem 3D (1996) and the development of the BUILD engine by Ken Silverman would also be a really interesting technical read.
[I Am Error: The Nintendo Family Computer / Entertainment System Platform | Books Gateway | MIT Press](https://direct.mit.edu/books/monograph/4054/I-Am-ErrorThe-Ni...)
Sorry for the "asking for more"-style comment, but it would be amazing if this came in epub and not just PDF.
Given its open source in latex format, it should be pretty easy to render it in any format that isn’t asking for significant decision-making on how to structure and format it.
Ie. Rendering to PDF or HTML would be pretty straightforward. Rendering to video, audio, or as a chocolate bar would require more authorship. Would epub be much more work?
I was almost tricked into thinking this was a new Fabien Sanglard book and got excited
Another game from the same era: https://cosmodoc.org/
this looks like a copy of fabien's site, plus the topic is very related and likely trampolining on his brand :/
I can understand the feeling of loyalty to a widely admired figure (and deservedly so!) but this isn't a great way to respond to someone else's work. Unless there's some evidence of ill intent, why not just classify it as an homage?
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
"Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith."
https://news.ycombinator.com/newsguidelines.html
totally, I wrongly assummed ill intent as I thought it was fabiens work for a good while and then came back here frustrated
Fabien's site is an invaluable resource, but I think I've read it all over the years and he one has post specifically on Commander Keen, and that's focused on just the adaptive tile refresh (https://fabiensanglard.net/ega/). This book is 211 pages on the entire game.
On the first page this author credits Fabian's excellent analysis of Doom and Wolfenstein as the inspiration to attempt the same for Commander Keen.
> "Fast forward to 2021, I discovered Fabien Sanglard’s website and began reading his Game Engine Black Books on Wolfenstein 3D and Doom. Inspired by those works, I wondered whether I could do something similar for Commander Keen: open up the source code, ex plore the files, and piece together a picture of the overall architecture and the clever tricks used. The style, dimensions, and structure of this book are intentionally similar to Fabien’s Game Engine Black Books, as an homage to those masterpieces."
Just skimming so far, but this book looks like a valuable contribution to the genre of retro game code analysis. Obviously, it will build on the work of others who've done adjacent research. In a page 87 footnote the author refers readers to Fabien's site for detailed instructions on installing a DOSBox and Borland C++ dev environment.
57 lines of CSS and the only distinguishing characteristic, the use of Deja Vu Sans Mono, isn't present.
This is trampolining on his "brand" as much as my text editor is
The book's source has verbatim copy and pasted TeX ripped from Fabien's books which was licensed under GPL.
They should address that, then. It's still not trampolining on a so-called brand, which as far as I can tell does not exist.
The author may well disagree.
https://news.ycombinator.com/item?id=48550425
Fair enough!
First, shallow dismissals are against HN guidelines, for a good reason.
And I fail to make the connection. This content-heavy but minimal design is not unique.
Text inside a centered element, text-heavy but also packed with images, exists from the times of formatinng websites with `<table>` tags in DreamWeaver or Microsoft Frontpage 98.
If you're talking about the highly detailed article, can we not gatekeep this? I want more of that on the internet, not less.
From the preface: > Fast forward to 2021, I discovered Fabien Sanglard’s website and began reading his Game Engine Black Books on Wolfenstein 3D and Doom. Inspired by those works, I wondered whether I could do something similar for Commander Keen: open up the source code, explore the files, and piece together a picture of the overall architecture and the clever tricks used. The style, dimensions, and structure of this book are intentionally similar to Fabien’s Game Engine Black Books, as an homage to those masterpieces. To give it a personal twist, I inverted the title and cover to white.
Yeesh, until I saw your comment I thought this was Fabien. I'm sure it's not intentional but this goes beyond "homage" and into "deceptive". The replies to this claiming to not see what the issue is are inexplicable to me.
The work on the book itself looks fantastic, so it's a shame about the site design.
It's often helpful not to immediately assume bad faith without further enquiry. It appears that Fabien had reviewed the book beforehand and he has reposted John Carmack's tweet[1] linking the book.
[1] https://x.com/ID_AA_Carmack/status/2066577536339923091
I thought "I'm sure it's not intentional" would make it clear that I'm not assuming bad faith - actually the opposite, I'm assuming good faith.
Understood. It's reasonable to call out potential conflict while also being unclear on intention. Something as simple in the Keen book author acknowledging the proofreader would put to rest the ambiguity central to the discussion point in contention.
Turns out it was intentional. https://news.ycombinator.com/item?id=48550425
Have LLMs made all arcana about games engineering meaningless?
Definitely not. If anything this arcana is what feeds the llms not the other way around.
Imagine if you replaced "games engineering" with "political history" or "nuclear physics"
Eh, it's not so clear cut. LLMs have definitely killed a lot of fun in reverse engineering old games by making it trivial to solve riddles that in the past would have been interesting problems to work on.
But the field still offers many mysteries that need human brains to be solved.
Whether LLMs are a net positive here depends if one is result-oriented (e.g. wants to rewrite an old game in a modern language) or process-oriented (is there for the investigation work and the intellectual challenges).
Were they really that interesting?