Question

• Does Common Input Settings support Horizontal single stick use?
• The glyphs doesn’t update is that intended?

Right out of the box, the Common Input Base Controller Data does not initially support Horizontal single stick use in the Common Input Settings.

Solution

I was able to figure a way to support Single horizontal, Dual JoyCon & ProController environments using Common Input Settings.

1. Setting the right configurations within the Project Settings:

   • Navigate to Project Settings > Platforms.
   • Enable the option to enable single stick controllers and use horizontal single sticks.

2. Create Left and Right JoyCon folders:

   • Inside the Engine\\Platforms directory, create two new folders: LeftJoyCon and RightJoyCon.
   • By default, there's already a "Switch" folder in this directory.

3. Set up the Configuration File:

   • Within each new folder, create a Config subfolder.
   • Copy the Switch's DataDrivenPlatformInfo.ini file into each Config folder.

4. Modify Configuration File:

   • In the copied .ini files, update the PlatformName and DeviceProfileName to be Switch_Left_JoyCon and Switch_Right_JoyCon respectively.

5. Set Up Common Input Settings:

   • This allows for differentiation between Switch, SwitchLeftJoyCon, and SwitchRightJoyCon controllers inside the Common Input Settings.

     

   • Under Common Input Base Controller data, ensure the Gamepad Name dropdown includes options for "Switch", "SwitchLeftJoyCon", or "SwitchRightJoyCon".

     

6. Configure Gamepad Hardware ID Mapping:

   • Ensure the Common Input Base Controller Data has the correct Gamepad Hardware ID mapping set up for all three Controller Datas.

     

7. Create Custom Logic for a Force Refresh Current Input Method :

   • I am using the function called void RefreshCurrentInputMethod that lives inside CommonInputSubsystem.cpp*.* Since that function is private, I had to create my own function called ForceRefreshCurrentInputMethod to force update the current input method since I needed call it inside the function:

     void UCommonUIActionRouterBase::ApplyUIInputConfig()
     

     This is how I can guarantee whenever a JoyCon gets calibrated, it will refresh the current input method.

8. Implement Custom Controller Selection Logic for the Nintendo Switch JoyCon:

   FName UCommonInputPlatformSettings::GetBestGamepadNameForHardware(FName CurrentGamepadName, FName InputDeviceName, const FString& HardwareDeviceIdentifier)
   

   • Inside FName UCommonInputPlatformSettings::GetBestGamepadNameForHardware() we want to implement our custom logic to detect which Controller Data is best for our current setting and have it return the correct FName. By Default it will always call "Switch" which is why we had to set up the Config files.
   • The function I created checks if the CurrentGamepadName is one of the three JoyCon data controllers, then selects the best JoyCon type (left or right) based on the HardwareDeviceIdentifier. Finally, it assigns the selected JoyCon type to be used for the gamepad input mapping which then returns the correct FName.

By following these steps, I enable support for Single horizontal, Dual JoyCon & ProController environments using Common Input Settings on the Switch platform!