>>39039035>>39039113>>39039998>>39040573Guess I'll explain this shit for the umpteenth time.
There aren't "Hundreds of Lillies" and there aren't "4 Different Models per Pokemon"
That's based on a poor understanding of how object oriented programming works.
The hundreds of Lillies the anon saw are likely hundreds of Lillie PREFABS. They all use the SAME model (well, 2 model since some will use Lillie and others Lillie Z-Form). Prefabs take up barely any space at all because they're just a bunch of data saying "load these assets together with these scripts/variables applied". Those variables are different in each scene so there's a copy of the Lillie Prefab with different placement, dialogue and animation variables in each scene she shows up in throughout the game, along with a variable telling her when she should stay in the scene or just delete herself immediately based on story progression at that point.
Pokemon are the same. Each pokemon is a unique instance pulling from the same prefab of the generic Pokemon but with different variables for stats and moves. When they dynamax, they just scale up the already loaded model and load in "storm.prefab" under the Pokemon's object hierarchy (makes it easier to reference later on) and places it above the Pokemon. Also applies some kind of dynamax shader to the models for the red glow.
The clip of Steelix "loading a new model" wasn't that at all. It was a camera culling bug where the camera turned off all rendering in Steelix' heirarchy because it would have been in the way of the shot, then forgot to turn it back on till the camera finished moving. It's a script bug, not an optimization thing.
I really need to boil this down to a simpler explanation.
