Xbox 360 wireless controller freeze randomly

[simplementeUnPorito]

Information

Atmosphere version: 1.8.0.

Switch OS version: 19.0.1.

Sys-con version: 1.5.4.

Controllers:

•Official Xbox 360 wireless controller (with original USB PC receiver).

•Redragon Harrow G808.

•Unofficial Xbox 360 controller.

Description

While using an Xbox 360 wireless controller on my Switch through sys-con, everything works fine at first. However, after a while, the controller appears to "freeze" — the character continues performing the last input (e.g., keeps walking forward) even though I'm not pressing anything. This behavior lasts for about 2–5 seconds and then returns to normal.

This issue also happens with my Redragon Harrow G808 and another unofficial Xbox 360 controller, so it doesn’t seem to be device-specific.

I’m attaching my log files and configuration as well: sys-con.zip.

Note: The last controller disconnection shown in the logs is because I connected the Switch to my PC to extract the files.

Let me know if you need additional information or testing. Thanks!

[o0Zz]

Could you try with v1.5.2 to see if you reproduce the problem ?
I introduced an optimization in v1.5.3 that seems to introduce some regressions, so I wondering if your issue is not a side effect of this optimization.
Thanks.

[simplementeUnPorito]

Hi man! First of all, thanks again for replying so quickly — I really appreciate it.

I just tested it with v1.5.2 as you suggested, and unfortunately the issue actually aggravated quite a lot. I couldn’t even move in the menu due to severe input lag.

Then I tried using only the Xbox 360 controller (with no other controllers connected), and it seemed to work just fine — no noticeable issues.

But as soon as I connect my Redragon controller, I get massive input lag again — the controls become almost unusable.
This happens both when I use the Redragon alone, and when I use both controllers together.

That said, there's actually a bit of improvement: I was able to play with my little sister using just the Xbox 360 controller, and didn’t experience those strange freezing moments anymore — so that’s definitely a step forward!

I’d really love to be able to use both controllers together, since that’s the only way I can play with my whole family.

Let me know if there's anything else you'd like me to test - I'll be happy to do it as soon as I get back from uni. Thanks again!

[o0Zz]

The input lag you described in your last comment seems caused by the log level, could you confirm what is your log_level on your last test for the v1.5.2 ?

The log_level should be 3

log_level=3

Could you retry the v1.5.2 and make sure log_level=3 in order to have a "normal" input lag. (You need to reboot the switch when you change the log_level)

---

Another test to consider, if you come back to the v1.5.4, Could you try to play with "polling_thread_priority". On the last version it's 30, maybe you could try 40 ?

[simplementeUnPorito]

Hi again! Sorry for not replying yesterday - I had some stuff to take care of.

Well, just now my sister and I played through a full circuit on Mario Kart, and it worked perfectly!

Something in my gut told me to set the log level to 5, so I did - and even though I accidentally updated to the latest version, everything worked! We were able to use both controllers at the same time without any issues.

Also, I noticed the thread priority was set to 43 at that moment. I don't know why it was set to that number.

I'm now gonna try lowers numbers to see if there is any difference.

Anyway, thanks so much for your help and for your awesome work!

[o0Zz]

OK great, however is that possible to know what is your exact working setup please ?

Version	Thread priority	Comment
v1.5.2	43	OK: Works with multiple controller
v1.5.4	30	NOK: Random freeze with multiple controllers
v1.5.4	30	NOK: Works with only 1 controller
v1.5.4	43	???
v1.5.4	36	???

Could you let me know if this table is correct or not ?
And if you could just make some test in order to find the lower working thread priority for you with the latest version ?

[simplementeUnPorito]

Hi! Sure, here’s my current setup and what I tested so far:

Version	Thread Priority	Result	Comments
v1.5.2	Unknown (default)	✅ OK (with 1 controller)	Massive input lag with 2 controllers
v1.5.4	Unknown	❌ Freeze with 2 controllers	Not sure what the priority was
v1.5.4	43	✅ OK with 2 controllers	Smooth, no freezing
v1.5.4	41	✅ OK with 2 controllers	Slight improvement in input lag

When I experienced the freezes, I hadn’t yet set the thread priority manually, so I don’t know what value it was using at that point.

Right now, I’m on v1.5.4 with:

thread_priority = 41

log = 5

This combo works great with both controllers. I didn’t notice further input lag improvements when going lower than 41. Soon I will try it with 4 controllers and tell you about it.

Let me know if you'd like me to test any specific values! Happy to help.

[o0Zz]

@simplementeUnPorito thank you for your tests, @Breadn11 it look like the thread_priority = 30 we set to solve this issue #70 is now a bit too high and cause some side effects to other users like simplementeUnPorito.

Is that possible for you two to try different thread priority in order to find the one that match perfectly your needs:
The idea is to find a good compromise between input lag and freeze when we have multiple controllers

What we currently know:

Version	Thread Priority	Result for simplementeUnPorito	Result for Breadn11
v1.5.4	30	❌ Freeze with 2 controllers	Works perfectly
v1.5.4	36	??	??
v1.5.4	38	??	??
v1.5.4	41	✅ OK with 2 controllers (Slight improvement in input lag)	??
v1.5.4	43	✅ OK with 2 controllers (Smooth, no freezing)	??
v1.5.4	48	We don't know we we don't care	Big input lag

Thank you for your help on this

[o0Zz]

@simplementeUnPorito @Breadn11 Would either of you be able to test different priority values to determine the best trade-off between freeze and latency? If not, I’ll just set the default to 41 at random.