Gamexplain Explains the Joy-Con Desyncing Problem

Good to know this is an issue, but it's not going to stop me from getting a NS or playing with a split controller setup. I hope Nintendo gets this fixed, but it's not a deal breaker. These kinds of problems happen with hardware these days. If people found the resolve to deal with the crazy Xbox 360 RRoD, then this is nothing. Bring on the NS, Nintendo.
 
Right, but the post asked for a situation in which you would put your hand in front of the joycon. The reason doesn't really matter if it would block the bluetooth (which this might not for all we know).

One of the bigger possible reasons is obstruction from line of sight of the switch console itself. Unless your switch is to the side, I don't expect that utilization to have any effect.
 
You play arms by completely gripping the joycon in your hands. Depending on the size of your hands, they'll be like 95-100% covered.
Don't you hold the joycons with the rail pointing down? If so the antenna is probably not being covered. I am guessing they just lowered the Bluetooth power usage and some controllers have worse Bluetooth chips then others. Everyone can reproduce GameXplain but on some units you have to be 10ft away and others are having it happen very close.
 
The rail is pointing towards from the TV in ARMS, and you're covering it with your fingers, which may be less of a nuisance to the signal than the meat of your hand.
 
Well that sucks.

Like some others have guessed, I'm assuming this is because the controllers aren't leaving low power mode when pulled from the controllers are detached from the system. Has anyone tried restarting the system outside the dock with the joycons detached? Wondering if that would change anything potentially.
 
You play arms by completely gripping the joycon in your hands. Depending on the size of your hands, they'll be like 95-100% covered.
Would you notice the connection issue in that game though? Maybe it's just the sticks that are affected? Or maybe you don't need to have total control 100% of the time in ARMS?

Anyhow, it's really bad, I won't cancel my preorder but I'm preparing myself to eventually buy two joycon+.
 
Distance has already been confirmed as one of the major factors from what I've seen. People posting the issue starts anywhere from 8-13 feet away. I assume it's setup dependent as well. Closer than that appears to be fine.

That's good to hear. I won't be farther than 5-6 feet from the Switch at any time.
 
Would you notice the connection issue in that game though? Maybe it's just the sticks that are affected? Or maybe you don't need to have total control 100% of the time in ARMS?

Anyhow, it's really bad, I won't cancel my preorder but I'm preparing myself to eventually buy two joycon+.

There's no reason why the sticks would be affected but other functions wouldn't be.
 
Right, but the post asked for a situation in which you would put your hand in front of the joycon. The reason doesn't really matter if it would block the bluetooth (which this might not for all we know).

his hand isn't covering the front of it in your pic as he does in the video. i just can't think of any situation where you would go out of your way to block it as he did in the video
 
They had a ton of journalists demoing Milk at the preview events right? And based off the Twitter videos from Jeff Gerstmann, the setup had them a decent distance from the system IIRC.

Strange that this issue never came up there.
How would they know if it had the issue? It doesn't completely disconnect or anything, just makes it intermittent. Nobody knew how to judge if the game was correctly reflecting their milking motions correctly. (Not saying the issue happened but it would be very hard to detect vs link running weird or not being able to turn in Mario Kart, I mean you aren't even looking at the screen in 1-2 switch)
 
Does this mean any sort of golf or bowling game is out the window since hands could get in the way? That seems quite problematic.
 
As long as I can do this

cl8GKbj.jpg

I am good.
 
Maybe it can't be fixed with a software update and maybe they'll use the don't-hold-it-that-way defense or say that we should sit closer to the TV/console?

I'm pretty sure Nintendo is going to fix this. No one should worry about that. Whether it's hardware or software, they'll get it taken care of. They (and us) might just say "don't hold it like that" in the meantime...or use another controller. Unfortunately, my be something that can't be corrected with a software update, which means they'll have to send out hardware and that will take time. Shouldn't stop someone from playing the games in the meantime.
 
People have been playing the switch for weeks now in public and this issue just came to light today. I willing to bet it's not as serious as it's being described.


It does occur to me, the Switch has been in public settings, developer hands, and QA testing for weeks if not months, as well as the Treehouse and various NOA testers/employees. It's unfeasible to me this hasn't been noticed by someone.

So it leads me to believe it's one of two things:

1. A bug in the pre-release OS. Something to do with the BT mode of the joycons, as mentioned by other posters.

2. A completely defective batch of joy cons, a defect that wasn't in previous batches.


It strikes me as a little odd that the defect seems to be in every single press unit. So is it just that batch of press units that have an issue, or is it in every unit set for release next week.

I'm hoping, and inclined to believe, it could be some kind of software bug. It would have pretty disastrous results for Nintendo if every launch joy con had to be recalled or fixed. It's just completely dampens the excitement for launch hardware knowing a part of it is literally defective. It would be bad PR too. I, for one, would be upset because I own a bunch of stock in Nintendo and know they need a smooth and successful launch.

I hope they say something about it tomorrow.
 
People have been playing the switch for weeks now in public and this issue just came to light today. I willing to bet it's not as serious as it's being described.

If this is due to a controller or console firmware issue or bug, this wouldn't have come to light until the retail units released.

The best we can hope for is that this is a known issue and is fixable with a software update.
 
If this is due to a controller or console firmware issue or bug, this wouldn't have come to light until the retail units released.

The best we can hope for is that this is a known issue and is fixable with a software update.

If it is a firmware issue, it could already be fixed since it's likely the units on display are more up to date than the ones shipped to retail due to manufacturing time.
 
I dont remember xb1 or ps4 or pro launching with any serious hardware troubles,
there was some hdmi issue with the ps4 or the bad rubber on the s-ticks i think but not nearly widespread enough to even be deemed a serious problem.

half your controller constantly dying is a way bigger issue. whats worrisome is that so many people faced this among the already few that got to test it out

Some launch xb1 units chewed up disks and had to be replaced - was quite widespread I think?
 
Yeah how do you explain ARMS? People were playing it with the joycons and pretty much covering the whole joycons up.

My experience with Arms was that the game was sorta button-mashy and if you told me my inputs cut out for a second or two, I would totally believe it. You make these big, long punches and you're sorta committed to them, so if something cut out in that game you might just think your timing was off. It's not like Zelda, where you would clearly see Link stop walking or something.
 
What the heck? That seems utterly inexcusable. Why on Earth are these controllers somehow worse at connecting than the Wiimotes? I can see this being an issue for a lot of people, and I really would have thought it would have been caught in QA. Jeesh.
 
I wonder how big an issue this is going to be.
My sympathies go out to anyone working retail next month. Parents aren't going to have the patience that hardcore gamers will when their kids are complaining that their new $300 game console isn't reading controller signals properly. They're also not likely to have Pro controllers on hand to mitigate it.

Japan will barely notice as they'll be predominantly using their Switches in handheld mode regardless.
 
It absolutely will work. It's like 2 feet of distance, the hysteria about this is really getting ridiculous.

Oh I am sure I will be able to. And I agree, this hysteria is ridiculous.

Edit: Everything is getting magnified and exaggerated more and more as we get closer, but I really do think Nintendo has this.
 
Posted this on another thread about this issue, based on a video I saw that applies more science to this issue:

Saw this video suggesting a possible cause of this:

https://www.youtube.com/watch?v=nJBAp33tnNE

Basic Summary:

- This issue can reliably be triggered by covering the Joy-Con with your hand

Possible explanation:

- Humans are mostly water
- Water absorbs radio waves
- Bluetooth is based on radio waves
- Nintendo is likely using a weak Bluetooth signal to boost battery life.

Depending on how this is set up, they may or may not be able to boost the power of the bluetooth signal via a firmware update.
 
Posted this on another thread about this issue, based on a video I saw that applies more science to this issue:
Boosting the output power through a firmware update could likely require re-certification unless they already certified it with a higher output power. It seems strange that they would lock the chip into a low power mode though, as most modern chipsets offer dynamic power control even for Class 2 devices where it is technically not required. This means that lowering the output power actually doesn't save you much power (though people often assume it does) because the device will only increase the power when needed. I will say though, that there is absolutely no reason why a Bluetooth device should require line-of-sight when you are indoors and within a few meters of the other unit.
 
I remember the iPhone 4s antenna issue sounding familiar to this. If you held the phone a certain way your hands blocked the phones signal. They later rectified this with free cases for every user. People hoping for a software fix for this are delusional. The only way I can think it could be fixed is if the Bluetooth signal is outputting a weak signal to favour battery life and that could somehow be addressed.
 
Hopefully it is just a dialled down wireless strength issue that can be rectified by an update.

This won't be an issue for me as 90% of my game playing will be in handheld mode, but it's not a good thing with regards to negative PR it will create at launch.
 
I wonder if this "replication" of the issue is actually the same thing as the issue at hand. The reason I wonder is that, in order to replicate it, he has to completely cover the controller (probably around where the bluetooth chip is specifically). Nobody would be naturally doing that in the way he had to for the issue to show up. People are just playing games and it's happening. Why? I don't feel like this answered that.
 
Watching the full gameXplain video now, I'm realizing two things:

1) This is a terrible problem that should have been resolved in testing.
2) This probably isn't going to affect how I play the Switch at all.
 
I'm trying to figure out if this is an oversight or a technical limitation like being the proper distance from the Kinect in order for it to read you or where you place the IR sensor from the Wii.
 
Top Bottom