There are so many things being tracked all the time in the game for puzzles and the power arm. Yet despites literally tracking sunshadows for some puzzle completion for example it runs almost smoothly with (in my 170h) no crashes. On a 6 yo portable console??
Botw was already impressive but I could grasp it with the shaders and also there weren’t that much physics puzzle. Objects were more static, there wasn’t the two other maps, enemy diversity was limited, same for weapons. There was less of everything overall but I thought it was the limit of the console and the possible engineering around it.
Is there any resources on how they managed to pull this off? White papers, behind the scenes, charts, …?
When I was extracting sounds from the sound banks from the Nintendo 64 game F-Zero X I simply couldn’t find certain sound effects. It turns out that some effects are created during runtime by taking a sound sample and applying certain effects or filters, for instance pitch shifting the sample and looping it in rapid succession.
It’s a clever way to save on memory and the player doesn’t notice if it’s well done. The original Pokémon Red/Blue on the gameboy is an example where it’s not so well done in some places. If you pay attention you’ll notice that some Pokémon’s battle cries are simple pitch shifts of other ones and they didn’t apply any other effects to obfuscate this.
Shout out to Retro Video Game Mechanics Explained for his explanation of the entire construction of the cries.
I mean, pokemon needed 151 different battle cries. There is bound to be some overlap.
Pokemon is very optimised. In order to have the feature to give your pokemon nicknames, they had to scrap the other 105 pokemon just so they had enough space to write the code.
Need is such a strong word
I don’t think they needed a single one.
The game would be equally popular with, and without the screeches.