It was his royalties from Crash Bandicoot that enabled him to co-found/angel-invest in ITA Software, the flight search platform that Google acquired to be the foundation for Google Flights.
A little tangential/OT, but one of the things I admire about Andy Gavin and the Naughty Dog team is that they were capable of doing things on a brand new system that few ever figured out how to do.
Usually when a new system/console comes out it takes a while for developers to get used to its quirks and figure out optimizations and hacks to eke out whatever little performance gains you can under the constraints of the hardware.
One of the first games for the PS2 was Jak and Daxter: The Precursor Legacy, developed by Naughty Dog. What is remarkable is that Gavin had figured out that a lot of the assets and textures etc. that needed to be available in order to start the game could be loaded while the typical splash screens were displayed at the beginning.
I never noticed it when I played the game years ago, but I picked it up a while back and had a "wait, what?" moment when the PRESS START button appears, and instantly upon pressing it you're launched into the game and can interact with the world. No loading screen, no cutscene, just straight into the game.
Anyway, mad respect for a small team that managed to produce some of the most beloved games from that era.
I was taking to a woman at a party a couple of years ago (an event related to a choir composition that my wife had done), and at some point she mentioned her son was a developer, specifically that he made video games. When I asked if she knew which games he worked on, she said Crash Bandicoot and suddenly I felt like I was talking to Ned royalty. I gushed a bit about what I had read on this blog post, but kept the conversation going so as not to dwell on it.
Part 9 elaborates on GOOL, the Lisp dialect they designed in-house to create the gameplay.
One of the interesting points to me from reading this (or something similar about CB) the last time was this:
The PSX had no real 3D capability, you could just throw a list of triangles at it to draw. The problem here is that you have to sort the list of triangles yourself, since there is no such thing as a z-buffer.
For Crash Bandicoot, since the path is essentially linear, they were able to pre-sort most of the triangles at build time, which allowed them to achieve greater visual fidelity compared to contemporary titles that allowed for freer movement.
Oh man, this has been posted probably 100 times now but this is still a great blog.
I guess today another 10,000 people will learn about how crash bandicoot was made.
I was in video game development at the time and it was really exciting due to the switch from 2D to 3D for most games which made the math a programmer was required to know go way up in complexity.
And you hade new things called graphics cards that had their own apis to program to and drivers that didn't always do what they were supposed to do so you were always feeling around in the dark a bit when working with a new console or new graphics card. I remember so many bugs that weren't necessarily our fault, but the fault of buggy drivers or a misimplemened OpenGL call by the driver or console provider.
I couldn't imagine layering on top of that a lisp dialog to program your game in given that we were doing incredible things to shave off milliseconds. It seems counter intuitive to put a high level interpreted language ontop of that but these geniuses pulled it off!!
There was a great conversation with Matt Godbolt on CoRecursive recently [1]. It was a bit of a dive into how some of those abstractions are a lie and, particularly in early game dev, how you can create magic by realising that then exploit how the hardware actually works. Highly recommend a listen.
For those not aware:
One of the developers of Crash Bandicoot, Dave Baggett, is a longtime HN contributor: https://news.ycombinator.com/user?id=dmbaggett.
It was his royalties from Crash Bandicoot that enabled him to co-found/angel-invest in ITA Software, the flight search platform that Google acquired to be the foundation for Google Flights.
https://mixergy.com/interviews/david-baggett-ita-software-in...
A little tangential/OT, but one of the things I admire about Andy Gavin and the Naughty Dog team is that they were capable of doing things on a brand new system that few ever figured out how to do.
Usually when a new system/console comes out it takes a while for developers to get used to its quirks and figure out optimizations and hacks to eke out whatever little performance gains you can under the constraints of the hardware.
One of the first games for the PS2 was Jak and Daxter: The Precursor Legacy, developed by Naughty Dog. What is remarkable is that Gavin had figured out that a lot of the assets and textures etc. that needed to be available in order to start the game could be loaded while the typical splash screens were displayed at the beginning.
I never noticed it when I played the game years ago, but I picked it up a while back and had a "wait, what?" moment when the PRESS START button appears, and instantly upon pressing it you're launched into the game and can interact with the world. No loading screen, no cutscene, just straight into the game.
Anyway, mad respect for a small team that managed to produce some of the most beloved games from that era.
I was taking to a woman at a party a couple of years ago (an event related to a choir composition that my wife had done), and at some point she mentioned her son was a developer, specifically that he made video games. When I asked if she knew which games he worked on, she said Crash Bandicoot and suddenly I felt like I was talking to Ned royalty. I gushed a bit about what I had read on this blog post, but kept the conversation going so as not to dwell on it.
Part 9 elaborates on GOOL, the Lisp dialect they designed in-house to create the gameplay.
This is my favorite part: https://all-things-andy-gavin.com/2011/03/12/making-crash-ba...
One of the interesting points to me from reading this (or something similar about CB) the last time was this:
The PSX had no real 3D capability, you could just throw a list of triangles at it to draw. The problem here is that you have to sort the list of triangles yourself, since there is no such thing as a z-buffer.
For Crash Bandicoot, since the path is essentially linear, they were able to pre-sort most of the triangles at build time, which allowed them to achieve greater visual fidelity compared to contemporary titles that allowed for freer movement.
Oh man, this has been posted probably 100 times now but this is still a great blog.
I guess today another 10,000 people will learn about how crash bandicoot was made.
https://xkcd.com/1053/
I was in video game development at the time and it was really exciting due to the switch from 2D to 3D for most games which made the math a programmer was required to know go way up in complexity.
And you hade new things called graphics cards that had their own apis to program to and drivers that didn't always do what they were supposed to do so you were always feeling around in the dark a bit when working with a new console or new graphics card. I remember so many bugs that weren't necessarily our fault, but the fault of buggy drivers or a misimplemened OpenGL call by the driver or console provider.
I couldn't imagine layering on top of that a lisp dialog to program your game in given that we were doing incredible things to shave off milliseconds. It seems counter intuitive to put a high level interpreted language ontop of that but these geniuses pulled it off!!
There was a great conversation with Matt Godbolt on CoRecursive recently [1]. It was a bit of a dive into how some of those abstractions are a lie and, particularly in early game dev, how you can create magic by realising that then exploit how the hardware actually works. Highly recommend a listen.
[1]: https://corecursive.com/godbolt-rule-matt-godbolt/
Crash Bandicoot, loved that game! Especially the levels where you had to run backwards, those were amazing fun
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]