Just how the f*CK did Nintendo developed tears of the kingdom?
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, ...?
You are viewing a single comment
Console games developed at the end of the console lifecycle often includes various optimizations learned by the dev community to squeeze as much performance as possible. Just look at how good gtav and mgsv on ps3 for example.
MGS V's performance is a freaking work of art. It ran incredibly smoothly on my PC, and was gorgeous to boot. Then I loaded a few other games and had to turn down settings to hit 60fps.
Can confirm, I still remember how impressed I was to see MGS:V running smoothly on my old dual-core Intel CPU with integrated graphics. It could never handle Sleeping Dogs or Deus Ex: Human Revolution yet this massive and beautiful open-world sandbox ran on it like a champ.
fox engine was well developed and iirc was used for PES, sad it didnt get much other uses though due i konami functionality pulling out of game development.
Well, Konami is back into game development, but the Fox Engine remains on mothballs. MGS3 remake will be on UE5 :/