• Hey everyone, staff have documented a list of banned content and subject matter that we feel are not consistent with site values, and don't make sense to host discussion of on Famiboards. This list (and the relevant reasoning per item) is viewable here.
  • Do you have audio editing experience and want to help out with the Famiboards Discussion Club Podcast? If so, we're looking for help and would love to have you on the team! Just let us know in the Podcast Thread if you are interested!

StarTopic Future Nintendo Hardware & Technology Speculation & Discussion |ST| (Read the staff posts before commenting!)

Is the first time non-Nintendo job postings for Nintendo hardware specifically have been identified and speculated over? Usually third-party involvement speculation comes from patents, sales orders, etc. The closest would be LinkedIn stuff, but that was all for SoC development in particular, not Nintendo's hardware per se.
as far as I know yea

There is another job listing by eSol. They are hiring cloud engineers for a next generation game console.
I wonder how much is for testing hypotheticals. I always assumed Nintendo would just partner with Nvidia. that would be an amazing get for GeForce Now

EDIT: the translation makes it sound like analytics
 
as far as I know yea


I wonder how much is for testing hypotheticals. I always assumed Nintendo would just partner with Nvidia. that would be an amazing get for GeForce Now

EDIT: the translation makes it sound like analytics
"cloud" is a very generic term that can mean a lot of different things. Whatever they're talking about here is likely completely uninteresting.
 
as far as I know yea

I wonder how much is for testing hypotheticals. I always assumed Nintendo would just partner with Nvidia. that would be an amazing get for GeForce Now

EDIT: the translation makes it sound like analytics
Yeah, it doesn't say anything about cloud gaming. My first thought was that it could be outsourcing for NSO/online infrastructure, but after reading the machine translation, it sounds more like implementing and collating analytics from the online infrastructure that already exists, with a particular mention of a system that "proposes services suitable for each user" -- which could mean either internal business analysis for what kind of services to provide, and/or recommender systems for marketing to the users.
 
So basically we have a 3 month renewable contract job related to OS support, including post-release support for a new unannounced game platform for a console maker in Kyoto.

It's obviously for Nintendo. It doesn't really say anything conclusive about launch timing, but putting out a 3 month contract job for a product that (supposedly) isn't coming for like, 18 months, and specifically mentioning post-release support as a duty/responsibility seems extremely odd.
donthurtme-baby.gif
 
One interesting thing from the job posting is that it potentially gives a bit of an insight on Nintendo's security around the new hardware:

This is a long-term dispatch job, renewable for 3 months. Work 2 to 3 days a week, other days can be handled remotely. Security is important to us, so when you come to work, you will work in a dedicated security room in the client's Osaka office. When working from home, you will work on a dedicated PC loaned to you by the client.

This is translated via DeepL, so all the usual translation caveats apply. Assuming "client" here means Nintendo (ie eSol's client, not eSol themselves, as a client of the recruitment agency), this states that the employee would have to spend 2 to 3 days a week working in a "dedicated security room" in Nintendo's Osaka office. This would mean that eSol, a company Nintendo has had a relatively long relationship with and who are presumably providing key components of [redacted]'s OS like they did for the Switch, isn't allowed to have [redacted] dev kits. In this particular case it appears that dev hardware isn't allowed to leave Nintendo's offices, and with a dedicated security room it would suggest that even Nintendo's Osaka employees may not be allowed access.
 
One interesting thing from the job posting is that it potentially gives a bit of an insight on Nintendo's security around the new hardware:

This is translated via DeepL, so all the usual translation caveats apply. Assuming "client" here means Nintendo (ie eSol's client, not eSol themselves, as a client of the recruitment agency), this states that the employee would have to spend 2 to 3 days a week working in a "dedicated security room" in Nintendo's Osaka office. This would mean that eSol, a company Nintendo has had a relatively long relationship with and who are presumably providing key components of [redacted]'s OS like they did for the Switch, isn't allowed to have [redacted] dev kits. In this particular case it appears that dev hardware isn't allowed to leave Nintendo's offices, and with a dedicated security room it would suggest that even Nintendo's Osaka employees may not be allowed access.
I would draw a distinction between devkits (in common usage) and the kind of development hardware which is likely to be kept in security rooms. The former are sent out to partners at various points in early development, and eventually more and more third-party developers and such. Security room development hardware is something less productized and polished than a devkit, the kind of thing anyone could potentially plug a USB cord into and mess with all the internal stuff. Also, given the nature of this job, source code security is also possibly the primary concern.
 
One interesting thing from the job posting is that it potentially gives a bit of an insight on Nintendo's security around the new hardware:



This is translated via DeepL, so all the usual translation caveats apply. Assuming "client" here means Nintendo (ie eSol's client, not eSol themselves, as a client of the recruitment agency), this states that the employee would have to spend 2 to 3 days a week working in a "dedicated security room" in Nintendo's Osaka office. This would mean that eSol, a company Nintendo has had a relatively long relationship with and who are presumably providing key components of [redacted]'s OS like they did for the Switch, isn't allowed to have [redacted] dev kits. In this particular case it appears that dev hardware isn't allowed to leave Nintendo's offices, and with a dedicated security room it would suggest that even Nintendo's Osaka employees may not be allowed access.
That's almost normal for pre-reveal console stuff. Mario series' director wasn't allowed see Wii U until after its reveal.
 
That would ve a hell of a way to explain the thin H2 coupled with confirmed Gamescom presence hahaha. But I think it's safer to think that perhaps Ninty will show-off the console to partners behind doors at Gamescom.

That's what I'm guessing as well. Would line up with a 2024 release. Optimistically could even mean a late spring 2024 release, but there's no way they plan to only give Devs 3 months with revised dev kits before launch.

I know that sort of thing happened at E3, but isn't Gamescom more public facing?
Well with E3 no longer existing that would explain why they suddenly would want to attend Gamescom.
 
That's what I'm guessing as well. Would line up with a 2024 release. Optimistically could even mean a late spring 2024 release, but there's no way they plan to only give Devs 3 months with revised dev kits before launch.


Well with E3 no longer existing that would explain why they suddenly would want to attend Gamescom.
Oooor... Gamescom, which is primarily consumer focussed, would be putting finalised consoles in consumers' hands as a preview? Nintendo has PLENTY of channels to advertise and distribute to developers...
 
I don't think DLSS changes things in any meaningful way. I agree that we don't have good information about the absolute performance of DLSS on a GPU this small, but what I'm talking about here is relative performance.
First off, this is deeply in the weeds, this is all hypothetical, edge-case stuff I'm mostly interested for technical reasons. The question of "1080p screen or not" is a lot about preference on the consumers end, and design goals on Nintendo's in. I'm not arguing for a "correct" answer.

But, second, the DLSS curves have never made sense to me, and I wanna wave this flag again. We know the curves go weird at the extreme ends, and we're talking about a device sitting well past the extreme end of the documented numbers. So understanding why the curves go all wonky is useful for predicting what the device is capable of.

The data in the DLSS programming guide is useful for integrators, but I think it's less useful for us. The clue is in the RTX 2080 (laptop) numbers. They skew wildly out of sync with the rest. The obvious answer to why - well, it's running on a laptop, different CPU/RAM set up etcetera. Which, unfortunately, means we can't trust that Nvidia took any more care in ensuring the base system for the rest of the numbers is identical.

Which means we can't really compare these numbers across cards to see how DLSS would behave at different levels of GPU power. But we can compare intra-card, and we see a pretty clear linear relationship with output resolution, which, yay! That's what we would expect. Solid.

However, the "curves" don't intersect the Y axis at 0. Not super surprising. The algorithm might be O(n) on paper, but all software has some overhead. And that's what I'm (in this overwritten way) trying to get at. On paper, the overhead seems to scale with TFLOPS, but we also know Nvidia didn't use a consistent base system, so it could easily be explained away by the CPU getting better and better across the various test systems, or memory size/bandwidth increasing in cards as performance does.

If this overhead is GPU bound, and scales with TFLOPS, then in handheld mode we should expect overhead to be a larger chunk of frametime, leaving less time for upscaling. This matches my initial, naive number crunching, where DLSS tends to fall apart at the bottom of the curve.

If this overhead is CPU bound, then we're in great shape, because we're not expecting CPU to change between modes. This would explain models that expect DLSS to be much much slower in TV mode than handheld mode - not because those models were correct, but because they were skewed by a non-constant overhead that wasn't properly accounted for.

If this overhead is bound by memory in some way, then it's a little up in the air what will happen, as it's unclear if Nintendo would choose to change the memory clock between the two modes for battery life purposes.

It's impossible to create "perfect scaling" between handheld and TV modes, there will always be games that prefer one environment over the other. Just scaling the GPU and screen tends to favor handheld mode slightly. More elaborate power saving strategies (altering storage or memory bandwidth) tends to favor TV mode. This isn't just true for DLSS, it's true for software as a whole. But DLSS remains a less-well-understood factor in the whole scheme.

Side note: this also potentially shows an area where Nvidia really could tune DLSS for the Switch.

Also, while I understand where you're coming from in terms of PS4 ports, I don't think that's going to factor into Nintendo's thinking in any meaningful way. This device, like the Switch, will be designed primarily around the needs and/or desires of Nintendo's internal development teams.
Yeah, I've stated in the past that I expect a 1080p screen, and personally would love a 1080p screen if the performance in handheld mode is right. Where I bristle is the idea that this is a clear win in IQ regardless of perf, which it isn't.

I understand the decision, and that for many players a 1080p screen for Nintendo games with bad image quality for 3rd party games is the preferred compromise. Where I get admittedly tetchy is being told by those players that the compromise doesn't exist.

They will of course take third party feedback into account, and will be happy to accommodate third parties where possible, but "this system should display low-effort PS4 ports in portable mode in the most faithful way possible" will be about a thousand rungs down on the priority list compared to "this system should make the new Mario and Zelda look as good as possible".
I see what you're getting at, but I think you're misstating what I'm trying to say. My assertion is "as much as possible games should look equally good in both docked and handheld play, without significant extra work." The PS4 port example is just to demonstrate how a 1080p screen on a 1.3 TFLOPS device would fail that test. The industry has coalesced around a rough performance standard for "1080p content" which is built around PBR rendering, the last gen consoles, and 2018-2019 graphics cards. There is a reason that the Steam Deck also does not have a 1080p screen.

In docked mode, you can run your existing 1080p content, and it will look great, because 1080p content scales perfectly on a 4k screen and REDACTED has more than enough power for the industry's de-facto 1080p standard. You can take that extra power, use it to run DLSS, and now you have a 4k upscaled image. And if you have next gen content, you can target sub-1080p and upscale to 1080p, which again will at least integer scale on the 4k screen.

In 1080p handheld, you don't have enough power to run your 1080p content, so you need to make image sacrifices, possibly running 720p and getting scaling artifacts. You can bump that down to 540p and use DLSS to get back to where you started, resolution and settings wise. And if you have a miracle port, you're using something like ultra-performance mode DLSS, or starting from a base resolution sub 540p and scaling up to 720p, adding scaling artifacts on top.

The only games which would benefit from such an arrangement are games which are bespoke to the console and can afford to really dial in the two modes almost as separate projects (Nintendo games) and games which don't push the graphics sufficiently hard to have trouble running at native res in handheld mode. This upsets both the engineer and the gamer in me.

That doesn't mean it's a wrong decision for Nintendo, or that there won't be players who prefer it - I think there is a decent chunk of folks who would love a higher res game UI even if the visuals were slightly muddier. It also wouldn't be the first time Nintendo made a decision about a handheld screen that made backward compatible games look like ass :)

But I'll take the backwards compat shittiness! I'll take the 1080p screen! Just... don't do it for the marketing number, give me the performance that comes along with it.
 
Honestly if I were Ninty and I had a console that could feasibly make it for holiday 2023. I don't know that I wouldn't plan for March-May 2024 (and announce in Jan/Feb) just to get those sweet switch 1 final holiday sales. I'd go further to say even if I had say Mario kart 9 near-ready, I'd resell an enhanced MK8 port and then have MK9 be a 2024 holiday title. Maybe that's short sighed of me, but if I just want to maximise revenue in the short term, why not?
knowing Nintendo they will problaby release a definitive version of Mario Kart 8, with all DLC for Switch sucessor, Mario Kart 8 Deluxe definitive Edition releasing on Nintendo Switch sucessor around launch year.
 
0
To some degree, it depends on what you mean by "hardware announcement". If you strictly mean the trailer where the hardware itself gets announced, then that will probably be a Switch 2 only affair where everyone involved knows what's going on, but I'm also expecting that to be similar to the Switch 1, where the reveal is a standalone trailer focused entirely on the hardware with little game focus and very little third party involvement in general. The actual meat of the presentation where games are talked about would only happen a week or two later, and could feasibly just be a normal Direct.

Now with that said, I'll definitely entertain the idea that Nintendo would split up the announcements and do an "extra" 4th general Direct entirely focused on games that will run natively on the new hardware, but I don't really see much benefit in doing it after Pikmin specifically, as that game is likely to feature, albeit briefly. This is sort of what I was mentioned in the Direct thread as a "Direct sandwich" where they first do a normal Switch 1 summer Direct, then do the hardware announcement, then do a second, entirely Switch 2 Direct.
Nintendo will problaby tease they next hardware on social media, hiting tune in day X/Y for the reveal or more informations of the future of Nintendo Switch or something similar to this.
 
It's obviously for Nintendo. It doesn't really say anything conclusive about launch timing, but putting out a 3 month contract job for a product that (supposedly) isn't coming for like, 18 months, and specifically mentioning post-release support as a duty/responsibility seems extremely odd.
The first customers of this will be Nintendo's internal teams, and then 3rd parties with devkits that aren't cobbled together out of spare parts. Any one of these could qualify as a "release."

And it's worth noting that on other jobs eSOL lists 3 months as the trial period. This may be a standard window for the initial contract that has nothing to do with expected project length.

Yeah, it doesn't say anything about cloud gaming. My first thought was that it could be outsourcing for NSO/online infrastructure, but after reading the machine translation, it sounds more like implementing and collating analytics from the online infrastructure that already exists, with a particular mention of a system that "proposes services suitable for each user" -- which could mean either internal business analysis for what kind of services to provide, and/or recommender systems for marketing to the users.
it's not definitive, obviously, but I'd bet dollars to donuts it's the eShop.

Since we're going down the rabbit hole, eSOL began developing this Cloud Team For Game Consoles over a year ago. AI Translation incoming
You will be involved in the development of software systems associated with the use of cloud environments related to next-generation game consoles... There is an increasing demand for cloud-based collaboration between customer products and systems. However, we do not have much knowledge about cloud environment construction, so we are looking for human resources who will be the core of our future business development.

It seems eSOL has a dedicated "Nintendo" unit which I wasn't aware of. They're developing both sides of the system, here is a (closed) job posting for an embedded OS engineer to develop the systems to ship data from the console to the cloud, with an expectation of long-term support across the system's life time. However, this doesn't mean it was for REDACTED, exclusively

We are looking for a project manager who can work with our team members to design and implement improvements and functional additions to existing game consoles for the development of next-generation consoles.
Again, if I am assuming eShop, it would really be handy for Nintendo to already have the recommendation engine fully seeded before launch.


Hidden content is only available for registered users. Sharing it outside of Famiboards is subject to moderation.
 
re: job postings.

Looks like eSOL has a dedicated team for Nintendo. They began expanding that team last year both with a cloud team and an additional engineer to support the OS side of that cloud project. They've also hired at least one engineer for that team which at least has a partial mandate to support Nintendo's work, but also some projects where the game work might benefit other parts of their business, or open the console support team to new, non-Nintendo clients.

eSOL's standard job descriptions are built around a 3 month trial period. It's not clear to me if the job posting that set this off is in anyway short term, or if that's just how the contract is laid out.

In other words, it's entirely possible the position is just a backfill, and/or that the contract is long term but it's set up to mirror the 3 month trial period of employees.

The cloud position is actually the most interesting to me, because we know that the cloud team didn't exist last year, and the position for the team manager closed in April 2022. Sometime early last year, Nintendo pushed for something that needed tighter integration between the cloud and the OS, and eSOL needed to support both ends of the stack, not just the client, so eSOL had to expand.

We have vanishingly little info on the nature of that project save this:
You will be involved in the development of software and systems associated with the use of cloud environments related to next-generation gaming devices... Specifically, the system will absorb game playing patterns from all over the world, analyze big data, and propose services suitable for each user.
And that the team -
1 manager, 4 members
*We plan to increase the number of members in the future.
I have no idea if this product would be needed for launch, or how large it is, but this screams "beginning of multi-year development"
 
In 1080p handheld, you don't have enough power to run your 1080p content, so you need to make image sacrifices, possibly running 720p and getting scaling artifacts. You can bump that down to 540p and use DLSS to get back to where you started, resolution and settings wise. And if you have a miracle port, you're using something like ultra-performance mode DLSS, or starting from a base resolution sub 540p and scaling up to 720p, adding scaling artifacts on top.

The only games which would benefit from such an arrangement are games which are bespoke to the console and can afford to really dial in the two modes almost as separate projects (Nintendo games) and games which don't push the graphics sufficiently hard to have trouble running at native res in handheld mode. This upsets both the engineer and the gamer in me.
If the worst case scenario is that PS4 ports absolutely can do no more than 720p and not everyone bothers with DLSS, scaling artifacts to 1080p should still be pretty minimal. Cheap scaling tech like FSR1 sucks much less than what Switch does, and all artifacts simply become smaller as a part of the whole as overall resolution increases. If for whatever reason they used a 3500x1968 screen, that would make for an awful uneven scale from 720p by the numbers (x2.734 in both directions), but it's high enough resolution it would still not be very noticeable.
 
So Grubb is hearing something from Nintendo in July…

Switch Lite was announced July 10, 2019.
Switch OLED was announced July 6, 2021. ~2 years later.
Switch 2 [fill in the blank]…

🙂

edit: those were the wednesday and tuesday of July’s second week. ergo, Switch 2 announcement will be July 11-12. 😉
backstreet-boys.gif
 
If the worst case scenario is that PS4 ports absolutely can do no more than 720p and not everyone bothers with DLSS, scaling artifacts to 1080p should still be pretty minimal. Cheap scaling tech like FSR1 sucks much less than what Switch does, and all artifacts simply become smaller as a part of the whole as overall resolution increases. If for whatever reason they used a 3500x1968 screen, that would make for an awful uneven scale from 720p by the numbers (x2.734 in both directions), but it's high enough resolution it would still not be very noticeable.
I find non-integer scaling artifacts really obvious, but yes, the density potentially obviates the problem.
 
0
The first customers of this will be Nintendo's internal teams, and then 3rd parties with devkits that aren't cobbled together out of spare parts. Any one of these could qualify as a "release."

And it's worth noting that on other jobs eSOL lists 3 months as the trial period. This may be a standard window for the initial contract that has nothing to do with expected project length.
I haven't seen a full translation of the job listing yet but unless we have the full context the idea that Nintendo is their first customer may not exactly be relevant to the "post-release defect" part depending on what exactly they're referring to the release of.

Basically, what I mean is we need more context and an accurate translation before we can really figure out what product it's referring to releasing.
 
Idk, but I don’t think this could be for something soon… but long-term throughout the span of the system.

so not really indicative of when this thing is releasing.
 
0
Interesting that the job starts in July. That’s actually exactly when I’m expecting news about distribution of NS2 dev kits to come out. (Going off the same info timing from MZ with Switch)
 
Interesting developments tend to occur when I’m traveling, so I missed the initial excitement of the new job postings. Thanks to @Kysen, @oldpuck, and a few others’ excellent Nancy Drewing, it seems highly plausible that the open positions are for eSOL’s Nintendo products. Based on my own translation (assisted by machine translation) here are some observations:
  • The anonymous job post (not the ones directly associated with eSOL) was posted by a staffing agency. Therefore, it is a “dispatch” job (派遣) to the client site (eSOL Osaka office).
  • Unfortunately, it indicates that the renewable 3-month contract most likely does not hint at the release window of this “next gen console”. It is just a standard dispatch duration.
  • The job title is “Programmer, Control and Embedded Systems”. Looking at the job responsibilities, however, the position is more akin to what we call a “Sales Engineer” in the US.
  • The “post release defect handling” machine translation isn’t quite accurate. I’d translate that to “post release bug reports”. Note that it most likely refers to the release (from eSOL to Nintendo) of each software revision, not the release of the customer’s hardware product (Nintendo’s console or devkit).
  • What’s intriguing to me is the thinly veiled “Kyoto game company” reference in the subject line. If this job post was pre-approved by eSOL, I wonder why they were bold enough to be this public about it—are they expecting an announcement from the customer in the near future?
  • Or, it could simply be a blunder by the staffing agency, revealing more information than they should have.
Edit: clarity
 
  • Or, it could simply be a blunder by the staffing agency, revealing more information than they should have.
I chose this because my feeble heart can’t take another disappointment, if I get another one I will evaporate into thin air and become one with the PSP3; nonexistent
fade-away-oooooooooooo.gif
 
.
Interesting developments tend to occur when I’m traveling, so I missed the initial excitement of the new job postings. Thanks to @Kysen, @oldpuck, and a few others’ excellent Nancy Drewing, it seems highly plausible that the open positions are for eSOL’s Nintendo products. Based on my own translation (assisted by machine translation) here are some observations:
  • The anonymous job post (not the ones directly associated with eSOL) was posted by a staffing agency. Therefore, it is a “dispatch” job (派遣) to the client site (eSOL Osaka office).
  • Unfortunately, it indicates that the renewable 3-month contract most likely does not hint at the release window of this “next gen console”. It is just a standard dispatch duration.
  • The job title is “Programmer, Control and Embedded Systems”. Looking at the job responsibilities, however, the position is more akin to what we call a “Sales Engineer” in the US.
  • The “post release defect handling” machine translation isn’t quite accurate. I’d translate that to “post release bug reports”. Note that it most likely refers to the release (from eSOL to Nintendo) of each software revision, not the release of the customer’s hardware product (Nintendo’s console or devkit).
  • What’s intriguing to me is the thinly veiled “Kyoto game company” reference in the subject line. If this job post was pre-approved by eSOL, I wonder why they were bold enough to be this public about it—are they expecting an announcement from the customer in the near future?
  • Or, it could simply be a blunder by the staffing agency, revealing more information than they should have.
Edit: clarity

THINLY

VEILED

!!!

My hope remains ablaze.
 
my new vibe is that it's either getting revealed sometime next year or literally next fucking week
At present my hope is based in:

Nintendo never, EVER skips E3 season unless there is a literal global catastrophe to stop them.

They appear intent on revealing and discussing upcoming Nintendo Switch games with abandon.

Ergo, the coming E3 season presentation is for something other than Switch games.

June? July? Who knows. But there's more than one person talking about them holding a digital event of some sort, and even the insiders, usually good about Direct dates, seem divided as to whether this is a non-Direct event or Direct.

Plus an earlier claim from someone in this thread ( Z0m3le I believe ) that insiders are aware of the new system but hesitant to talk about it due to being burned with Switch Pro rumours before, and most are waiting for one to break the news before the rest come out to back them up.

I know it's less than meaningless, but Digital Foundry Direct has had a weird vibe around it lately, like they don't really want to talk about the next Switch outside of whispers and opinions and scratching heads and chins.
 
I think if there’s anything we can be sure of is that the new hardware will release, at the latest, Holiday 2024. Receiving something from eSOL would make that a deliverable. I know the standard staffing time is for three months and they can always renew, but if Nintendo is comfortable with a 90 day contract that can be renewed if necessary… it must be a deliverable they need in the short term rather than the lobg term
 
Initial devkits were in 2015 though. Later in 2015, as per MZ.
Yeah the original article from WSJ per MZ about dev kits being sent out was published 504 days before the Switch's launch. Assuming a NS2 launch date of Nov 22, 2024 (basically the latest WW release date or earliest NA launch AND no delay to Q1 2025), 504 days before then would put us at July 7, 2023. Oh and I'm assuming we even get a similar article at all.

I don't think things will line up exactly the same this time around, but I think 16 months before launch (about ~1.5 years) sounds about right for sending dev kits out.
 
I think if there’s anything we can be sure of is that the new hardware will release, at the latest, Holiday 2024. Receiving something from eSOL would make that a deliverable. I know the standard staffing time is for three months and they can always renew, but if Nintendo is comfortable with a 90 day contract that can be renewed if necessary… it must be a deliverable they need in the short term rather than the lobg term

Hiring contractors for, as I understand it, delivering patches and support for embedded software, presumably the new controllers... Well. To me that sounds like something you do way at the end. When the software is already finished, and the hardware for it too, and now you want a support team to keep the ball rolling. Definitely sounds late game to me.
 
Hiring contractors for, as I understand it, delivering patches and support for embedded software, presumably the new controllers... Well. To me that sounds like something you do way at the end. When the software is already finished, and the hardware for it too, and now you want a support team to keep the ball rolling. Definitely sounds late game to me.
even you can surely admit that such a conclusion hinges on heavy conjecture though
 
Yeah the original article from WSJ per MZ about dev kits being sent out was published 504 days before the Switch's launch. Assuming a NS2 launch date of Nov 22, 2024 (basically the latest WW release date or earliest NA launch AND no delay to Q1 2025), 504 days before then would put us at July 7, 2023. Oh and I'm assuming we even get a similar article at all.

I don't think things will line up exactly the same this time around, but I think 16 months before launch (about ~1.5 years) sounds about right for sending dev kits out.
We've bad articles about Dev kits being sent out for the new Switch for literal years... We're well PAST our 500 days.
 
even you can surely admit that such a conclusion hinges on heavy conjecture though
As I understand it, it appears to be such and such a way, yeah.

Now as with everything else. In isolation this wouldn't mean much, but given Funcle rumblings and "digital event" discussions, etc., we appear to be approaching curious levels of smoke for something without fire. (I realise this turn of phrase at present may mean something else, but I'm of course speaking metaphorically here.)
 
As I understand it, it appears to be such and such a way, yeah.

Now as with everything else. In isolation this wouldn't mean much, but given Funcle rumblings and "digital event" discussions, etc., we appear to be approaching curious levels of smoke for something without fire. (I realise this turn of phrase at present may mean something else, but I'm of course speaking metaphorically here.)
cumulative perception tends to amplify a lot of negligible evidence though. it's confirmation bias

  • digital event hair splitting is probably just a reaction to the partner showcase blowback. all they know is that there will be something; the lack of knowledge does not imply it being something radically different
  • funcle rumblings are totally unverifiable
  • this job listing could just as well be irrelevant to timing
 
cumulative perception tends to amplify a lot of negligible evidence though. it's confirmation bias

  • digital event hair splitting is probably just a reaction to the partner showcase blowback. all they know is that there will be something; the lack of knowledge does not imply it being something radically different
  • funcle rumblings are totally unverifiable
  • this job listing could just as well be irrelevant to timing
Since when were leaks expected to be "verifiable" beyond whether they come true or not? I don't trust Funcles any less or more than any other 'insider' type. Is the Wall Street Journal more reliable than random forum posters? Sure. But about Nintendo hardware? Well, we'll see.

A Partner Showcase IS a Direct. If they know it's a Direct I'd expect they'd say Direct. Seems like an odd thing for them to split hairs about, no?

This job listing is clearly for Nintendo contracting embedded systems support. Timing relevant? Maybe not. Relevant? Yes. As fwd-bwd said, if things were tight lipped they wouldn't be so blasé mentioning the sector and location, thus revealing the company and purpose. Why are things a little less under lock and key? Maybe because its reveal is imminent?

That's far from the only smoke of course. We have rumours started on this very thread, we have Microsoft's documents about the [REDACTED] console going so far as to name features, we have system updates with things Nintendo Switch 1 can't or doesn't use.

It's not confirmation bias to point to things and say "these seem connected, could this mean?". I also would not consider the evidence negligible in the slightest. I am not a lawyer, but this isn't a legal case. As console leaks go, this stuff is well evidenced.

And that's all before we mention the Nvidia leak with a taped out processor a year ago! Chips don't exactly rot sitting on shelves but they don't appreciate in value either. Something has to give.
 
As hyped as I am for there to potentially be an announcement soon, I'm just glad that this thread is showing a pulse again LOL. I need something to do while I'm at work and don't feel like working on pet projects.
 
We've bad articles about Dev kits being sent out for the new Switch for literal years... We're well PAST our 500 days.
True, but the last we got from Mochizuki or any other reputable outlet like WSJ/BB was back in Sep 2021. Also, that article for the NX back in Oct 2015 revealed more than just the fact that dev kits were being sent out. People still didn't know the exact form of the hardware at the time, but dev kits getting sent out en masse gave more confidence to analysts on the idea that a launch would come next year in 2016. We don't have to get another article exactly like that, but if we start hearing more rumblings about further finalized kits reaching devs, then we would also be safe to assume a late 2024 launch.

We are also currently in a window where a game in development for Drake could leak out, ala DQ11 via Horii from SE or another source. Beyond that, again assuming a Nov 2024 launch, reports on parts orders and whatnot should come around October this year or by December at the latest. Even further after that and we approach Eurogamer's NX bombshell in 2024.

These are just guidelines I'm throwing out there though for when things might come out or happen, not real expectations.
 
True, but the last we got from Mochizuki or any other reputable outlet like WSJ/BB was back in Sep 2021. Also, that article for the NX back in Oct 2015 revealed more than just the fact that dev kits were being sent out. People still didn't know the exact form of the hardware at the time, but dev kits getting sent out en masse gave more confidence to analysts on the idea that a launch would come next year in 2016. We don't have to get another article exactly like that, but if we start hearing more rumblings about further finalized kits reaching devs, then we would also be safe to assume a late 2024 launch.

We are also currently in a window where a game in development for Drake could leak out, ala DQ11 via Horii from SE or another source. Beyond that, again assuming a Nov 2024 launch, reports on parts orders and whatnot should come around October this year or by December at the latest. Even further after that and we approach Eurogamer's NX bombshell in 2024.

These are just guidelines I'm throwing out there though for when things might come out or happen, not real expectations.
Why on earth would we assume a November 2024 launch...
 
Please read this staff post before posting.

Furthermore, according to this follow-up post, all off-topic chat will be moderated.
Last edited:


Back
Top Bottom