Wyrdness said:
Yes the will never be hardware that can overcome this issue because full permanence on this scale would mean that data keeps building up as the player goes through the game what that means is the only true fix to this is infinite memory which can never be achieved by any hardware . This is why all games like this have measures in place to reset, limit or restrict permanence as it's a games way of clearing and reserving memory. |
You're vastly overestimating the amount of data necessary to store the buildups. The information needed to load the buildups is not huge it's actually very tinny
the RAM necessary to concretely load the assets in the enginee in other hand is big, but the workload to load them js just as big as of any construct made by the dev team. The key here is how costly the assets are for the engine to handle. A game like Zelda has assets with little detail and graphical fidelity, so there is a finite number of items necessary to fill whatever is the space the engine loads in your face, i.e. Give PS5 RAM to Switch and it will load everything you put o the game without much trouble
Of course players could overload the map with designs and turn the game an unplayable mess, kinda like an infinite Kakariko Village, but that's players decision. For instance I have filled my Animal Crossing island with so much furniture that it failed to load the assets seamlessly eventually. This is fixed with enough RAM.
So while theoretically it's an unsovable problem, in practice it's not. Indeed I truly believe that even on the tinny Switch TOTK could actually save the constructs you made and leave them as they are. But they avoided because iit because first it mess deeply with saving files structure and probably needed to rework all the code related to how the assets are loaded and handled, I could only imagine the nightmare of reworking the core engine all over again for such small feature
Could also understand the a nightmare to test the consequences of this on map and game design, urgh
