Why could these games run without lag while 3ds cant

Reused N-64 models. Trainer animations and polygons are atrocious.

>>29476930
My 3DS never lag.

>>29476930
Most of the Gen1/2 models were ripped from Pokémon Stadium?

File: 1476658987987.jpg (119KB, 471x490px) Image search: [Google]

119KB, 471x490px

>>29476930
>2000 + 16
>Gamecube runs better and has somewhat decent models
>meanwhile N3DS/3DS runs like shit during 2v2 or 3v3 battles, can't use 3D for most places and everything is either pixelated and hindered by the shitty hardware
LOL

>>29477163
They're planning for the future; the models are too much for the 3DS to handle but they can be directly reused for the Switch and look better.
If they do it right, they'll never have to remodel a pokemon again

File: 9318.png (231KB, 750x650px) Image search: [Google]

231KB, 750x650px

Low quality models, animations, and special effects, even at the time. Most, if not all, the Pokemon models for the first 251 were directly ported from Stadium 1 and 2. Since X/Y, Game Freak has been using the same models, maybe with a few touch ups here and there, to save them the effort of redoing all 800+ Pokemon every generation. These models are high quality, intended to last them a long while, but the 3DS resolution isn't great so they look a lot shoddier than they actually are, and the 3DS's rendering is subpar enough to cause slowdowns when there are multiple of these models on screen. It's really more the 3DS's fault if for being underpowered than Game Freak's laziness. The best solution for performance would be to make models with less polygons for scenes with more than 2 Pokemon, to keep the framerate steady.

File: slurpuff_sez.png (57KB, 250x250px) Image search: [Google]

57KB, 250x250px

>>29477163
Creatures didn't want to go through the trouble of rendering 600+ Pokemon models for a next gen handheld or console but GameFreak didn't want to go through the trouble of scaling down the poly count to work optimally on 3DS.

>>29477163
>fucking Pokemon GO runs better on my shitty phone using the same models

>>29476930
Because Gamefreak didn't make that.

>>29477380
The graphics chip in the 3DS is nearly 10 years old, your phone isn't that old if it can run Go.

>>29477380
1. Your phone is recent if it can run Pokemon Go, while 3DS uses a 10 years old graphics chip
2. Your phone's battery life diminishes much faster than a 3DS while Go's running, even if you turn off the AR, and it's minimalistic as hell with rendering and animating stuff compared to a main series game. Only three backgrounds between catching and battling, and two of them are day/night variants of the same thing.
No shit a more recent piece of hardware has higher performance playing something as watered-down in the animations and special as Go than something that can actually qualify as a game. Same goes for Pokedex 3D Pro. Of course the Pokemon look better when there's nothing else going on.

>>29477467
>>29477800
So what you guys are saying is that mobile games are obviously better than games on my 3ds?

>>29477883
We mean that if you manage to run X on your phone, it'll work better for 1/1.5 hour/s before eating your battery. If it doesn't burst in flames.

File: 0.jpg (20KB, 640x360px) Image search: [Google]

20KB, 640x360px

>>29477208
>We'll be stuck with the shitty Salamence model for ages

File: allsmiles.jpg (7KB, 210x250px) Image search: [Google]

7KB, 210x250px

>>29478008
Best case scenario is they update and refine some of the shittier models like Salamence and Archeops.

>>29478094
It's not even the models that are bad for flying-types, it's just their animations.

File: eevee.gif (178KB, 340x336px) Image search: [Google]

178KB, 340x336px

>>29476930
Bring HAL back to do the models. They gave each pokemon WAY more personality than the boring static shit we're given now.

Speaking of which, what was up with Eevee's puff-ball hair?

>>29477314
>Game Freak makes ridiculous 7-10k poly models, doesn't optimize whatsoever and instead chooses to disable game features to shove more models into battles which kill the framerate further and more consistently
>3DS chugs because it's clearly being pushed over its limit with unoptimized code and models with massive polygon counts
>this is the 3DS's fault

Naw son, Game Freak both can't code for shit and don't care if the game suffers when they cut some corners. Smash 3DS ran at a stable 60 with 3D on no matter how hard you pushed it, this is Game Freak fucking up.

Though to be honest, I really can't wait to see the insane the polygon counts will be on the ultra beasts and how low the framerate gets when you put them together into a triple battle.

>>29478535
There's actually no triple battles now. That said, Smash did some crazy things to run well. Higher quality models are only used when pausing the game, 30 FPS assist trophies and whatnot.

>>29478535
I still don't get why they don't reduce the polygon count for the ingame models instead of using those 10k ones.
I don't know about these things, but is it possible to ''cut'' some polygons without starting from scratch?

>>29478686
No triples anywhere? I don't remember that being said. If that is true, it's just more gameplay features being stripped because of an unoptimized game.

And if Bamco could afford to do it, Game Freak could afford to do it. ORAS sold almost 5 million more copies than Smash 3DS, so some optimization clearly won't break the budget. Game Freak just doesn't want to spend the effort to optimize or can't because all their coders are trash.

Because the GCN is more powerful than the 3DS for everything besides dem light shaders

File: mewtwo models.png (342KB, 927x819px) Image search: [Google]

342KB, 927x819px

Because it had literally N64 graphics. Some models got some textures changes here and there, but with the same geometry of Pokémon Stadium.

Here's a quick comparison of some models. Mewtwo.

>>29478474
Although I do agree some old models looked more stylish, thanks to the more realistic textures and lighting, their animations are pretty much the same, no?

>>29479583
I feel like I may be cherry-picking the few that went crazy. Like Stadium's Eevee went buck-wild when it rushed the opponent, getting into a ball and rolling into them at full speed. Kangaskhan, Golbat, and Jynx are also way more animated.

>>29479583
>>29479712
Also Blastoise's shell opens up and releases the cannons when it uses Hydro Pump.

the one thing i wish would return from the consoles games is that pokemon were to SCALE. that adds so much to my immersion

>>29478535

As far as we can tell from online rules and code from the demo, triple battles and rotation battles have been scrapped.

The models in the 3DS games are a lot better, and the 3DS is weaker than the Gamecube.

>>29479583
Stadium animations definitely had more character for the most part. XY models are much more static, lack decent 'hit by an attack' animations, and faint animations cut before you can get a good look at them.

Part of this could be because the camera work in Stadium games was better, physical attacks would cut to make it look like punches were actually connecting, whereas in XY Pokemon just punch the air.

>>29477163
>A folded xbox hueg runs better than a tiny ass device that needs to render two screens at the same time trying to pull off more detailed graphics (yes, the resolution of the screen is terrible, but models and texture themselves tend to be bigger anyway, just look at what the fuck devs would do with the DS for extreme examples)


woooooo color me surprised

Because its a fucking handheld.
Is /vp/ this stupid?

>>29479625
damn

File: 1477126642797.jpg (85KB, 824x579px) Image search: [Google]

85KB, 824x579px

>you'll never have 3DS models with Stadium animations and effects

>>29478008
>A dragon themed around flying flies
wtf Game Freak

File: 1456969817603.jpg (53KB, 500x519px) Image search: [Google]

53KB, 500x519px

>he doesn't raise the clockspeed of the games on his n3DS
>he doesn't make use of the available L2 cache

>>29476995
This. Colosseum is my favorite game in the franchise but a lot of the Kanto and Johto pokemon look like utter shit.

>>29476995
not as atrocious as 3ds models are
even pokemon stadium had better models than 3dshit

>>29478535
Smash forced shut down everything on your 3DS to run. The 3DS is an outdated system. It'll be replaced by the Switch.

It also isn't that GameFreak can't code; optimization isn't exactly easy to do. Lots of developers do a poor job at optimizing.

File: d2045.gif (2MB, 220x165px) Image search: [Google]

2MB, 220x165px

>>29482654
I don't know how to crack my 3DS
>inb4 /hbg/
Guide is too confusing got my dick stuck in the toaster.

>>29482760
You're objectively wrong

>>29478008

It's. Not. The. Model.

Go play with your Salamence in Pokemon-Amie. You'll notice that it's standing on the ground. The flying animations are for battle.

File: Lucario models.png (403KB, 1222x697px) Image search: [Google]

403KB, 1222x697px

>>29482760

Wrong. The 3DS models are vastly superior and have a higher polycount.

By contrast, Colossum, XD, and Battle Revolution ripped most of the old Pokemon's models straight from the Stadium games, which is why they looked like shit compared to the newer Pokemon's models.

File: voltorb model.jpg (115KB, 806x768px) Image search: [Google]

115KB, 806x768px

A model that got downgraded. Voltorb is now a perfect sphere, lacking his brows.

>>29476930

Because the models in those games look like dogshit compared to Game Freak's models.

>>29483131
You can still see some vertices

>>29482760
See >>29479583
>>29479625

Are you fucking blind?

File: b18ccc1a3d766fd6744f885517786108-650-80.jpg (38KB, 603x402px) Image search: [Google]

38KB, 603x402px

>>29476995
>reused N64 models
I love how shitty they look in Battle Revolution, like they're not even trying to hide it.

>>29476930
Because the Gamecube wasn't a piece of shit.

>>29478474
Except HAL didn't make the models, Creatures did.

>>29478535
GameFreak didn't make the models, the problem is that GameFreak didn't tweak the futureproofed models Creatures provided.

>>29483442
It wouldn't be able to run the games at all if they had the new models you know.

>>29479897
>physical attacks would cut to make it look like punches were actually connecting
Even as a kid I thought that the physical attack animations looked ridiculous. Most of them have the Pokemon roaring or something, then a cut to the other Pokemon getting hit.

>>29478474
>Bring HAL back to do the models. They gave each pokemon WAY more personality than the boring static shit we're given now.
Do yourself a favor and actually play the games instead of going by the rips.

File: mewtwo revolution.png (121KB, 750x650px) Image search: [Google]

121KB, 750x650px

>>29483420
A few pokémon got new models in Battle Revolution, and this made the old N64 models look even more dated.

>>29483040
>Wrong. The 3DS models are vastly superior and have a higher polycount.
For reference, Pikachu alone has twice as many polygons as Pokemon Stadium was capable of displaying on-screen at once. Those models are fuckhuge for a 3DS game.

File: Umbreon.png (308KB, 975x650px) Image search: [Google]

308KB, 975x650px

>>29483442

Example of future-proofing: Pokken uses the same model as the 3DS games for the Support Pokemon, just with some textures slapped on

On a system with more power, they can just touch up the current models.

>>29483442

The 3DS is more powerful than the Gamecube though.

File: 1105.png (85KB, 834x513px) Image search: [Google]

85KB, 834x513px

>>29483420
Battle Revolution also has widely varying quality textures. This is Regigigas

They simply didn't gave a fuck about some Pokémon.

File: 1059.png (21KB, 179x241px) Image search: [Google]

21KB, 179x241px

>>29484781
And this is Sceptile. Kek

>>29482760
They had nicer animation than XY models, yes. But they were lower poly, and the lighting engine made those polys more apparent.

File: 1035.png (144KB, 884x512px) Image search: [Google]

144KB, 884x512px

>>29484818

File: 1048.png (16KB, 163x225px) Image search: [Google]

16KB, 163x225px

>>29484862
Thank god the hacks from Genius Sonority aren't near Pokémon anymore.

File: pokemon-shuffle-169.jpg (110KB, 578x327px) Image search: [Google]

110KB, 578x327px

>>29484899
I'm sorry to tell you this, anon...

>>29484259
3DS is also running two screens at once and a 3D feature that eats up a shit-ton of processing, even when it's turned off. (in games where there's an in-menu option to disable it, the system suddenly runs a LOT smoother)

>>29484088
I think people mostly need to stop confusing bad models with bad animations. The games would look much better if they cared more about the animations. It's rediculous when you compare Blastoise in ORAS to Blastoise in Stadium. In Stadium when he does Hydro Pump, the shell opens for the cannons to come out and fire (or at least look like he's firing from the cannons) where in ORAS, he just does a roar and it fire at the opponent. Even Mega Blastoise he just fires from his mouth. It's just absurd.

>>29486162
The gen 7 starters' signature moves look completely natural so maybe they fixed Blastoise's animations

then again, Greninja still looks dumb when using Water Shuriken

>>29486298
I hope so, even if it's just a little. It's so depressing playing Stadium and seeing Pokemon move around so wildly like actual monsters inbetween attacks, and when they get KO'd, react so harshly like they've actually been knocked out. As it was in ORAS, it's almost like we might as well been back in BW.

>>29476930
>Why could this game, with bad textures/low polygon count/poorly animated/bad lighting,,,etc...run better on a home console, than the new games with high poly-count, better animated, better textured, better lighting, on a handheld.

Gee...I wonder why?

>>29485085
Is there a hack available that turn the feature off in the pokemon games to see if it runs smoother?
If there is, I want that hack.

Do the people in this thread even realize how much processing power it takes to render a polygon? or that MORE polygons equals GREATER demand from the rendering tool, be it from integrated graphics from the chip or a separate computing device dedicated to graphics rendering, REGARDLESS of the size of the polygons?

For real though, it's much easier to render 1 big polygon than it is to render 10 tiny ones. But, the tinier the polygons, the more "curvature" you can add to a model. It makes it look much smoother, at the great cost of more processing power.

As far as textures go, yeah, really good ones will eat up some power, but there are "tricks" or artistic freedoms that you can take to make a game look good without sacrificing too much power.

That's why a lot of cel shaded games hold up visually as compared to "at the time" amazing textures. Artistic Style and visually pleasing does not mean "Good Graphics." It just means it looks pretty.