cathery / sys-con Goto Github PK

Hello! First of all, you are fantastic! Thanks for your effort to bring us a wonderful modification!
I have a Xbox 360 controller, wireless edition, and when put together with the USB cable "Charge And Play" doesn't work.
The Switch don't recognize it.
I tested it in 0.2.2 and 0.2.3 Version.

Thanks for all!

There is a typo in the Xbox One config with the X and Y swap ex. "key_FACE_LEFT = FACE_UPUP".

Gets noticed (with the little controller plugged in icon) but no inputs work

I tried the sys module and reeboted the console. It didnt work. I have a regular xbox one controller and i pluged it to my switch in handheld mode. Im on ams 9.0.1

You should create a remap utility, I know you are making a config app.
Will it have this feature?

Is it possible to get this working on a third part Xbox 360 dongle?

Vendor:045e Product:0291

The applet screetnshot can be found by checking AnthonyTorres58's post in the thread below
#11

I tested it with the current build, and it did nothing seemed to work.

hey

first of all thank you for the hard work
your the best

second question is i got issue with SpeedLink Torid controller
the switch didn't recognized him
its a connection with a USB Bluetooth (its working on my pc and ps3)
the question if it can work on the switch with sys-con?

i installed the new version of sys-con 0.4.1

thank you master

I am specifically talking about this adapter: https://rukminim1.flixcart.com/image/416/416/gaming-adapter/charging-kit/e/b/v/b-v-g-xbox-360-play-charge-kit-original-imaehayfxr6ggr9w.jpeg?q=70

Its plugged into the top of the Xbox 360 wireless controller.

I just tested it and it does not work yet. LEDs just keep blinking.

Thank you!

I am probably completel wrong but can't you use the library that TX now provides, surprisingly, to add direct usb support (no dock)
Or analayse their library to see how it works?
;)

https://sx.xecuter.com/download/libusbfs.zip

• Switch: 8.1.0
• Atmosphere: 0.9.4
• sys-con: 0.2.3

One of my xbox 360 controllers gives off this error.
The gamepad in question was always recognised as a original 360 controller by both xbox consoles and pcs but I always tought it was an really good clone.

Anyway I checked the logs and the error is:
Error creating interface for product 654 with error 369
A bit criptic to me but maybe it can help. Also, it seems that after the error retries and fails again.
Here it is the full log:
Steps for this log:

1. Delete previous log.
2. Unplug working 360 controller
3. Plug working 360 controller
4. Plug non working 360 controller
5. Wait a while
6. Unplug non working 360 controller

Anything I can do to help let me know.

log.txt

I've tried every USB port on the dock. No input is accepted, the LED in the middle just blinks.

It's an 'Afterglow for Xbox 360 PL-3702'.

I saw you had a diagnostic applet, so I ran that in case it helps:

Thanks!

Edit: Logs attached:
log.txt

I saw on the last update of the SX that they added the flags modules, I wonder if we can use Sys-Con with the SX-OS ?

PS: @cathery you are too strong.

does not recognize the controls of the Xbox 360 with charge and play kit

PS3 Controller not working with Atmosphere 0.9.4 | on 5.1.0 , nothing append ,only endless flash on controller.

I have this in the log.txt:

2019-10-11 00:00:00: File check succeeded! Loading configs...

2019-10-11 00:00:00: Failed to read from xbox orig config!

2019-10-11 00:00:00: Failed to read from xbox one config!

2019-10-11 00:00:00: Failed to read from xbox 360 config!

2019-10-11 00:00:00: File check succeeded! Loading configs...

2019-10-11 00:00:00:

New sysmodule session started on version 0.4.2

2019-10-11 00:00:00: Successfully created event for Dualshock 3

2019-10-11 00:00:00: Successfully created catch-all event

2019-10-11 00:00:00: Catch-all event went off

2019-10-11 00:00:00: Dualshock 3 event went off

2019-10-11 00:00:00: Catch-all event went off

2019-10-11 00:00:00: Dualshock 3 event went off

The name of the NSP in sdmc:/atmosphere/titles/690000000000000D is sys-con.nsp when it should be exefs.nsp. This is why 0.2.3 doesn't work (#17). I'd recommend you release 0.2.3.1 so that people are notified about the fix.

Is this feasible?

luigis mansion always seems to move luigi around on ds3 controllers.

Hi, version 0.2.2 work with my xbox one controllers, version 0.2.3 does not work any more.
It only vibrates once, then nothing happens.

Hello.

Thanks for that file.

Can you make a file for Reinx? Or is it loadable from Renx?

Thanks.

If this happens you, the only way to resolve it right now is to completely reboot your switch.

The reason this is happening is due to a resource exhaustion error (0xCE01) from usbHsEpPostBuffer in the Input thread of any controller. I don't know what's causing it, considering i make sure to free up any allocated resources. I could reproduce this issue by plugging and unplugging any controller multiple times until the app runs out of memory. The last error received before unplugging the final controller is 0x25A8C. The memory issue persists even when the app is closed and re-opened. Perhaps it is due to the destructor forcefully ending the eventWait in epPostBuffer?

I was trying to use a multitude of different controllers while my switch was docked, and tried plugging in my 8bitdo adapter so i could use my ds4 controller, and it didn't work. I cleared the mod files off of my sd card and the adapter started working again. Is this an issue with the fact that there isn't any ds4 support yet? or is it an issue with the different pieces of hardware not being able to work at the same time.

the new receiver (the slim one) isn't recognized at all, how i can help you to resolve the issue?

tks for the this plugin
it can work fine with my TXOS, until about 10 to 20min later the system reports a crash then automatically close my running xci game, with no time for me to even make a save.
it's devastating, I tried twice and still get the same result
hoped to get some advise here
tks again

This isn't a priority for me personally, but thought it might be useful to someone else. May as well be added eventually.

These are cheap DS3 controllers not manufactured by Sony.

i assume wired xbox one controllers are different from wireless ones that you use with a micro usb cable, as when i go to plug in my controller, its little light never lights up and its buttons do nothing.

I know the sys-module itself is functional, as using a dualshock 3 over usb works as intended.

if it helps any, i think the ids for my controller are VID_24C6 and PID_543A

Still there with the newest update

I can't seem to correctly identify and acquire dualshock 3 interfaces on the switch. When queried with the filter of idVendor = 0x54C, availableInterfaces will give you 0 results, allInterfaces will give you 1 result, and acquiredInterfaces will give you 0 results. Sometimes an event will pop off with an available dualshock 3 interface, but trying to acquire it will result in an error. Perhaps it is being blacklisted in a HidGamepad json file in the usb-sysmodule?

If you know how to solve this issue, or have anything to add, please let me know.

Works well with D-pad control, but in games like SSBU, the analog stick emulations doesn`t work.
Is the any option to config?

As title, if I plug the Slim controller the Switch crash, the Duke doesn't make the console crash.
Both of them works on OG Xbox.

As title, when I press B it's like pressing every button, even L-R who are not physically available on the controller
On the OG Xbox the controller works fine

If not on SX OS, does it need funding or isnt it possible?

Is there any setup needed? I connect my Xbox 1 controller to the dock with USB and it vibrates once, then nothing happens. Controller doesn't work and no controller is detected.

in luigis mansion the controllee deadzone appears to be too tiny somehow resulting in luigi walking slighty to the left

Latest version 0.2.3 hotfix. FW 9.0.1, Atmos 0.9.4 vanilla. Tried this several times so I'm pretty sure it's not just random thing.

Edit: Seems like something like this happens while console is turned off in dock and controller is plugged into it. Just now PS3 has been turned on by itself and player indicator on controller is lit (like someone pressed PS button to turn on console)

Edit 2: Nvm, I'm a dum-dum, forgot that this is default behavior for DS3 that is paired with a console. Haven't connected DS3 to anything but PS3 since I've bought PS4. Tho would be nice if this behavior could be circumvented somehow.

I don't know if it's technically possible, but it would be great to have compatibility with the official Xbox 360 dongle for PC. Right now it lights up but the controller isn't recognized.

i have a xbox 360 controller (gamestop) and tried connecting on the dock with the modules you released, but it doesn't work, tried rebooting and make sure that files are in the right place, nothing, also tried nacoon controller, doesn't work too

Is there any way to recognize an USB controller e.g. xbox 360 as gamecube controller to use the analog trigger?
The game GRID does support the gamecube controller to use the analog trigger to brake and accelerate. It would be nice to configure each controller as what they should be recognized.

i don't have a dualshock 4

1. HUGE thanks for your effort with this project.

2. My console is at ver 8.0.1. I'm trying to lend another joystick for testing.

Title say it all

After I put the sysmodule onto my card and rebooted, my system began to hang on the Switch splash screen. Need some help? There isn't an error code or hard crash, either.

Doesn't work for me I'm using an xbox one s controller , i already renamed the nsp to exefs after doing this when i plug the USB cable the console recognized that a usb controller was plugged but the controller just vibrates and nothing happened no button press is detected , my console is running 9.0.1 and atmosphere 0.9.4

Would this work? In fact, could dedicated wireless adapters for other controllers work as well like the steam controller's adapter?

As of right now, the AbstractedPad implementation lacks complete input functionality.

In the SwitchAbstractedPadHandler::UpdateAbstractedState function, if m_state was passed with m_state.state.buttons that has a value of 0x19 or more, the state of the abstracted pad freezes indefinitely. if m_state.state.buttons has a value of 0x2000 or more, it triggers an InterfaceChangeEvent, essentially locking any connected controllers from being properly disconnected.
This issue only arises when the function was called from a separate thread, everything would work as intended if the main thread was used.

If you know how to solve this issue, or have anything to add, please let me know.

I don't know why, but my Switch immediately connect with Dualshock 3 but just the home button works, nothing more.

tried to use it and it does not work. however ds3 controller worled flawlessy, cant wait for rumble!

The controller does connect, and tries register properly; although it will disconnect every so often, and no inputs will register (Except L and R for some reason)

On latest Atmosphere, AMS 9.0.1 and 0.4 sys-con

Xbox 360 wired controller no vibrations

I'm attempting to build this from source to test a custom device. I have devkitpro set up and I can build all the examples. However when I attempt to build this project is throws some dependency errors.
Any help would be appreciated.

make -f MakefileSysmodule

output is attached.
output.txt