I think PS5 didn’t, but Series X (and by extension the unrevealed S at the time) was alluded to being taped out in August.
Yeah, production leaks are probably the most likely to happen. IIRC we got a leak of the Lite's casing in April 2019, for a September 2019 release. For Drake I'm guessing October or November, so maybe we'll see production leaks starting in May/June.
Yes, the closest Alps part publicly available is the RKJXY. It doesn't support the center push, however, and has a different ribbon cable and two different screw mounts. The Joy-Con stick is probably a custom design based upon the RKJXY. It does seem curious that the Alps patent uses drawings looking like the Switch part.
As far as I can tell, there's no new "gimmick" in this patent filing. It is to improve the user experience, but not adding anything new.
That assumes there’s a drastic difference in the housing, which I doubt.
I can say that eliminating drift count as a new gimmick for me
Just a drift fix. As if that isn't amazing by itself.
Everything point out to Intel foundry having few wpm(Wafers per month) capability. They need to expand before being able to serve themselves + others. But given Intel Foundry Services aren't supposed to be online before 2025, there's still time.
Ehh, I wouldn't take that as suggestion it's for a new hardware. SQEnix has tight lipped Horii since the NX blunder. And honestly, DQ XII missing Switch userbase on Japan would be a disaster. It's probably a PS4/5/Switch/Drake game.
Small correction, Orin uses 8.7 and Drake 8.8.
Square Enix might end up leaning on a "cloud version for Switch, real version for Drake" model for some future games. For better or worse, what they did with the Kingdom Hearts Integrum Masterpiece collection on the Switch could be a sign of things to come.
There's also AV1 encode support, which Orin supports, but not consumer Ampere GPUs.
I don't think so since I believe that roadmap was strictly for datacentre GPU architectures, not a combination of datacentre and consumer GPU architectures. And kopite7kimi was explicitly referring to the MCM variant of Hopper when talking about Hopper being delayed, which wasn't announced yesterday.
Okay, so the Ampere Next in that roadmap would have been Hopper, then?
Nah, they're not going to do a cloud version for the main SKU. Switch will be a 30 million+ diverse userbase in Japan by the time DQ XII launches. I expect Switch to be the base SKU with enhancements for Switch Next.
When considering the existing GameCube / Wii emulated releases (Sunshine, Galaxy, Skyward Sword), I would prefer more enhanced ports for future titles, then they can earn back the cost of porting to the original Switch and Drake.
Personally I'd prefer emulation because then we'll get way more games.
Fingers crossed for no borders! #DrakeExclusive
This business model has been proposed quite a few times in this thread. While technically feasible, the marketing of such a game may be more difficult than some would think. Explaining the differences between these two versions to the average consumers would be a headache. Pricing them would be another puzzle.
Thank goodness I'm an Erista owner.
Agreed. To make the cloud/native hybrid a viable business model for Switch developers, it may need to be an NSO feature so that the devs are paying one landlord instead of two (Nintendo + cloud provider); that would reduce the administrative overhead too. Nintendo might require any cloud games hosted on NSO to offer a native version, to prevent (lazy?) devs only release PC cloud games on the Switch.
There's no way it is. DLSS uses specialized hardware, FSR is a software solution. It's just a good stop gap solution while they wait for the next console.
But is it? And what's a ton of extra research? Asking Nvidia to hook up the existing DLSS code to their new system's GPU whose architecture already supports it? As big new features go DLSS is a natural, almost inevitable one when you're using a current generation Tegra. Nintendo didn't spend some huge amount of time and money on this.
I think that depends on the performance penalty (or rather, relative performance benefit) that each one gives. I can see FSR 2.0 extending the current Switch's lifespan, but DLSS has the added benefit of offloading the process to the Tensor cores along with RT to make the successor more appealing as a full 4k console.
Ah, thanks for clarifying!
My bad. I can still see Tensor cores being used for other forms of simulation calculations, perhaps things like sound for instance or water physics.
In general I agree with you that they probably didn't dump a ton of resources into getting DLSS on their next console, but do keep in mind that to get it working to an acceptable level on a handheld device with a strict power budget probably wasn't particularly easy. Getting DLSS and Raytracing into a 10-15 watt portable system is almost unfathomable, and it's why the new device has me so excited, to see how they pulled this off (presumably, I guess they could still remove it, but that seems unlikely).
Well I don't know if we have a release window for the Open-Source version of it (Although doesn't discount the idea that Nintendo could ask for use of it ahead of time due to their status)
I think that depends on how early Nintendo got access to FSR 2.0, especially with FSR 1.0 using spatial data, and FSR 2.0 using temporal data. I presume not initially with Nintendo Switch Sports and Xenoblade Chronicles 3. But there's definitely a possibility of patches coming after release that could add FSR 2.0 support for Nintendo Switch Sports and Xenoblade Chronicles 3. And I presume probably not for Xenoblade Chronicles 2.
Yeah, the addition of temporal data might mean them having to do a bit more work and they'd probably miss the shipping date by then.
Well, Mario Kart 8 Deluxe has a huge number of sales since launch. In fact, as of February 2022, Mario Kart 8 Deluxe is the top selling Nintendo game on the Nintendo Switch with 43.35 million sales. So I don't think Mario Kart 8 Deluxe getting DLC is necessarily a strange decision when taking sales numbers into account.
Theoretically yes
RTXGI is vastly more performant, it has less latency, and is visually more convincing. I would only use Lumen if I had no other choice.
