Fabien Sanglard

probably worth linking to it, if that's the case. i think you are referring to this one? https://fabiensanglard.net/

I love reading technical blogs, and Fabien Sanglard’s are some of the best out there https://fabiensanglard.net/ also the simple design of the website makes it great

Oh yeah. But the distracting fluff usually can't cover for the lack of good content. My personal favorite: https://fabiensanglard.net. Love how minimal and distraction free the site is. You immediately know what he writes about and the front page doesn't ask you to click around a gazillion links to find out content.

Fabian Sanglard’s books are excellent! I highly recommend them for retro DOS game engine programming. https://fabiensanglard.net/

>we do well to remember what actually happened rather than just lionizing one man This statement alone was worth the price of admission. As a fan of game engine history (highly recommend Fabian's books: https://fabiensanglard.net/), I have to remember that all of these things were built on the shoulders of giants. It wasn't just one person that contributed, even if it may be only their code that lives on.

Fabien Sanglard's blog is one of my favorites. He posts mostly about internals and implementation details of classic video/computer games, plus other tech like Git and USB. https://fabiensanglard.net And if you find his blog to your liking, he has a couple of books doing a deeper dive into the internals of Wolfenstein 3D and Doom.

https://fabiensanglard.net/ does some great code reviews of old games

The biggest thing is lower resolution. 640x480 at 256 colors was a high-color, high-resolution mode at the time. Small bitmaps, with indexed palettes and run-length-encoding to further shrink them. Caches were tiny, memory was slower, hard disks massively slower, and if you had to hit a CD to load data, forget about it. So packing data was important, and organizing data for cache locality, and writing algorithms to take advantage of instruction pipelining and avoid branches. Fabian Sanglard has a great blog that goes into the nitty gritty of a lot of these techniques as used in different games. https://fabiensanglard.net/

I highly recommend looking through the flipcode archives here https://flipcode.com/archives/ to see some techniques from back in the day. I also recommend anything by Fabien Sanglard here https://fabiensanglard.net/

Fabian Sanglard (who is perhaps best known for his writing on wolfenstein/doom/quake and associated black books) also has a series of articles on another world, its bytecode interpreter and various ports to other hardware: https://fabiensanglard.net/

Fabien https://fabiensanglard.net/ is a must on this list, IMO. I really enjoy his code reviews. I can also recommend the books he have made so far on Wolfenstien 3D and Doom.

Michael Abrash is an excellent chronicler of technical history. Reading through his contributions is always time well spent. See also https://fabiensanglard.net/ for a more contemporary take. His 'Black Books' on Wolfenstein and Doom are directly inspired by Abrash.

https://fabiensanglard.net/ it is tech, but it is fantastic tech, tons of amiga stuff that takes me back to earlier, simpler time. I'd recommend a browse through the titles, at least. I'd be shocked if this crowd didn't love it.

Yes! the blog is full of more articles just like this, i love this stuff. http://fabiensanglard.net/

If you're looking for a high-level overview of some of id's source code releases, check out Fabien Sanglard's guides[0]. He's also written a book that goes into greater detail about the Wolf 3D engine. [0]: http://fabiensanglard.net

Fabien Sanglard wrote great reviews of various codebases, including git, Doom 3 and others. http://fabiensanglard.net/

Some excellent ones here: http://fabiensanglard.net/ Mostly video game related.

This is one of the reasons I love the Id github (https://github.com/id-Software), and even more so, Fabien Sanglard's reviews of the code in that code base http://fabiensanglard.net/

Fabien Sanglard http://fabiensanglard.net has some excellent code reviews on his website, particularly games. You could read some of the code-bases he reviews, and then read his review. You'll be able to compare and contrast your opinions with his, and if there's interesting variation you can blog about it ;)

Take a look at Racing the Beam by Nick Montfort and Ian Bogost, which tells the story of the Atari VCS (2600). While not a book, and quite a bit more technical, there's also Fabien Sanglard's website (http://fabiensanglard.net/). It contains great technical analyses of the code of historically important games.

You'd be committing the classic fallacy of "i'll just work on these tools, then make the game", which while a fun exercise, almost never results in a game being released. Think about what your ultimate goal is: - you want to make games: use an existing engine. don't bother with half of the features, focus on whether the game is fun or not. add polish (like character animation transitions) later. use stock assets to begin with. - you want knowledge to work in games industry but not actually release a game yourself: learn all the bells and whistles of Unreal Engine - you want to make things that are unlike regular games: develop your own code - you don't ever intend to release a game, you just want to see how they're made: just read other people's code. Read the Quake engine source code and https://fabiensanglard.net/ as a companion site. If you're talking about using raylib, that is also a game engine, just a simpler one. We can look in both directions; if this is an exercise exclusively for personal learning and development, why not also learn about what's done for you by that library and by the GPU, etc? Occlusion, rasterisation, depth buffering, perspective-correct texture mapping... "the number one most important skill is how to keep a tangle of features from collapsing under the weight of its own complexity" https://prog21.dadgum.com/177.html this is what game engines do - they abstract the essential complexity present in all games, and keep it from infecting the…

This is awesome! Great work! I love playing around with these older game engines that have source available, its really neat to explore how they work, and fiddle around with it. If you haven’t already, Fabien’s write ups of the various ID engines are a joy to read: https://fabiensanglard.net/quake3/index.php Shameless plug: I also like to play around with old game engines: https://github.com/bishopdynamics/Continuum

Copetti enjoyers should also checkout everything Fabien Sanglard has done, including the Wolfenstein and Doom Black Books, the Another World port analyses, and the other dozens of code reviews he's posted. https://fabiensanglard.net/

I hope this means that Fabien is working on another Game Engine Black Book. I really love these deep dives and historical preservation of 1990's game tech. https://fabiensanglard.net/gebbwolf3d/ https://fabiensanglard.net/gebbdoom/

Thanks! Amazing website, so many useful articles. Wish I had a couple of free years to work through these books https://fabiensanglard.net/Computer_Graphics_Principles_and_Practices/…

Tangent: Author has this fabulous post I'd highly recommend: https://fabiensanglard.net/mjolnir/index.html I read it once years ago and I come back to it every now and then wishing my current PC (10+ years and going) would gently die so I could finally build something small and tiny.

I had a Cyrix 6x86 when Quake first came out. My disappointment at how poorly Quake ran on it was significant, especially because pretty much every other game at the time ran well on the Cyrix. The FPU performance in Quake was doubly handicapped on the Cyrix: not only was its FPU slower than the Pentium's to begin with, Quake's code was indeed hand-optimized for the Pentium's FPU pipeline. Fabien Sanglard's writeup of Michael Abrash's optimizations for Quake goes into great detail: https://fabiensanglard.net/quake_asm_optimizations/

Super cool stuff! I love the idea of games being refurbished to the point that it can be kept, almost source original, and still played years down the line. For example, I love Another World for this, being just a bytecode blob where each port is just a VM (good writeup: https://fabiensanglard.net/another_world_polygons/index.html).

https://technology.riotgames.com/ https://fabiensanglard.net/

Rebecca was well known in emulation circles for her high quality work on various games of the era, often pushing the hardware in unusual ways. This article is one of my favorites, detailing the wacky tricks she used to get Another World's 3D rendering system running acceptably on a Super Nintendo https://fabiensanglard.net/another_world_polygons_SNES/ Rest in piece, you absolute legend.