- Pronouns
- He/Him
Well, when you think about it, for a tech demo input latency isn't exactly a major consideration.Frame generation really isn't a benefit below a certain base framerate, since your input latency is still tied to the native frames.
Well, when you think about it, for a tech demo input latency isn't exactly a major consideration.Frame generation really isn't a benefit below a certain base framerate, since your input latency is still tied to the native frames.
Frame generation really isn't a benefit below a certain base framerate, since your input latency is still tied to the native frames.
Yes, but it would be an extreme misrepresentation to tell the devs you're courting "This is running on target specs!" and then later reveal it was running at 15fps with frame generation. Not that I believe that was the case, but I hope you can see what I'm saying.Well, when you think about it, for a tech demo input latency isn't exactly a major consideration.
If patches are possible I wouldn't expect anywhere near most games to be affected, but rephrasing your question to "Should any existing 60fps Switch game be able to be a 4K60 Switch 2 game if patched/ported to take advantage of the new hardware?" I can't think of a reason why not. It would be more easily done for some games than others.Should the new Switch be able to 4k/60fps (DLSS) all Switch games that are 720p/60fps if patched and the only difference between versions is resolution?
Xenoblade 3, at least, used a temporal upscaler. So closer to FSR2, though not precisely that.Yep! I personally imagine MP4 would target similar performance and resolution as MPR. Up to 900fps and targeting 60fps on Switch docked (600-720p on handheld). Didn't XB3 and Totk use some kind of upscaling FSR too btw?
There's nothing magical about the modes they gave names for easier choosing by consumers, so the demo could theoretically have an internal resolution of like 10p. Except I imagine some of the reports would then mention how shit the new version of BOTW looked.Ghostsonplanets quoting Digital Foundry said:The Legend of Zelda: Breath of the Wild's mooted tech demo is an altogether different proposition, sounding more like a practical example of how DLSS can be transformational for consoles - but again, context is king and we don't have any. Our understanding is that the demo runs at 60 frames per second with a 4K output target, but with DLSS's various quality levels, the native internal resolution could be anything from 720p upwards (Switch 1 runs at 720p30 in mobile mode, 900p30 docked).
Frame generation really isn't a benefit below a certain base framerate, since your input latency is still tied to the native frames.
The fact that frames further apart in time makes the created frame look worse still is a consideration, even if Nintendo somehow got frame generation working only for bullshot demo presentation purposes.Well, when you think about it, for a tech demo input latency isn't exactly a major consideration.
It depends on your definition of "noticeably," but the Switch's internal storage is a little faster than SD cards which are somewhat faster than game cards, with up to several seconds separating them overall in loading sequences. It's certainly noticeable to speedrunners.So, a few general comments on the updates:
Firstly, and most importantly, now that "around March" is on the table, I'd like to officially announce the re-launch of #TeamLeapDay. We'll be accepting membership applications by messenger pigeon, which must be accompanied by a one thousand word essay on why Wave Race should be a launch title.
Secondly, it looks like I wasn't completely wrong about BoTW, with both DLSS and fast loading confirmed to be in the demo. No mention of ray tracing, but two out of three ain't bad.
Actually being able to run DLSS at 4K/60fps is a bit better than I'd expected. My personal expectations were 4K/30fps, or around 1440p/60fps, just due to the cost of running DLSS itself, but it looks like it's either cheaper than I expected, or the hardware is more capable than I expected, or a bit of both. Good news either way.
The talk of "instant" load times in BoTW is interesting. Of course nothing is truly instant (even Ratchet & Clank uses a short portal sequence to hide loading, a bit like the old door-opening trick on Metroid Prime back in the day), but we're probably talking around a second or so for it to feel instant. That's about a 30x speed up compared to the Switch.
It's important to note that there are multiple factors which impact loading speeds, not just the speed of the storage itself (although as I've explained before, I was already expecting that to be much quicker). Roughly speaking, I'd categorise them into three different bottlenecks which could factor into how fast loading is:
On Switch, it seems most games are bottlenecked by number 2. We know that T239 contains a dedicated File Decompression Engine, so ideally we're not bottlenecked here anymore, but if we were, it would suggest that the FDE is around 30x as fast at decompressing data as the Switch CPU. I don't know if we can say for sure what data rates BoTW was operating at while loading, but I don't believe it's noticeably faster on internal storage or microSD than game cards. Game cards top out at 50MB/s, so if the Switch CPU was able to keep up with that, then we'd be looking at 30x as much, or about 1.5GB/s of compressed data coming into the FDE. It could certainly be less than that, with the CPU perhaps bottlenecking things even lower on the Switch, but honestly 1.5GB/s or so wouldn't be crazy. Both MS and Sony designed much faster decompression hardware 3 years previously, and Nvidia isn't exactly a slouch when it comes to designing fast coprocessors.
- The speed of the storage medium itself. Obviously this can be a big bottleneck, as if you want to pull 1GB of data off a storage device which maxes out at 100MB/s, you can't do that any quicker than 10 seconds.
- The CPU overhead associated with pulling that data off the storage medium. The main part of this nowadays is decompression. If your CPU can't decompress data fast enough, then even if you've got super fast storage you're not going to be leveraging it (unless you want to ship purely uncompressed assets and balloon the game size). Aside from decompression, though, there's still some additional overhead of just communicating with the storage medium and transferring the data, which can be non-trivial.
- Non-storage related CPU work. This is doing everything you need to do to actually set up the game state. Allocate memory for all the different things you need to keep track of during gameplay, initialise all the different systems which are going to be running, and sync the game state with the save file. This is also where you're doing any kind of procedural generation, which is often overlooked when thinking about load times. People playing No Man's Sky on the PS5 for the first time were really puzzled why it wasn't loading much quicker than the PS4, but the game is fully procedural, so it was never really bottlenecked by storage in the first place.
If we were bottlenecked on storage, then again comparing to the original Switch game card as the baseline we'd once more be looking at around 1.5GB/s. For a while I've been considering UFS 3.1 to be reasonably likely, which ranges from 1.7GB/s to 2GB/s read speeds, and is pretty much in line with this. In fact, if Nintendo actually is considering 512GB of storage for the console, then 1.7GB/s UFS 3.1 is the slowest option they would have. Nobody makes 512GB modules for either eMMC or UFS 2.
The last one probably isn't trivial for BoTW on the original Switch, although likely a lighter workload than it is for ToTK with its increased number of gameplay systems. I definitely don't expect a 30x speedup here, but between taking the decompression work off the CPU, and just having more, faster CPU cores to do the work, it should be much faster either way.
Of course this is all based on a very specific reading of "instant" loading. If 2 seconds counts as instant, then divide every number in half. If it's 0.5 seconds, multiply by 2, etc. However, given expectations of internal storage close to 2GB/s, and dedicated decompression hardware to remove the main CPU bottleneck, dropping load times from 30s to around 1s seems quite reasonable.
I think it is. Developers want an idea of what they can reasonably expect to ship on the hardware. Bullshot demos are usually aimed at the general public.Well, when you think about it, for a tech demo input latency isn't exactly a major consideration.
Oh I absolutely do, I was being a bit cheeky. That would be a way to "cheat" in a tech demo.Yes, but it would be an extreme misrepresentation to tell the devs you're courting "This is running on target specs!" and then later reveal it was running at 15fps with frame generation. Not that I believe that was the case, but I hope you can see what I'm saying.
Did I miss that the next Switch is doing frame generation? I really doubt it's the case.Hm, no ?
no. it probably doesnt. any discussion of it here is hypotheticals.Did I miss that the next Switch is doing frame generation? I really doubt it's the case.
It was mentioned here a week ago that data miners apparently found evidence of enhancement support added to one of the Xenoblade titles following a patch update, then of course there was PokéPoster asserting work being done on Scarlet & Violet, and now an improved Breath of the Wild showcased at GamescomIf patches are possible I wouldn't expect anywhere near most games to be affected, but rephrasing your question to "Should any existing 60fps Switch game be able to be a 4K60 Switch 2 game if patched/ported to take advantage of the new hardware?" I can't think of a reason why not. It would be more easily done for some games than others.
Xenoblade 3, at least, used a temporal upscaler. So closer to FSR2, though not precisely that.
Artefacts would be, though, and I can imagine them being rough trying to use DLSS-FG to get from 15fps to 30fps. That's a big old gap between each frame you're trying to interpolate over.Well, when you think about it, for a tech demo input latency isn't exactly a major consideration.
Another mention of t239context?
From Aug22
Look to the far right under the ampere b header. It's T239. It proves this talk of frame generation and Lovelace is silly.context?
From Aug22
Perhaps it has already been mentioned here at some point, i dont really rememberThe commit is from November 2022? Or was that not found before
The commit is from August 2022, when that file was initially created. And we did discuss it in the thread, probably in September 2022.The commit is from November 2022? Or was that not found before
A is the first sub-family (there's probably an official Nvidia term but it's escaping me at the moment) and B is the second. For Ampere, the first was datacenter and the second was everything else.Anybody know what the difference would be in "ampere_A" and "ampere_b" and if it matters for us?
Anybody know what the difference would be in "ampere_A" and "ampere_b" and if it matters for us?
It's still interesting to see "T239 = Ampere" from Nvidia but I guess that's not really new thoPerhaps it has already been mentioned here at some point, i dont really remember
We saw that in the initial leak in February 2022, it's been known.It's still interesting to see "T239 = Ampere" from Nvidia but I guess that's not really new tho
All you nerds talking about your ray traced metroids and Mario's
Meanwhile I'm dreaming of games that look like this!
Ampere A is the HPC chip. Has no rt cores and more tensor cores. Ampere B is the gaming designAnybody know what the difference would be in "ampere_A" and "ampere_b" and if it matters for us?
And then when the TX1 was announced for Switch, people posted the poor performing shield port proving Switch was doomed to failHow far we’ve come. Remember the dark days when Capcom said Wii couldn’t run the title screen for Resident Evil 5?
Thats what i expected, but coming from kepler I brought it here just in case.And we did discuss it in the thread, probably in September 2022.
Probably have to take the source code and attach a new renderer to it. That's how Mario 64 RT is doing itI wonder how hard/easy it will be to get DLSS/RTX into NSO games, because that would be a cool way to resfresh the older games. I would like to see how it would work with Gamecube/Wii games. Also, the tensor cores should be able to help create ai generated improved textures right?
That’s a generous offer. I have a family member who’s a professional conference organizer. From the bits and pieces I heard, it seems unlikely that a conference center would provide you with their booking information unless you’re an organizer. Also, setting up a event of that size, it probably will require a few days to set up. So even if it’s confirmed that Nintendo’s booked the South Halls on the days prior, we can’t be certain of a press conference.Someone gotta call Tokyo Big Sight and ask them if the venue is available the Friday before for an event, I can actually ask my Japanese girlfriend to do it. Shall we ?
This feels like something one of the birds could clarify. The fade in and out animation even if it doesn't drop to the BotW loading screen could give you a few seconds to load out and in objects.Of course this is all based on a very specific reading of "instant" loading. If 2 seconds counts as instant, then divide every number in half. If it's 0.5 seconds, multiply by 2, etc. However, given expectations of internal storage close to 2GB/s, and dedicated decompression hardware to remove the main CPU bottleneck, dropping load times from 30s to around 1s seems quite reasonable.
Aug 8 2022 (use git blame to see commit information of the line)The commit is from November 2022? Or was that not found before
Could you find the original post/source for this? I'm interested in seeing this.It was mentioned here a week ago that data miners apparently found evidence of enhancement support added to one of the Xenoblade titles following a patch update, then of course there was PokéPoster asserting work being done on Scarlet & Violet, and now an improved Breath of the Wild showcased at Gamescom
Probably safe to say if it's a (recent) Pokémon, Mario, Zelda, Splatoon, Kirby or Xenoblade title, it's getting a makeover
A reveal date for March 2024 wouldn't make a lot of sense, if it's entering production in December then descriptive and photographic factory leaks will follow within days of beginning assembly - if Nintendo don't announce it before mass production then they'll lose control of the information cycleI tend to be on the skeptical side of things when it comes to Nintendo hardware, but that tech demo sounds seriously impressive. DLSS sounds like its doing some real heavy lifting, so I suppose that Nintendo-NVidia partnership for the past decade or so has really paid off.
The upscaled 4k sounds great, but truthfully its the frame rate that really sounds like gravy to me. I can't imagine I'd really need much else as long as everything can hit that 1080p / 60fps threshold, DLSS and 4k just makes it all the sweeter.
I've always been team Q2/Q3 2024 (sometime around June or July), so my personal guess is that the March 2024 date floating around is probably a reveal date instead of a launch date. My guess is that the reason they're throwing it out there is to see if they can get any of these smaller developers (because I'm confident your big companies like Bandai Namco, Capcom, Square Enix, etc. have already known about the Switch 2 for a minute now) to see if they can do anything within the next couple of months for launch title / first year releases.
There's a chance they have a special version of DLSS running but I can't imagine they're doing something like running the demo at 240p internally and using DLSS to boost it to 4k. That would either be a mushy muddy mess or if it did work well, actual wizardry that NVidia would want out on their PCs instead of locked to a business partner's console. UE5 has become a lot more stable and a lot more optimized over 2 years. That's the most likely explanation.
Yes, I've partly misremembered it, it was to do with the OS but the comment was made in response to one discussing Xenoblade:Could you find the original post/source for this? I'm interested in seeing this.
Datamines of the OS show the existence of a so-called "datapatch", which is speculated to be for next gen patches. It was added to the OS around the same time as the new memory management system, which is also for new hardware, so I think it probably is to do with next gen patches.
Yes, I've partly misremembered it, it was to do with the OS but the comment was made in response to one discussing Xenoblade:
This is "nn::ncm::[sic]DataPatchId".
This was added with [15.0.0+].
The Switch 15.0.0 system update was released on October 11, 2022 (UTC). This Switch update was released for the following regions: ALL, and CHN.
Yes yes ice cream so goodThat's their new slogan right there:
Nintendo Switch 2, better than ice cream...
I think Game Freak is sweating hard right now, they will have to scale up from their gamecube style graphics hard on the next switch, maybe go on a hiring spree for new devs?Don't forget Game Freak and TPCI!
You know, that "early 2024" next gen patch for ScVi makes a lot of sense now.
Game Freak hire more devs? Hell will freeze over before this is a reality. 3 people and a cat will continue to make Pokemon until the end of time.I think Game Freak is sweating hard right now, they will have to scale up from their gamecube style graphics hard on the next switch, maybe go on a hiring spree for new devs?
I think Game Freak is sweating hard right now, they will have to scale up from their gamecube style graphics hard on the next switch, maybe go on a hiring spree for new devs?
They're currently on one, and with Scarlet and Violet DLC (and a likely next gen patch) spread out over 2023 and 2024, it looks like they might be taking a bit of extra time.I think Game Freak is sweating hard right now, they will have to scale up from their gamecube style graphics hard on the next switch, maybe go on a hiring spree for new devs?
they already areI think Game Freak is sweating hard right now, they will have to scale up from their gamecube style graphics hard on the next switch, maybe go on a hiring spree for new devs?
The Game Freak situation isn't salvageable without Nintendo stepping in to start making demands or inserting themselves into the heart of the development process, which they probably can't do due to whatever way the contract was drawn up or else they would've done so a long time ago alreadyI think Game Freak is sweating hard right now, they will have to scale up from their gamecube style graphics hard on the next switch, maybe go on a hiring spree for new devs?
I think I've read in this thread speculation that Ultra Performance has been built with Switch 2 in mind.There's a chance they have a special version of DLSS running but I can't imagine they're doing something like running the demo at 240p internally and using DLSS to boost it to 4k. That would either be a mushy muddy mess or if it did work well, actual wizardry that NVidia would want out on their PCs instead of locked to a business partner's console. UE5 has become a lot more stable and a lot more optimized over 2 years. That's the most likely explanation.