mjayer
Bob-omb
I am. With what we know of the Nvidia hack that’s what it is. Nintendo may not call it that or market it as such but ya.So is it okay if we start calling this thing Switch 2 in the meantime?
I am. With what we know of the Nvidia hack that’s what it is. Nintendo may not call it that or market it as such but ya.So is it okay if we start calling this thing Switch 2 in the meantime?
That depends entirely on how you design them. For example, the range of motion with the analogue shoulders on GameCube controllers likely does not require that much range, as there were to my knowledge certain dead zones in the range of motion that did not register as a different input, even in games that used them. So designing analogue shoulder of trigger buttons would only demand a range of motion that is useful. We can see this kind of design change with the original Classic Controller on Wii, which had much smaller analogue shoulder buttons with far less ”play” in their range of motion before the hard click overall.The GameCube style of analogue triggers is the worst idea to a joycon implementation, it needs so much space
I've been somewhat consciously trying to refer to it as Drake to avoid the Pro vs 2 debate, but I ultimately do view it as Switch 2, and have since we first got wind of it being Ampere.So is it okay if we start calling this thing Switch 2 in the meantime?
Probably the latter, especially with Nintendo being recently granted a patent for AI image upscaling.i'm curious if we're gonna see nvidia technologies in Nintendo's games like RTXDI or if they're gonna make their own solution
yes, but things like restir-based ray tracing is pretty novel (with the most referenced paper for derivative techniques coming out in 2020). whether Nintendo goes so hard into ray tracing is a question that needs to be answered firstProbably the latter, especially with Nintendo being recently granted a patent for AI image upscaling.
In terms of hardware, it's absolutely the next generation of Nintendo tech. It's a completely new architecture, with new features, and if you make an exclusive game for it, it will blow away anything possible on TX1. How Nintendo will market it is anyone's guess, but the Drake chip will be here for years and there will be a substantial number of exclusives on it (meaning on the Drake hardware but not TX1).So is it okay if we start calling this thing Switch 2 in the meantime?
Another one?Probably the latter, especially with Nintendo being recently granted a patent for AI image upscaling.
No, the same one discussed on September 2021, which was recently granted by the USPTO a little more than a month ago.Another one?
I see. Still kind of doubt this will actually be used as a dlss replacement in games.No, the same one discussed on September 2021, which was recently granted by the USPTO a little more than a month ago.
Probably not, but it does put Nintendo on solid ground should they need to implement Switch back compat on a future non-Nvidia deviceI see. Still kind of doubt this will actually be used as a dlss replacement in games.
Actually, wonder if the XBC3 Upscaling solution is a variation of that made to run on Shader cores rather than AI-Cores.Probably the latter, especially with Nintendo being recently granted a patent for AI image upscaling.
it's most likely that Monolith made their upscaler independent of NERDActually, wonder if the XBC3 Upscaling solution is a variation of that made to run on Shader cores rather than AI-Cores.
If they are not going with Nvidia then what would the options be? Because it’s not just hardware Nvidia has helped with.Probably not, but it does put Nintendo on solid ground should they need to implement Switch back compat on a future non-Nvidia device
We are talking long long term, like in 20 years+If they are not going with Nvidia then what would the options be? Because it’s not just hardware Nvidia has helped with.
nvidia aren't the only ones with matrix acceleratorsIf they are not going with Nvidia then what would the options be? Because it’s not just hardware Nvidia has helped with.
Is Intel interested in designing custom Arm based SoCs in general?nvidia aren't the only ones with matrix accelerators
We are talking long long term, like in 20 years+
Sure, I’m just talking in general in terms of companies & not specifically about upscaling tech.nvidia aren't the only ones with matrix accelerators
No word on pricing. This article gives at least a release window (early 2023 for flagship smartphones).
Of course depends on when Drake will come out, but if it is H1 2023, wouldn't anything new coming out now, whether it is a new storage option, new manufacturing process, or some new standard, be irrelevant, since by now all the pieces of the puzzle should have been finalized, give or take memory size and frequencies (?)
Generally speaking, yes.Of course depends on when Drake will come out, but if it is H1 2023, wouldn't anything new coming out now, whether it is a new storage option, new manufacturing process, or some new standard, be irrelevant, since by now all the pieces of the puzzle should have been finalized, give or take memory size and frequencies (?)
Digital Foundry speculated that since Monolith Soft is lending dev and tech assistance to BotW2, there is a chance Xenoblade 3's temporal upsampling could be used.… kinda quiet today. Well, with Splatoon 3 using FSR (confirmed?) and it being used for Switch Sports, does anyone think it’s going to be utilized for BOTW2 on OG Switches? Drake will be doing it’s own thing, for sure, but I’m hoping for better performance than BOTW’s 900p30. Hell, 30 fps wasn’t even a given with BOTW. But with 5 years worth of streamlining and development, I hope BOTW2 has some visual improvements.
AMD and Intel I guessSure, I’m just talking in general in terms of companies & not specifically about upscaling tech.
What’s your source on splatoon 3 fsr?… kinda quiet today. Well, with Splatoon 3 using FSR (confirmed?) and it being used for Switch Sports, does anyone think it’s going to be utilized for BOTW2 on OG Switches? Drake will be doing it’s own thing, for sure, but I’m hoping for better performance than BOTW’s 900p30. Hell, 30 fps wasn’t even a given with BOTW. But with 5 years worth of streamlining and development, I hope BOTW2 has some visual improvements.
What’s your source on splatoon 3 fsr?
Also, I’m fairly confident switch sport does not use it, cause if it did it went under John Linnemans radar which I consider unlikely.
I‘m anxious to see this as well. I’ve heard conflicting opinions about HOW optimized BOTW was on Switch, and given my limited technical knowledge I don‘t have an educated opinion myself. The only upgrade on the Switch port was a res bump to 900p and a bigger high texture radius around Link (don’t know the technical term for that), IIRC. Definitely looking forward to seeing the differences between the two when 2 is released.It was discussed earlier in this thread, but with BotW being a Wii U game and having a relatively unoptimized Switch port, I expect a noticeable improvement with the sequel.
Is there a way to prove or disprove that the games use FSR besides copyright notices? From what I’ve read online the general consensus was that Switch Sports does use FSR.Nintendo EPD uses a common graphics library for their games, AGL. FSR is implemented in it so all future Nintendo titles with AGL should include the copyright notice for FSR until they remove FSR from AGL, whether the game uses it or not.
Switch Sport does not run with FSR enabled, it is likely to be the same case for Splatoon 3.
Monolith's temporal technique is pretty decent. I think something like BOTW using it from a higher base resolution would produce some solid results for sure. I will say though that XC3 still has some pretty noticeable blur in spots that I didn't feel BOTW did though obviously they are different games with different focuses.Digital Foundry speculated that since Monolith Soft is lending dev and tech assistance to BotW2, there is a chance Xenoblade 3's temporal upsampling could be used.
It was discussed earlier in this thread, but with BotW being a Wii U game and having a relatively unoptimized Switch port, I expect a noticeable improvement with the sequel.
I can say that after clocking quite a few hours of Xenoblade 3 on my 4K set, the temporal upsampling works a treat. There were legitimate moments where I forgot to turn my mClassic on and the IQ was still good. If the sequel comes out before I get my hands on Switch Advance then I won't mind just playing it Day 1, especially if it uses this technique.
It should tell people enough that it’s using the same textures on a console with 3.25x more usable memory.I‘m anxious to see this as well. I’ve heard conflicting opinions about HOW optimized BOTW was on Switch, and given my limited technical knowledge I don‘t have an educated opinion myself. The only upgrade on the Switch port was a res bump to 900p and a bigger high texture radius around Link (don’t know the technical term for that), IIRC. Definitely looking forward to seeing the differences between the two when 2 is released.
As Hermii said, John Linnemans (Digital Foundry) did not notice the use of FSR.Is there a way to prove or disprove that the games use FSR besides copyright notices? From what I’ve read online the general consensus was that Switch Sports does use FSR.
In theory you can mod the game and write garbage to the code used by FSR. If the game crash, then FSR is used. (pretty much a theory, I don't know how FSR works but I don't think any of the function is used if the game doesn't use FSR at all)Is there a way to prove or disprove that the games use FSR besides copyright notices? From what I’ve read online the general consensus was that Switch Sports does use FSR.
Is there a way to prove or disprove that the games use FSR besides copyright notices? From what I’ve read online the general consensus was that Switch Sports does use FSR.
we don't know if Monolith offers much technical assistance as far as rendering goes. we know that they provided environment design assistance and asset design assistance. I'm not expecting Monolith's TAAU to appear in Zelda, personallyDigital Foundry speculated that since Monolith Soft is lending dev and tech assistance to BotW2, there is a chance Xenoblade 3's temporal upsampling could be used.
It was discussed earlier in this thread, but with BotW being a Wii U game and having a relatively unoptimized Switch port, I expect a noticeable improvement with the sequel.
I can say that after clocking quite a few hours of Xenoblade 3 on my 4K set, the temporal upsampling works a treat. There were legitimate moments where I forgot to turn my mClassic on and the IQ was still good. If the sequel comes out before I get my hands on Switch Advance then I won't mind just playing it Day 1, especially if it uses this technique.
I‘m anxious to see this as well. I’ve heard conflicting opinions about HOW optimized BOTW was on Switch, and given my limited technical knowledge I don‘t have an educated opinion myself.
Well that's just not entirely true. When Breath of the Wild is running on Wii U it uses closer to 1.5-2GB of RAM, the entire OS is jettisoned from memory and the Home Menu needs to be loaded in (the game unloaded, then re-loaded in) when you press the home button.It should tell people enough that it’s using the same textures on a console with 3.25x more usable memory.
I had no idea that happened on WiiU.Well that's just not entirely true. When Breath of the Wild is running on Wii U it uses closer to 1.5-2GB of RAM, the entire OS is jettisoned from memory and the Home Menu needs to be loaded in (the game unloaded, then re-loaded in) when you press the home button.
Meanwhile the Switch was going to be 2 or 3GB of RAM before Capcom intervened to ask for it to be 4GB.
So early Switch games really, really didn't have a lot more RAM to work with than Wii U. And definitely not a quick and dirty port like Breath of the Wild.
More powerful, absolutely, it was a handheld that outperformed their previous home console. But 3.25* RAM available? Nintendo Switch doesn't even have 2* the RAM.
What’s your source on splatoon 3 fsr?
Also, I’m fairly confident switch sport does not use it, cause if it did it went under John Linnemans radar which I consider unlikely.
Switch sports is extremely ugly so that's proof enough right thereIs there a way to prove or disprove that the games use FSR besides copyright notices? From what I’ve read online the general consensus was that Switch Sports does use FSR.
I think BotW 2 is going to be very similar to Xenoblade 3 in terms of raw pixel counts so 540p in handheld and 720p docked with image quality helped massively by other techniques like reconstruction and fsr.… kinda quiet today. Well, with Splatoon 3 using FSR (confirmed?) and it being used for Switch Sports, does anyone think it’s going to be utilized for BOTW2 on OG Switches? Drake will be doing it’s own thing, for sure, but I’m hoping for better performance than BOTW’s 900p30. Hell, 30 fps wasn’t even a given with BOTW. But with 5 years worth of streamlining and development, I hope BOTW2 has some visual improvements.
FSR 1.0 is nowhere near good enough for people to not notice it being used when you're running at switch levels of resolutionSwitch sports is extremely ugly so that's proof enough right there
I'm only partly joking
I really would expect Switch Sports to have significantly less jaggies if it was enabled. Its so visually noisy... and if it were using it then what's the base resolution running at 240p?
I guess another reason right there... if you couldn't notice ... why use it at all?FSR 1.0 is nowhere near good enough for people to not notice it being used when you're running at switch levels of resolution
Do you have a reference for this? I'm surprised this is possible. Certainly it can't be the entire OS, as the game depends on system services, and there has to be a background process for loading the shell, otherwise game code could run arbitrary system code, which would be a major security back door.Well that's just not entirely true. When Breath of the Wild is running on Wii U it uses closer to 1.5-2GB of RAM, the entire OS is jettisoned from memory and the Home Menu needs to be loaded in (the game unloaded, then re-loaded in) when you press the home button.
That is exactly the point - this whole thread is "how optimized for Switch was BotW" and the answer is "not very."Meanwhile the Switch was going to be 2 or 3GB of RAM before Capcom intervened to ask for it to be 4GB.
So early Switch games really, really didn't have a lot more RAM to work with than Wii U. And definitely not a quick and dirty port like Breath of the Wild.
Switch has 2x the RAM. Switch has 4GB, WiiU has 2GB. Both systems reserve a GB for System use. In conventional use cases, yes, the ~3x number is correct.More powerful, absolutely, it was a handheld that outperformed their previous home console. But 3.25* RAM available? Nintendo Switch doesn't even have 2* the RAM.
It is a spatial upscaler, the patent specifically mentions upscaling as part of a system service without engine level integration. It is a block based upscaler that uses a CNN - the specific advantages of the technique are that it is designed to run in real time on heavily memory constrained devices. It is pretty clearly targetted at real time upscaling of games on the Switch - it specifically mentions an acceleration strategy using the Tegra X1, and how to disable/enable upscaling in response to being docked, in order to preserve battery life.So I didn't really look into the Nintendo upscaling patent, but does anyone know whether it's spatial upscaling (as in it uses only the information about the current frame) like FSR 1.0, or if it's temporal upscaling (as in it also uses information from previous frames) like DLSS 2.0+ and FSR 2.0?
If it's like FSR 1.0, maybe it could be a system-level toggle (kinda like in the Steam Deck) to maybe make some games that don't support DLSS look better/increase fps, since FSR 1.0 doesn't really require too much developer intervention (I assume, since the Steam Deck offers the toggle at the system level), contrary to FSR 2.0 and DLSS 2.0+. Could that be possible?
It's a cheap way to make displaying subnative resolutions suck slightly less, but I think it would take quite a trained eye to just look at a running game out of context and properly tell if it was in use.I guess another reason right there... if you couldn't notice ... why use it at all?
Yes and no. With Steam Deck it's plausible the user could tell a game to render at any lower resolution. For any Switch game to date it's usually going to be the case that the big scaling is done within the game before the UI is slapped on, so the system just receives a 1080p image and scales it if the output resolution is not 1080p. So a game like Witcher 3 rendering at 720p or less would see no new benefit on a 1080p screen. On a future Switch model it could be told to automatically apply it to base Switch games being output at 4K, or portable mode to a new resolution if they don't stick with ancient 720p. Would have 0 affect on FPS, though.If it's like FSR 1.0, maybe it could be a system-level toggle (kinda like in the Steam Deck) to maybe make some games that don't support DLSS look better/increase fps, since FSR 1.0 doesn't really require too much developer intervention (I assume, since the Steam Deck offers the toggle at the system level), contrary to FSR 2.0 and DLSS 2.0+. Could that be possible?
if it's been integrated into the tools, then it has to be mentioned whether it's used or not. the simple answer is, Nintendo integrated it for testing purposes but didn't use it in the final buildI guess another reason right there... if you couldn't notice ... why use it at all?
I don't know if BotW does this or not, but there's definitely precedent. A bunch of later 3DS titles actually run in a special mode that changes the memory layout to allocate a bit more RAM to the game when run on Old 3DS. Some of the heavier applets are locked out in this mode.Do you have a reference for this? I'm surprised this is possible. Certainly it can't be the entire OS, as the game depends on system services, and there has to be a background process for loading the shell, otherwise game code could run arbitrary system code, which would be a major security back door.