[Controller Request]: Flydigi APEX and Flydigi Apex 2

[blackver]

Controller Name

Flydigi APEX

Current Controller Behaviour

Controller is not successful in pairing with the console

Controller vendor and product ID

No response

Supported Features

• [X] Rumble/Vibration
• [X] Motion Controls
• [ ] Player Number Indicator
• [X] Battery Level Reporting

Input Report Format

No response

Additional Details

the official website link to the product : https://www.flydigi.com/en/apex/

[ndeadly]

The website for this controller mentions a 2.5G receiver. Is actually possible to connect it to other devices without that? Assuming you have done everything else correctly, a controller that doesn't pair with the console at all usually means the hardware isn't compatible/supported.

[blackver]

the controller can use Bluetooth to connect with other devices. Using button B + Pair to activate the bluetooth pairing.

[ndeadly]

And you activate this pairing mode at the Change Grip/Order screen and nothing happens? Or do you see a pairing notification of some kind?

[blackver]

yes, nothing happens on Change Grip/Order screen. maybe I can try it again when i am at home today, last time I tried on V2. I will try on my OLED this time. So basically the Mission Control can capture almost all bluetooth controllers?

[ndeadly]

So basically the Mission Control can capture almost all bluetooth controllers?

Yes, even if support for a controller hasn't been explicitly added to mission control for mapping buttons, any compatible bluetooth controller should still pair successfully. If it doesn't, likely explanations are:

• Incorrect pairing procedure. Eg. wrong pairing mode, user on the wrong menu etc.
• The controller advertises a device class other than on of several supported HID device types and is rejected by checks introduced on more recent firmwares.
• The controller uses bluetooth legacy pincode pairing, and uses a pincode other than the default 0000.
• Incompatible hardware. This can be a cheap out-of-spec bluetooth chipset, a bluetooth LE controller, or one that doesn't support bluetooth at all.

We can potentially get some more information via logging some of the pairing events, but best to rule out the obvious things first. In my experience the logs contain little information of value in most cases.

[blackver]

for points number 1 and 3 I can re-check it today. for point 2, how can I check it?

[ndeadly]

for points number 1 and 3 I can re-check it today. for point 2, how can I check it?

Either through logging (needs a debug build of mission control) or looking at device class properties when connected to a PC. Alternately, you could try pairing on a pre-12.0.0 firmware before the device class checks were added.

[blackver]

sorry I don't have pre-12.0.0 firmware switch cfw. so i will check it when connected to PC,.

[ghost]

This joystick uses bluetooth LE technology, but if you connect the 2.4G wireless adapter, you can use it natively on the Switch.

[ndeadly]

That makes sense, thanks for the clarification. You mean to say it emulates a Switch controller via the USB adapter? Or do you need sys-con running?

[ghost]

Just connect the USB adapter, if it doesn't work, activate sys-con.

[ndeadly]

Well, it's either one or the other. I imagine sys-con is necessary since the product page makes no mention of Switch support. This is not what I would refer to as being able to use "natively"

[ghost]

Although the manufacturer's page says it doesn't work mine works with the UBS adapter without needing any homebrew controller and recognized as Xbox controller.

[blackver]

Hi Elson, i tried using USB adapter without sys-con and the gamepad (Flydigi Apex) not detected. Next week i will try it using sys-con because right now my switch don't have Mission Control installed yet and still away from home.

[blackver]

Also, are you using Flydigi Apex or Apex 2?

[ghost]

Apex 2!

[ndeadly]

recognized as Xbox controller

Not sure what you mean by that, as the Switch has no concept of controller types outside of the officially supported ones. If something looks like an Xbox controller to the console it certainly won't be sending the correct packet format...

i tried using USB adapter without sys-con and the gamepad (Flydigi Apex) not detected.

@blackver I am still somewhat skeptical this can work natively, but make sure you have Pro Controller Wired Communication enabled in the system settings in any case.

[blackver]

tested using the usb wireless receiver : not detected with or without mission control tested android mode : not detected with or without mission control tested bluetooth mode : not detected with or without mission control Controller : Flydigi APEX

[ndeadly]

@blackver this is to be expected if @Elson-creator is correct about the controllers using Bluetooth LE. You will need to wait until I have finished implementing LE support before this controller can be used via Bluetooth. Mission Control also doesn't support USB currently so you shouldn't expect it to work with the adapter either. You might have some luck with sys-con for USB connections via the wireless adapter.

[blackver]

i see.. i will wait for the Bluetooth LE implementation then. Thank you.

[ndeadly]

No problem. I will follow up in this thread when it's ready in order to correctly recognise and map this controller.

[teguhsatria892]

apex 2 support with sys con using USB adapter, but I need Bluetooth connection, I wont plug and unplug my adapter from my PC to switch