The Computer Graphics Library
fabiensanglard.net
The Computer Graphics Library
1–10 of 21 posts
Re: The Computer Graphics Library
#2For anyone curious in the field, there's a version of Michael Abrash's black book publicly available at github;
Re: The Computer Graphics Library
#3The link towards the "shadow mapping article" seems broken, it's this one: http://fabiensanglard.net/shadowmapping/index.php
Re: The Computer Graphics Library
#4ahaan, gotcha..
Re: The Computer Graphics Library
#5For anyone curious in the field, there's a version of Michael Abrash's black book publicly available at github; https://github.com/jagregory/abrash-black-book
although its labelled and oft quoted as such the black book is really an optimisation manual in disguise imo.
the content on graphics is virtually non-existent except for outdated information about old hardware interfaces from a time before DirectX, OpenGL and any particularly friendly rendering interfaces (so there was GDI and Win32 for early Windows, but we weren't yet in the time where programmers could spunk away resources and the hardware suck it up without destroying your performance).
there is some discussion on VSD techniques, the bresenham line algorithm etc. but these are also outdated - libraries today draw lines for us and even AAA games can ship without giving a serious crap about culling and hit framerate...
i do still highly recommend reading it, just don't expect to learn anything useful about graphics. my main takeaway from this book was 'optimise by measuring then experimenting and measuring to confirm the optimisation'. its so obvious but a large number of programmers i've worked with seem to prefer to guess and not measure...
Re: The Computer Graphics Library
#6For anyone curious in the field, there's a version of Michael Abrash's black book publicly available at github; https://github.com/jagregory/abrash-black-book
although its labelled and oft quoted as such the black book is really an optimisation manual in disguise imo. the content on graphics is virtually non-existent except for outdated information about old hardware interfaces from a time before DirectX, OpenGL and any particularly friendly rendering interfaces (so there was GDI and Win32 for early Windows, but we weren't yet in the time where programmers could spunk away…
I actually started reading the book slowly a few days ago, and am now in Chapter 17. So far there hasn't been anything about graphics; it's been mostly about low-level optimization and discussion of differences between 8086, 286, 386, and 486... yes, it's that outdated. There are some ideas that apply more generally (optimize your design and algorithms first, profile or measure, etc.). I don't think you need a book to learn these things, and I think they're close enough to common sense (for programmers) now anyway.
Having said that, I still find the book interesting, and I can't wait to get to the part where Mr. Abrash gets to talk about the software rendering in Quake (which he worked on). It might be outdated information for most of you, but I'm actually interested in seeing how far you could push software rendering with modern CPUs; it's sad that progress on that front pretty much ended around the time Unreal was released. If it was good enough for games back in the 90s, why wouldn't it be good for games in 2014?
If someone else here happens to be interested in 90s software rendering, make sure you read this bit about the Thief engine.. :-)
Re: The Computer Graphics Library
#7Nice list of books. I think I read Fundamentals of interactive Computer graphics (1st edition) around 1999 :).
Re: The Computer Graphics Library
#8Earlier quoted context omitted.
although its labelled and oft quoted as such the black book is really an optimisation manual in disguise imo. the content on graphics is virtually non-existent except for outdated information about old hardware interfaces from a time before DirectX, OpenGL and any particularly friendly rendering interfaces (so there was GDI and Win32 for early Windows, but we weren't yet in the time where programmers could spunk away…
I actually started reading the book slowly a few days ago, and am now in Chapter 17. So far there hasn't been anything about graphics; it's been mostly about low-level optimization and discussion of differences between 8086, 286, 386, and 486... yes, it's that outdated. There are some ideas that apply more generally (optimize your design and algorithms first, profile or measure, etc.). I don't think you need a book t…
Thanks for the link on Thief rendering. I remember playing the demo (or more like watching my brother playing the demo) and was scared to death so we never bought it.
All that sneaking around scared me to death. I now play racing games. During the daytime.
Re: The Computer Graphics Library
#9Earlier quoted context omitted.
although its labelled and oft quoted as such the black book is really an optimisation manual in disguise imo. the content on graphics is virtually non-existent except for outdated information about old hardware interfaces from a time before DirectX, OpenGL and any particularly friendly rendering interfaces (so there was GDI and Win32 for early Windows, but we weren't yet in the time where programmers could spunk away…
I actually started reading the book slowly a few days ago, and am now in Chapter 17. So far there hasn't been anything about graphics; it's been mostly about low-level optimization and discussion of differences between 8086, 286, 386, and 486... yes, it's that outdated. There are some ideas that apply more generally (optimize your design and algorithms first, profile or measure, etc.). I don't think you need a book t…
I started writing one and got discouraged when per-pixel Phong shading on the teapot ran at like 10 FPS. A profiler showed me that I was bottlenecked by simple unavoidable work like matrix multiplies in my shaders. Maybe that profiler was wrong though... now I want to hack on it some more.
Re: The Computer Graphics Library
#10For anyone curious in the field, there's a version of Michael Abrash's black book publicly available at github; https://github.com/jagregory/abrash-black-book
although its labelled and oft quoted as such the black book is really an optimisation manual in disguise imo. the content on graphics is virtually non-existent except for outdated information about old hardware interfaces from a time before DirectX, OpenGL and any particularly friendly rendering interfaces (so there was GDI and Win32 for early Windows, but we weren't yet in the time where programmers could spunk away…
You missed out on WinG.
As a side note it is quite hard to find anything WinG related nowadays, even as historical curiosity.