Bravo Nintendo. Bravo. iykyk
>see model in game files>proceed to completely make up non-sequiter conclusions you have zero context for because screeching about Pokemon is trendy
>>58408480you can't even explain why this is a bad thing. stfu retard. you just wanna complain to complain
>>58408498Larger textures require more processing power and take up more space, so it's best to optimize where you canBut to have an ENTIRE CITY be one model, means that the ENTIRE CITY has one single UV map! It's ONE texture!Meaning that BY DESIGN they *have* to re-use areas on the texture map CONSTANTLY, and everything is going to *have* to be low resolution, because they're trying to use ONE texture map for a WHOLE CITY
>>58408498you cant explain why its good, or bad, you are useless. Game runs like absolute anus, again, and looks like fucking garbage. Eat the slop you lil pig.
still runs better than scarlet/violet
>>58408521so 20 fps instead of 15?
>>58408521That's because ScarVi did the exact same thing on a larger scale. Meaning the ENTIRE world map in ScarVi is also one model
>>58408480I don't know all that much about 3D modelling and such, but aren't both counts relatively low for a whole map? And can't we still have culling involved even if the entire model is loaded (assuming it all is loaded; there's probably some way to only load portions of a model at once, right?)
>>58408513>Larger textures require more processing powerthere are no textures in the OP
>>58408545Three low poly count is another issue in itself. The reason why large scale rpgs like xenoblade or morrowind worked as they did is because the maps wetter broken up into individual blocks of models whose assets could be loaded as you entered a new block area. By making the entire map one single pie plate model, every asset is being rendered all at once
>>58408575Maps were*
>>58408531I've clipped through enough walls to know that's not true.
>>58408521The switch 2 is doing all the work
>>58408531>That's because [FANFIC]
>>58408480So you've extracted a single model via data mining, and you've drawn conclusions on how the game engine runs based on the model geometry alone?
>>58408480another brilliant lamefreak dumbjeet production
>>58408641It's not just the how it runs, it explains flat balconies and shit textures
>>58408641I've assisted in game dev before, which is how I'm familiar why this isn't a good practice for map design
>>58408480People couldn't figure this one out already? They did this in other games too.
>>58408692>I've [FANFIC]no one cares
>>58408696You cared enough to reply
>>58408480didn't Nintendo want to outsource this garbage?
>>58408692if you were actually in game dev you would know it's fucking retarded to draw conclusions from a single model file without having any details on the implementation of how the file is used.
>Supposedly one model making the textures and stuff look bad>Still looks way better than PLAOk. Like anon said, people are complaining for the sake of it
>>58408696stop seething, shitjeetyou'll survive
>>58408707If they were less shit at programming we'd have better games.
>>58408491This argument fails when you see every map, every scene every single thing has lillie multiple times. It would be easier and better performant to have it loaded as a singleton to drop as needed. What kaphotic says applies most of the time but when a model/character is this repeated like this the pattern used changes.
It's really funny reading you people redditpost about graphics on this. Octrees and BSP exist, you people know nothing.
>>58408913>It would be easier and better performant to have it loaded as a singleton to drop as neededno it wouldn’t
This discussion is useless when we have the zelda games, pokemon company is just lazy, and has bad administrators.
>>58409066Latest Zelda games' maps were outsourced to Monolith Soft, and those guys use fucking witchcraft in their games
