theguy
Paratroopa
i know(Not for a lot of devs)
i know(Not for a lot of devs)
As others have pointed out, the eshop is running in a web browser, but it's running javascript through an interpreter rather than allowing for just in time (JIT) compilation. This eliminates JIT as a vector for security bugs (and its a huge vector for bugs), which is good for Nintendo, but javascript through an interpreter is much slower.Does the Switch allow web view for that stuff, or even period? I thought that the whole reason the eShop is so sluggish is because there's not really much of anything in the way of a web browser to handle the brunt of the work.
If all goes well, Nintendo would have to announce console before gamefreak can announce the enhancement pack.
Ah gotcha. Thanks for the clarification!As others have pointed out, the eshop is running in a web browser, but it's running javascript through an interpreter rather than allowing for just in time (JIT) compilation. This eliminates JIT as a vector for security bugs (and its a huge vector for bugs), which is good for Nintendo, but javascript through an interpreter is much slower.
Further, the eshop web app runs out of its allocated memory quickly, which is why things always seem to reload, because they are.
oofthey should just make really crappy ports of everything for switch and then when switch 2 comes out “here’s your old games but better”
this is a joke
big oof for everyone, if Nintendo/Pokemon Company is stupid enough to do thisThere should be a dozen announced next-gen games with proper trailers and gameplay before Game Freak shows anything.
Imagine a Game Freak game being our first look at a Switch 2. Recipe for disaster.
Definitely.big oof for everyone, if Nintendo/Pokemon Company is stupid enough to do this
If all goes well, Nintendo would have to announce console before gamefreak can announce the enhancement pack.
Some of those would be easy enough, but for what this project seems to be I doubt anybody is getting higher texture quality than PS3/X360 version.PS4 will probably get some additional improvements that the Switch build doesn't. Things like texture quality, texture filtering and shadow resolution could very well be much higher quality than Switch. Perhaps even LOD and draw distance differences.
That all sounds rather unlikely given what we've seen.Switch 2 won’t be out until late 2024 and the DLC will be a year old by then. We might not even see an update and they’ll just focus on the next games instead.
Not trying to deepen an argument here, but 2023's first party lineup is genuinely much stronger for me than 2018's. Aside from Torna, 2018 was pretty much just indies for me.So,
2D Mario, an SNES game, a 3DS game, a Mario Spin-off.
Versus the first home console, mainline Pokémon game and SMASH BROS.?
That's a terribly unfair comparison for 2023, not for 2018. 2023 is closer to Wii U's first year in quality. Which is fine, for a final year!
Ditto. Remove Zelda from the 2023 equation, and I think 2023's lineup is still stronger than 2018's. I bought Smash for the sake of having it as a fun party game, but I'm not nearly as fond of the series as a lot of Nintendo fans are. Maybe that's why I don't hold 2018 in high regard.Not trying to deepen an argument here, but 2023's first party lineup is genuinely much stronger for me than 2018's. Aside from Torna, 2018 was pretty much just indies for me.
That all sounds rather unlikely given what we've seen.
At the very least why don’t they cache the thumbnails on eshopI'm assuming the news applet has a set memory footprint, which allows for its content to always be prepared to fit inside its app and background updates can occur whenever. The eshop content doesn't have that predictability.
Still, I would think that making an app with all of the text of the eshop should be fairly lightweight and could be saved on the device side.
Thick client, thin client/web app. The eternal struggle.
We all have our own viewpoints. For me, the first year of Wii U (which includes much of 2013) was definitely stronger than 2023.Not trying to deepen an argument here, but 2023's first party lineup is genuinely much stronger for me than 2018's. Aside from Torna, 2018 was pretty much just indies for me.
A good point, heck pre-loading all of the eshop text (with formatting) should measure in say a few hundred MB at most.
Shoot format it something like markdown and kick into the web view for purchases. You would only need to load images dynamically.
It certainly seems like a solvable problem.
Like others, I find the eshop "fine", it's just weird that it could be better.
The difference between the two is that the news app is mostly content updates, with the client updating on the same schedule as the rest of the firmware, while the eShop gets code updates fairly frequently. It's hard to tell exactly how often it happens without paying much closer attention to it than I do, but potentially any eShop maintenance is them rolling out new code for the eShop UI. A native eShop app would have to be able to update itself like a game to be feasible, which is definitely something Nintendo could do, but probably won't to keep it fairly platform agnostic and low friction to update.
Ah gotcha. Thanks for the clarification!
Even if they keep things as is for next-gen (running JS through an interpreter), would more and faster memory alleviate some of the issues, or will it be just as slow, minus not having to reload as often due to more memory?
Probably 16GB of 5, the benefits of 5X couldn't make up for an extra 4GB of system memory.What would be better (as a hypothetical)?
12 GB of LPDDR 5X
or
16 GB of LPDDR5
they have and it's getting annoying.What have we seen?
I think you’ve said similar about every Switch Pro/2 release date comment, including dismissing anyone, including myself, who dared say after 2022 or 2023.
Is the new take it will definitely be early 2024?
Bit of a dumb question to piggyback off of this. I understand that 1. My knowledge is limited, and 2. This could potentially open an entire can of worms: If Nintendo wanted to speed things up, while still not doing JIT compilation in the name of security, would they be able to use the HDE in tandem with a lower clock CPU and get the same result as a clock increase when running applets like the eShop, while also not using as much power? Or would powering the HDE be a bit of a waste - or even not have any use at all - due to the eShop being small and so heavily online driven?I don't think actually loading the data takes all that long, it's likely only a megabyte or so per product page. The news applet only pre-loads content so that it can absolutely minimise friction on the front page, but even on non pre-loaded pages it's very quick to load.
I'm also fine with the eShop personally, but if I were working for Nintendo it would be another matter. Slow ecommerce platforms lose sales, and the eShop isn't immune from that
I appreciate there are good reasons for going with a web app approach, including increased flexibility on updates, I just think it's interesting that Nintendo have also provided an example of exactly how much is being sacrificed for that flexibility.
I also wouldn't necessarily say that eShop maintenance is tied to client-side updates, they could be mostly infrastructure updates. Given that it's a web app, Nintendo could conceivably push out updates with zero downtime. I'm curious if anyone has been tracking eShop client updates.
A faster CPU would be the biggest difference. Comparing a Shield TV to an A78-based phone in Geekbench, you're looking at about 2.2x the performance per clock on the browser sub-task just from the architectural improvement. With a modest clock increase we could get around a 3x speedup from the Switch NG's CPU vs the Switch. Of course the Geekbench browser sub-task may not align exactly to what the eShop's doing, but it's probably roughly in the same ballpark.
Just saw this in my sub box should be a interesting watch
I haven't been tracking it closely, but visible changes to the eShop UI that I have noticed have been generally packaged with eShop maintenance. It's clearly for both infrastructure and the UI.I appreciate there are good reasons for going with a web app approach, including increased flexibility on updates, I just think it's interesting that Nintendo have also provided an example of exactly how much is being sacrificed for that flexibility.
I also wouldn't necessarily say that eShop maintenance is tied to client-side updates, they could be mostly infrastructure updates. Given that it's a web app, Nintendo could conceivably push out updates with zero downtime. I'm curious if anyone has been tracking eShop client updates.
FormerWhat would be better (as a hypothetical)?
12 GB of LPDDR 5X
or
16 GB of LPDDR5
Probably 16GB of 5, the benefits of 5X couldn't make up for an extra 4GB of system memory.
Interesting, I've heard both ways now. I would assume there are various pros and cons to each.Former
The most annoying thing in the world:they have and it's getting annoying.
If you're referring to the decompression hardware, there probably isn't enough for that to do to make a meaningful difference.Bit of a dumb question to piggyback off of this. I understand that 1. My knowledge is limited, and 2. This could potentially open an entire can of worms: If Nintendo wanted to speed things up, while still not doing JIT compilation in the name of security, would they be able to use the HDE in tandem with a lower clock CPU and get the same result as a clock increase when running applets like the eShop, while also not using as much power? Or would powering the HDE be a bit of a waste - or even not have any use at all - due to the eShop being small and so heavily online driven?
I know that it's typically not common practice to use decompression on front end stuff like websites, but I figured I'd pick your brain a bit and try to learn in the process.
ah yes that's what it isThe most annoying thing in the world:
Optimism
Figured as much. Thanks!If you're referring to the decompression hardware, there probably isn't enough for that to do to make a meaningful difference.
Don’t think so unless they pull a new tier of NSO like NSO++.i wonder if ubisoft+ and ea play will come to NSO next gen
I wonder what happened to game freak, sun and moon on the 3DS looked amazing and played amazing. Most of the 3DS Pokemon games did look and run great for the most part. Then the switch comes and it looks like they just ported a 3DS game that looks like it has been touched up to work on modern consoles. It was disappointing to meDefinitely.
Although imagine, and that's a bif IF, if Game Freak magically got their shit together and has been working with another studio to make an absolutely stunning graphics overhaul?
Something that no one could see coming and that would look so good that it'd just have to be next gen exclusive?
The gap with how Gen 9 currently looks would be so insanely huge that it would actually make sense to showcase it when revealing Switch 2.
But that's for another timeline.
Now that I'm back to reality, let's hope some DLC 2 date leak or anything adds credibility to the whole 4chan leak so it would (almost?) confirm Swtich NG for early 2024.
16GB of LPDDR5, but that is a slightly nuanced answer.What would be better (as a hypothetical)?
12 GB of LPDDR 5X
or
16 GB of LPDDR5
It's not like a major game like say, Last of Us Part 2, has ever stopped a console releasing anyway.Sensing some Mario Wonder disrespect brewing to justify an early 2024, when that game breaks records and help move a lot of hardware/software I hope you will regret your words and deeds.
How does the power requirements scale with the overclocking? Is it linear or exponential? Would it be worth it to overclock 5X "just a little"?16GB of LPDDR5, but that is a slightly nuanced answer.
The thing is that 5X is, essentially, a "sanctioned" overclock of 5. So while it offers a higher bandwidth cap, it doesn't offer any power draw advantages. If you keep it the same speed as 5, it draws the same power as 5. Your run it at 5X speeds, you pay a proportionately higher battery life cost.
Side note: You'll see power efficiency wins claimed for 5X all the time. They're not for 5X protocol but updates to the manufacturing process for the memory controller and the RAM itself. In practice, in our case, all those efficiency wins apply to LPDDR5 as well.
If we got 5X, I wouldn't be surprised if Nintendo does it purely because it can source 5X more cheaply long term, and it still clocks it at base 5 speeds for battery purposes. In which case, no advantage for 5X.
If what we're really is asking is "12GB at 5X top speed or 16GB at 5's top speed, ignore the battery life problems" then my answer is becomes contingent on the rest of the design of the system - storage access speed, and GPU clocks - but that I would tend to come down on the side of "more RAM"
If you assume the uptick is because developers were getting kits or demos at Gamescom you could assume launch is still ~12 months out.doesn't dev kits getting out there in a more significant capacity more suggestive of late 2024 than earlier. after all it normally takes longer than 6 months to develop a game.
not saying it won't be early 2024 as plenty of trusted partners probably had them already and it all hinges on first party content, but I wouldn't take it as encouraging for the earlier release.
and oh yeah as someone brought it up again - Ridge Racer 8!! this would be so amazing for launch, the glorious return of a franchise MIA on consoles since PS3 (no the other games don't count). it was 100% in development for the OG Switch so it makes sense it was moved to next-gen instead of scrapped. i'm really excited for this one.
It think the issue is that they're a small team spreading themselves too thin in a time where game development on average, takes longer than 3 years and the output of the entire Pokemon franchise does not accommodate either Game Freak's needs as developers or how games of large scales are made these days.I wonder what happened to game freak, sun and moon on the 3DS looked amazing and played amazing. Most of the 3DS Pokemon games did look and run great for the most part. Then the switch comes and it looks like they just ported a 3DS game that looks like it has been touched up to work on modern consoles. It was disappointing to me
Going off of memory (not the most reliable indicator, I know), 2018 had Smash Ultimate, Let's Go Pikachu, Kirby Star Allies, Super Mario Party, Tropical Freeze port, Captain Toad port + extra levels, Mario Tennis Aces, Celeste port, Hollow Knight port, Machina game thingy, Dark Souls port, and Octopath Traveler. Were any systems added to NSO in 2018?We all have our own viewpoints. For me, the first year of Wii U (which includes much of 2013) was definitely stronger than 2023.
Not that I don't think Redrakted NG isn't coming out early next year, but "NX" was already said to be released early 2017 by the time that leak came out.If you assume the uptick is because developers were getting kits or demos at Gamescom you could assume launch is still ~12 months out.
However, playing devils advocate, the first big leak for Switch was from Digital Foundry in June 2016 following some sort of presentation regarding the then "NX" console and Switch was announced in Oct 2016 and Launched in March 2017.
No, the 3DS games got shat on a fair bit for how bad their performance could get during Hordes/lots of effects like Totem aura and when you turned 3D onI wonder what happened to game freak, sun and moon on the 3DS looked amazing and played amazing. Most of the 3DS Pokemon games did look and run great for the most part. Then the switch comes and it looks like they just ported a 3DS game that looks like it has been touched up to work on modern consoles. It was disappointing to me
Fair, my point was more about the devkit leaks being tied to launch timeframe, which to be clear I don't think is a good metric beyond "more leaks means hardware is nearing finalization".Not that I don't think Redrakted NG isn't coming out early next year, but "NX" was already said to be released early 2017 by the time that leak came out.
Also, the Switch was kinda slapdash, anyway, so that might not make for the best comparison for when devkits were sent out.