the hero we deserve. Happy New Year!Ma
ni
fest
ing
![]()
the hero we deserve. Happy New Year!Ma
ni
fest
ing
![]()
So
What now
Guess we're just waiting for around the 9th now. Funny that it also lines up roughly with when we should get new shipping info.So
What now
1. Validate it and show off how smart you've been
2. Submit it somewhere for credit
3. Put it on the ol' CV
4. Print it and frame it to put over your mantelpiece
My understanding with AMD's rasterization advantage as compared to nvidia starting with the 20xx series card is nvidia starting with those cards devoted some of the silicon to tensor cores for DLSS while nvidia did not. is that a fair understanding?Prediciting Switch 2 performance, part 2: The AMD raster advantage.
Here is a similar graph from before, except now it's for AMD cards. Same benchmark suite, same CPU setup.
Card 6500 XT 6600 6600 XT 6700 XT Average 44.8 82.4 99.2 120 TFLOPS 5.7 8.9 10.6 13.2 FPS/TFLOP 7.859649123 9.258426966 9.358490566 9.090909091
You'll notice a couple things. First off, AMD starts similarly consistent in it's FPS/TFLOP numbers, but totally falls apart at the bottom of the stack. Something about the 6500 XT is wrong and it is vastly less efficient than the other cards in the stack.
However, these performance numbers are much higher than Nvidia's. If you've heard about the AMD raster advantage, there it is. With the exception of the obviously broken 6500 XT, AMD is performing 38% better than Nvidia. This is why you can't compare Series S to Switch 2 just by TFLOPS.
An interesting but open question - does the Series S have the same problem affecting the 6500 XT? In making my performance predictions I assume it does not. Going by that assumption, even if we get 4 TFLOPS of performance out of Switch 2, it'll be substantially behind the Series S, and require dropping res or frame rate by a significant amount, with DLSS needing to fill in the gap.
But we've got some significant advantages over the Series S that reverse this situation, in some cases. That's the next post.
Play vidya while also reading the famiboardsSo
What now
I don't know who you're talking aboutHappy New year to the Most Sane, neutral, and Tech focused thread.
The most straightforward non-techy reason why I never believed in an 8nm is simply because it doesn't match up with the overall "theme" of this console. All the parts that have been procured have been solid "middle of the road" or "above-average" specs. 256gigs of UFS 3.1 which is second only to UFS 4.0. 12gigs of the newer LDRR5X RAM -- smaller than 16gigs, but of a newer type. Probably a high-quality LCD that's better than what the OG Switch got.
Nothing particularly too premium, but nothing garden variety or bland. If anything, with every reveal, people were positively surprised when Nintendo went higher than expected. The decompression hardware, a custom SoC with backported features from Lovelace, the tensor cores, and so-on.
5nm simply lines up with the rest of the console. It's a solid "middle of the road" process that's neither a bleeding-edge 4nm, but neither the outdated 8nm. 8nm is neither solid or middle of the road. It's virtually abandoned because we're in-between Nvidia producing Ada Lovelace/Geforce4000-series cards which are on 5nm and Blackwell/Geforce5000 series which presumably will go bigger (or rather, smaller).
I don't want to delve into the techy reasons because that's been discussed ad nauseam. I'm just saying: all the specs on the Switch 2 feel well "above average". 5nm simply feels like it fits in with the big picture and a 8nm just doesn't.
That's my guess - that Nvidia spent die area on tensor and RT cores, while AMD spent it on more ROPS and Infinity CacheMy understanding with AMD's rasterization advantage as compared to nvidia starting with the 20xx series card is nvidia starting with those cards devoted some of the silicon to tensor cores for DLSS while nvidia did not. is that a fair understanding?
The main disadvantage the Switch 2 will face compared to the Series S is the CPU performance. However, it will have more RAM as well as a more robust upscaling/ray-tracing implementation.Not to console wars butt
How do series s and switch 2 stack up?
Can someone give their best comparison?
Processor: 8-core Custom Zen 2 CPU at 3.6 GHz
GPU: 4 TFLOPS, 20 CUs at 1.565 GHz Custom RDNA 2 GPU
Memory: 10 GB GDDR6 with 8 GB at 224 GB/s and 2 GB at 56 GB/s
Storage: 512 GB or 1 TB Custom NVME SSD
Video: 1440p gaming resolution, up to 120 FPS performance, HDMI 2.1 port, Auto Low Latency Mode, HDMI Variable Refresh Rate, AMD FreeSync
Sound: L-PCM, up to 7.1, Dolby Digital 5.1, DTS 5.1, Dolby TrueHD with Atmos
Ports: 3x USB 3.1 Gen 1 ports, 802.11ac dual band wireless, 802.3 10/100/1000 Ethernet
Design: 6.5 cm x 15.1 cm x 27.5 cm, 4.25 lbs
Features: HDR, all-digital, Quick Resume, DirectX ray tracing
How do the 2 devices compare?
How will more RAM but less CPU translate into porting games?The main disadvantage the Switch 2 will face compared to the Series S is the CPU performance. However, it will have more RAM as well as a more robust upscaling/ray-tracing implementation.
In addition to all this, the final nail in the coffin for me personally was finding out how old the 8nm process actually was. I mean, in terms of nanotech, that thing is practically ancient. Nintendo may not necessarily always be cutting edge, but with every console, they used a fairly recent node, even the dang Wii!
A lot of this we don't exactly know (eg we lack CPU and GPU clocks)Not to console wars butt
How do series s and switch 2 stack up?
Can someone give their best comparison?
Processor: 8-core Custom Zen 2 CPU at 3.6 GHz
GPU: 4 TFLOPS, 20 CUs at 1.565 GHz Custom RDNA 2 GPU
Memory: 10 GB GDDR6 with 8 GB at 224 GB/s and 2 GB at 56 GB/s
Storage: 512 GB or 1 TB Custom NVME SSD
Video: 1440p gaming resolution, up to 120 FPS performance, HDMI 2.1 port, Auto Low Latency Mode, HDMI Variable Refresh Rate, AMD FreeSync
Sound: L-PCM, up to 7.1, Dolby Digital 5.1, DTS 5.1, Dolby TrueHD with Atmos
Ports: 3x USB 3.1 Gen 1 ports, 802.11ac dual band wireless, 802.3 10/100/1000 Ethernet
Design: 6.5 cm x 15.1 cm x 27.5 cm, 4.25 lbs
Features: HDR, all-digital, Quick Resume, DirectX ray tracing
How do the 2 devices compare?
Different games have different limitations so it'd depend I think. For a game that's already giving the PS5/series X/S CPUs trouble, it might get tough to get the game running on switch 2. That's not a ton of games to my knowledge, but it does matterHow will more RAM but less CPU translate into porting games?
They aren't targeting anything. Series S doesn't affect the switch.Of course it does - it means there's been a 4-year period ahead of Switch 2's launch where multiplatform developers have been targeting a baseline that is already in Switch 2's ballpark. That completely changes how business decisions are made from "will paying for engineering efforts to get a PS5/Series X game running on Switch 2 provide a return on investment?" to "we've already spent all this money to fit within Series S, with a little more we can also reach Switch 2 and which will certainly be a larger customer base".
I'm not sure I follow you.They aren't targeting anything. Series S doesn't affect the switch.
I'm not sure I follow you.
I think the argument is "IF it will run on X-box then it will run on switch 2"
Remember all series games are required to Run on both series consoles. Microsoft inadvertently helped Nintendo in this regard.
That's a solid take. I didn't think of this before but If Microsoft was smart then they would leverage gamepass ports to finally find a market in Japan.Check out @Goodtwin's take on that here
I agree with Goodtwin, I suspect going forward, there would be occurrences of this actually being the other way around: Switch 2 would end up being the "base target", then from there the game would be "up-ported" for XSX and PS5 ("side-ported" to XSS). Or they can ignore Switch 2 again at their own peril and risk missing out on making money yet again, even if Switch 2 userbase ends up only being as half big as Switch's was.
Saw this over in the speculation thread. Switch 2 motherboard leaked?
What information can we get from this leak? Famitechies Assemble!!!
Predicting Switch Performance Part 4: What if Big Though?
So, I'm one of the thread pessimists. I generally assume that Nintendo will clock their hardware down for power and heat reasons, giving us a nice, compact experience. But secretly, I've got an outrageous situation I've been modeling. Let's take a look.
Card 3050 3060 3060 Ti 3070 3070 Ti T239/3.5 T239/4 TFLOPS 9.1 12.7 16.2 20.3 21.7 3.5 4 Bandwidth 224 360 448 448 608 120 120 L2 2 3 4 4 4 1 1 Bandwidth/TFLOP 24.6 28.3 27.6 22.0 28.0 34.2 30 Cache/TFLOP 0.21 0.23 0.24 0.19 0.18 0.28 0.25 kilo Cache/Width 8.9 8.3 8.9 8.9 6.5 8.3 8.3
We've got T239, at both 3.5 and 4 TFLOPS, up against the low to mid-range cards in the RTX 30 stack. And something looks off, and if you're a long follower of the thread you'll see what.
Bandwidth/TFLOP is crazy high, even on the 4 TFLOP scenario. And we have an explanation of this - some of that bandwidth needs to serve the CPU, so we need to be over provisioned on bandwidth. And that makes sense, and if you're like me, you turn away from the data and ignore the huge bandwidth situation for a while.
But let's look at that weird metric at the bottom. kilo cache per gigabyte of bandwidth. This is a dumb way of naming the metric, but it's basically how much cache you get for all the bandwidth you've got. And the T239 number looks totally normal.
Except, it shouldn't because some of that bandwidth isn't being used by the GPU. It's being used by the CPU which has it's own cache! T239's cache is unusually beefy for how small the GPU is. And maybe it's just... beefy! Maybe that's it.
But what if it's not? Look at the similarly weird cache/tflop. The number is unusually high. Once again, we see too much cache. We don't know how much bandwidth is used by the CPU, but what if we dialed up the TFLOPS until the cache number made sense? Well, you'd wind up with 5 TFLOPS of performance.
Which is too high! It's stressing the bandwidth out too much. But it does imply that the memory subsystem can handle more performance than we've been estimating. I play primarily handheld, so none of this effects me directly, but if someone suggested 4.3-4.5 TFLOPS, I'd have to admit that the GPU could handle it.
ILikeWaffles64 posted this link over in the speculation thread. Switch 2 motherboard leaked?
What information can we get from this leak? Famitechies Assemble!!!
![]()
I'm seeing BEE printed on thereHoly smokes what a good start to the new year. Hope the big tech heads here have fun diving into it all and siftin through what's visible
I'll let the smart folks here chime in to make sure this is the real deal - but I can immediately see "BEE-CPU-01" in there which was what I was looking for.
Comparing this w/the prototype photos (CMB-CPU-X6) now
BEE is the retail code for Switch 2. Equivalent to "HAC-..." if you have original Switch, or "HEG-.." for OLED, or "HDH-.." for Lite. Look on the back of your Switch, you'll see. The same code would also be printed on the motherboard followed with -CPU-01I'm out of the loop, what does "bee" represent here?
Happy new year! Looks big to me, but Iβll let the experts chime in.We actually might be able to deduce an estimated size of the goddamn chip itself based on this!!!
ILikeWaffles64 posted this link over in the speculation thread. Switch 2 motherboard leaked?
What information can we get from this leak? Famitechies Assemble!!!
![]()
ILikeWaffles64 posted this link over in the speculation thread. Switch 2 motherboard leaked?
What information can we get from this leak? Famitechies Assemble!!!
![]()
This is fully confirmation of 4nm, It simple cant be samsung 8nmI'll let the smart folks here chime in to make sure this is the real deal - I see "BEE-CPU-01" in there which was what I was looking for.
Comparing this w/the prototype photos (CMB-CPU-X6) now
![]()
![]()
![]()
Is letter "G" next to pixelated area saying GML?
For reference, CMB-CPU-X6 prototype photo:
![]()
Would it be possible to fake a motherboard with that code?BEE is the retail code for Switch 2. Equivalent to "HAC-..." if you have original Switch, or "HEG-.." for OLED, or "HDH-.." for Lite. Look on the back of your Switch, you'll see. The same code would also be printed on the motherboard followed with -CPU-01
Happy new year! Looks big to me, but Iβll let the experts chime in.
Still would love to know the hardware βgimmickβ this time around. Nintendo always has something up their sleeve.
NFC reader is on the joy con on the original Switch, most likely same here.Hey is there no Amiibo reader on this?
Is Nintendo phasing out Amiibos?
It would have to be a very elaborate fake - I cannot rule out that possibility.Would it be possible to fake a motherboard with that code?
6500XT is badly hobbled by that 64-bit bus and 4GB memory, so some games tend to perform worse than expected which contributes to a lower than expected average. Also that 16MB Infinity Cache does not help at all.Prediciting Switch 2 performance, part 2: The AMD raster advantage.
Here is a similar graph from before, except now it's for AMD cards. Same benchmark suite, same CPU setup.
Card 6500 XT 6600 6600 XT 6700 XT Average 44.8 82.4 99.2 120 TFLOPS 5.7 8.9 10.6 13.2 FPS/TFLOP 7.859649123 9.258426966 9.358490566 9.090909091
You'll notice a couple things. First off, AMD starts similarly consistent in it's FPS/TFLOP numbers, but totally falls apart at the bottom of the stack. Something about the 6500 XT is wrong and it is vastly less efficient than the other cards in the stack.
However, these performance numbers are much higher than Nvidia's. If you've heard about the AMD raster advantage, there it is. With the exception of the obviously broken 6500 XT, AMD is performing 38% better than Nvidia. This is why you can't compare Series S to Switch 2 just by TFLOPS.
An interesting but open question - does the Series S have the same problem affecting the 6500 XT? In making my performance predictions I assume it does not. Going by that assumption, even if we get 4 TFLOPS of performance out of Switch 2, it'll be substantially behind the Series S, and require dropping res or frame rate by a significant amount, with DLSS needing to fill in the gap.
But we've got some significant advantages over the Series S that reverse this situation, in some cases. That's the next post.
This thingThis is looking like around that original 8nm estimation size from Reddit right? If those DRAM dies are 196mm^2 then this thing i 200mm^2 if not larger
Itβs not even the new year in my time zone yet. This is insane.It would have to be a very elaborate fake - I cannot rule out that possibility.
There have been analysis done here on Fami on the CMB-CPU-X6 prototype photos - there's way too many details included in there that would be obscure knowledge but did get "right".
This BEE-CPU-01 looks pretty legitimate to me right now.
The NFC reader would be on the Joy-Con itself again.Hey is there no Amiibo reader on this?
Is Nintendo phasing out Amiibos?
This would be more elaborate than any other elaborate gaming hoax in history. Its real.It would have to be a very elaborate fake - I cannot rule out that possibility.
There have been analysis done here on Fami on the CMB-CPU-X6 prototype photos - there's way too many details included in there that would be obscure knowledge but did get "right".
This BEE-CPU-01 looks pretty legitimate to me right now.
It does. RT needs a lot of bandwidth too.One theory is that DLSS benefits from extra cache/RAM bandwidth, and that Nintendo might push the memory subsystem extra far because of that.