4 ms·
I would have assumed that video game engines would have solved the problem of loading assets dynamically / on demand already, I guess not. It reminds me of Cybe
by Cthulhu_ 4y ago
I would have assumed that video game engines would have solved the problem of loading assets dynamically / on demand already, I guess not. It reminds me of Cyberpunk's bad PS4 / xbone release and issues, where a famous clip on the internet shows assets not having loaded yet during a cutscene; again, I would've thought loading assets was a solved problem.
- hotpotamus 4y agoThere's a talk by one of the developers of Crash Bandicoot of all the hacky (and brilliant) things they had to do to get the game to load quickly off the (2X?) CD-ROM into the very limited RAM of the Playstation 1. https://www.youtube.com/watch?v=izxXGuVL21o https://www.youtube.com/watch?v=izxXGuVL21o
- dj_mc_merlin 4y agoLoading assets in a simple, naive way is indeed solved. If you want "next-gen graphics", you need to push against the limit of your system, much as always. That is always tricky, new techniques are being developed every day, game studios have departments dedicated to finding new and better ways to stream data to-and-fro as needed.
- WorldMaker 4y agoIn large part, while a "solved problem" in aggregate, every engine has different solutions in play. In part, because of trade-offs baked into engine assumptions. It's certainly possible no two engines will ever agree on asset loading due to such tradeoffs and how engines themselves are built/optimized. In part, because there's still not much coordination between different game companies and few shared libraries/middleware/"content/asset pipelines". Think about how many bundlers there are in JS today that we know of because of open source (and HN headlines about them) and multiply that by how proprietary most game companies still see every bit of their code in 2022 and generally avoid HN headlines about low level details of their tech stacks (for "competitive advantage").