6 ms·
The games industry is so stinking bad at archival that it hurts. Very little consideration is paid to using architectures and build tools that can be replicated
by danShumway 8y ago
The games industry is so stinking bad at archival that it hurts. Very little consideration is paid to using architectures and build tools that can be replicated later. Source code becomes unavailable (as was the case here). Game logic is written using highly platform-specific code that's difficult to emulate. Source textures and other raw resources get thrown out.
And not to diminish from the accomplishment of the team here, because it must have been a huge amount of work, but even with that amount of work this recreation ended up having problems with collision detection that changed the entire feel of the game. I don't think that's because the devs are bad, but just because the task they were trying to undertake was so unbelievably impossible -- of course they missed stuff.
If you're in the games industry, please put some effort into preserving your work for history. It does actually matter.
- GatoVolador 8y agoPaid, not payed.
- JasonFruit 8y agoArchival is an adjective. I will die on this hill.
- user3359 8y agoIIRC from developer stories from this era, things had to be done "creatively" to save space, and ensure optimal runtime execution. Certain platforms may well have had undocumented bugs and platform-specific optimizations that you simply had to adapt to. Archiving wasn't a consideration - launching a playable game that would pay the salaries and lead to future projects was. We take for granted that websites but in 95 are still more or less viewable in their original format today, but that's because things are designed that way. Gaming platforms were more or less abandoned entirely and rewritten - I might be wrong here but games from PlayStation 1 are not playable on PlayStation 4 are they?
- danShumway 8y agoYes and no. I don't really have a justification for saying this because I was never working in that environment, but I don't think the industry spent enough time thinking about how their games would be played in the future and I suspect that a lot of the "well, the platforms required us to do this" is an excuse. Yes, there are platform-specific quirks and bugs and stuff to work around, but say you're taking advantage of a console specific hack -- well, is that hack encapsulated? Is that hack mentioned anywhere in your internal documentation? Do you have internal documentation? I think you're mostly right that the thought was, "why would we care about building a game that runs on PS2, we'll just make a new game for that console." You can do a lot with even really bad source code if the other stuff is good -- if you still have uncompressed assets, or your build process isn't completely reliant on some weird third-party proprietary dev kit. Bear in mind that with this project, they didn't even have access to the source code, and they had to manually decode 3D mesh data. So platform-specific logic was the least of their problems. I suspect that part of that is that the games industry is just really young. And maybe some people were yelling about archival back then, but there weren't any real tangible consequences. Now that remasters are a big thing, you've got situations like this, where companies want to leverage old IPs and are suddenly realizing that doing that is twice as complicated as it should be.
- wild_preference 8y agoIt just sounds like you underestimate the difficulty of building games and, especially, overestimate the certainly that they will be successful. It’s easy to preach how software should be written in the hindsight of a successful project that you had zero stake in. I doubt the developers of games that flop (so, most of them) wish they’d spent more time and money ensuring their unwanted flop of a game was easier to archive.
- danShumway 8y agoArchitecture is the last step in this process. The low hanging fruit is "do you still have your source code and original assets? Is any of it documented?" Nobody will ever know if the original code for Crash Bandicoot was written well or not, because in all likelyhood nobody has it anymore. And I don't think you can chock that up to, "well, developing games is hard." We can debate whether or not it's possible to release a game with readable source code, but if that was the only problem the games industry had with archival, I wouldn't honestly have much to complain about. The sort of second problem I have with this is the idea that flops aren't worth archiving. I want flopped games to be archivable. If you're a studio and you're saying, "we don't have time to worry about this", fine, that's your choice. What I'm advocating is that preserving history is important, not just for Mario, but also for games like ET. I want people in the future to be able to play your failed games. Of course caring about archival makes developing games harder, just like caring about accessibility does, and just like caring about framerate does, and just like caring about localization does. These are all different concerns that we try to balance, and widely the games industry has decided that archival is not a concern that it cares about balancing.
- agumonkey 8y agoIt's a fair point. See emulated snes games that fail on some vfx because code relied on ultra specific hardware architecture.
- techopoly 8y agoCorrect, PS1 games are not playable on PS4.
- reificator 8y ago> even with that amount of work this recreation ended up having problems with collision detection that changed the entire feel of the game. You know, I did 100% minus (non-required) relics on all three games, and I didn't really feel like it was any different. Sure I didn't compare them side-by-side, and sure I did explicitly ignore the speedrunning part of the games where minor differences would be easier to notice. But it felt like the same games to me...
- danShumway 8y agohttps://www.eurogamer.net/articles/2017-07-04-fans-may-know-why-jumping-is-harder-in-the-crash-bandicoot-n-sane-trilogy https://www.eurogamer.net/articles/2017-07-04-fans-may-know-... I'm curious if they ever patched this. It's certainly subtle enough that it got past their testing, so I'll give you that "changed the entire feel of the game" is probably an over-exaggeration.
- monocasa 8y agoCrash Bandicoot was written mainly in GOOL, a custom to Naughty Dog lisp variant. The game would have had to be rewritten anyway almost certainly.
- danShumway 8y agoI would think the lesson from this is, "don't build an in-house custom Lisp variant for all of your games unless you're willing to distribute the documentation, compiler, and dev tools with your source code."
- monocasa 8y agoIf it's intrinsically doing any code modification (which as I understand it does in order to dynamically load and link code), even with all of that they might be up shit creek. Some of these platforms don't allow anyone, even the kernel, to make pages executable without providing signatures.
- TeMPOraL 8y agoWell, if your platform can't support implementation of typical Lisp/dynamic idioms, then it's frankly a shit platform and doesn't deserve to be called "general-purpose computer".
- vertex-four 8y agoRather unsurprisingly, game consoles are not intended to be general purpose computers.
- zeta0134 8y agoI'm not convinced it'd be impossible to use the GOOL code though. It should in theory have been plausible to port a GOOL interpreter, and then simply use the original code in the new interpreter. That said, there are some possible complications with the approach, depending on how tightly integrated the old GOOL system was with the rest of Naughty Dog's very custom engine. Of course they'd need to actually have the GOOL code to start with. It sounds like all they got from the original games was the original meshes and some other non-code assets, which ... I mean, that's some incredible reverse engineering work. I'm much, much more forgiving of the tiny little inconsistencies here and there given that context; the team did a fantastic job if they were primarily going off reference footage.
- jmkni 8y agoFun fact, when Metal Gear Solid (1) was ported to PC, the work was done by a handful of people, and they didn't have access to the original resources so they found some of them on fan websites. Some of the audio files used in the release are 30 second loops of much longer pieces of music from the original game.
- monocasa 8y agoHuh, that's weird. PS1 assets were remarkably transparent. Generally the audio was just CD-A tracks or ADPCM files, and the rest of the data was a ISO-9660 filesystem that showed up when you stuck the disc in a computer.
- jmkni 8y agoThey mentioned it in the commentary on an MGS1 speedrun video on Youtube. They use the PC version because it contains features (such as first person mode) which fundamentally break the game, as well as other bugs. I'll try and find it.
- jlg23 8y agoLet me hand you some binoculars, it might be hard to see the details from the vantage point of giants' shoulders: * A lot of things "missed" is what further research proved to be "obvious" conclusions of exactly the groundwork laid by these games. * Between 80h/week, personal life and the permanent question whether your game will sell at all, considerations what you should do in case your game becomes a cultural heritage are moot. I have been part of this circus 15 years ago and while I definitely am proud of what I did, I do not think any lessons I learned are directly relevant today. Not only that, but I can not imagine to revisit my old code for any amount of money. Yes, my build system increased build speed by a factor of 200 over industry standards, but no, I am not going through those 2.5k loc gnu-make ever again. Or to even document the tricks we used to deliver a 80k jar, including assets. A lot of the stuff was done to deal with hardware limitations that are irrelevant today. Why go through a lot of pain when the resources today are sufficient to play 100 instances of an unoptimized rewrite in an emulator?
- danShumway 8y agoSo I'll say up front, you're right to say I don't have 15 years of experience to back this up. And if your takeaway is, "this idiot doesn't know what they're talking about", fine, I'll take that. That's a completely reasonable reaction. But, you're wrong. The top rated post on Hackernews right now is a bunch of people gushing about how cool it is to see the source code for the Apple II LOGO language[0]. Your code has value beyond whether or not someone is going to pick up a new game-dev trick for their next title. It's a window into how games used to be built. It is a tiny composite piece of gaming history, and history is not just about how Mario was built, it's also about how small games were built, and what trends across the entire industry looked like. Your code has value beyond just publicly releasing the source. Maybe you would never revisit it in a million years for a million dollars, but the overall gaming industry is interested in remakes and remasters right now, and if you've ever worked for a publisher or sold the IP rights to one of your titles, it is not out of the question that the publisher might want to do a remake without you. That's the entire premise of this article, and if you have the source code, even if it's not portable, even if it's using hardware-specific hacks, even if it's written in an obscure language, your publisher will be in a better position than if you didn't. To be kind of blunt, this attitude is exactly what I was getting at above. Game devs don't understand why they should even care about history. If your takeaway is, "I don't care about old games unless they make my new PS4 game run faster" you have missed the point. If your takeaway is, "archival only matters if my game is successful, and I don't know if it'll be successful yet", you have missed the point. I completely, 100% understand that game dev is stressful. Zoom out a bit from that; working in the games industry in general is kind of hellish right now. If you're putting 80 hours a week into building a game for (on average) less pay than you'd get as a general software dev, and you're not doing it because you genuinely care about what you're making... that's a stupid career choice. And if you do genuinely care about what you're making, then try to make sure it lives longer than you do. Bear in mind, what I'm asking for doesn't have to take much work. You don't have to go crazy building out your source-code in a special way if you don't have time. Change nothing at all about your dev process -- just take 3 minutes when your game ships, stick your raw source code, assets, and a DRM free binary on a flash drive, and then mail it to Jason Scott. That's it. Just by doing that, you're now ahead of most other companies in the games industry right now. [0]: https://news.ycombinator.com/item?id=18142287 https://news.ycombinator.com/item?id=18142287
- tiredwired 8y agoThe lack of archiving is due to the frequent layoffs at the end of projects at game companies.
- faitswulff 8y agoFirst paragraph of the top comment on Ars: > I worked at Insomniac on Spyro while Naughty Dog was working on the Crash series. We had a friendly competition squeezing out the maximum possible performance from the PlayStation, and that turned into an even friendlier coopetition on our respective PS2 engines when we actually started sharing some code. Based on what I saw of both code bases, Naughty Dog did them a huge favor by sharing so little. It would have been more work to rehab than recreate. Highly recommend reading the rest of the comment, too!
- Rebelgecko 8y agoAssuming it wasn't a typo, I really like the term "coopetition"
- toyg 8y agoIt is a problem that game development shares with other forms of mass-marketed art: film industry, tv, music... they are all pretty bad at conservation, and were downright atrocious until very recently (I’m sure you heard how the BBC lost the first few seasons of Dr Who — and they are an excellence for conservation in the field). Simply put, the emphasis in creative industries is to continuously create (eh) new stuff, not revisiting the old. Couple that with inevitable financial pressures, add the cultural distortion of software development culture at large (where everything changes every year or so, and if you are not on the latest and greatest you are dead in the water) and you have a situation where conservation is the very last priority.
- CJefferson 8y agoThe systems we run on make it very hard. With emulation, the best way to run an old game is a final binary. I wrote an iOS 3 game. I have a lovely git repository of code. Is fairly useless as apple won't give me either the OS or compiler I need to run the code.