[rcore] Gamepad not working on macOS

[NitroPlum]

Please, before submitting a new issue verify and check:

• I tested it on latest raylib version from master branch
• I checked there is no similar issue already reported
• I checked the documentation on the wiki
• My code has no errors or misuse of raylib

Issue description

Gamepad input not working. I tried 2 different controllers.

• Xbox One Series X connected via USB
  • IsGamepadAvailable(0) returns false.
• Nintendo Switch Pro Controller connected via USB
  • IsGamepadAvailable(0) returns true.
  • No button input is ever detected

Environment

MacOSX Ventura on an M2 Mac.

Issue Screenshot

Can't really show this.

Code Example

#include "raylib.h"
#include <stdio.h>

int main(void)
{
    const int screenWidth = 800;
    const int screenHeight = 450;

    InitWindow(screenWidth, screenHeight, "Gamepads Broken");

    SetTargetFPS(60);               

    while (!WindowShouldClose()) 
    {
        BeginDrawing();

            ClearBackground(RAYWHITE);

            if(IsGamepadAvailable(0)) {
                DrawText("FOUND GAMEPAD TEST", 190, 275, 20, PURPLE);
                
                if(IsGamepadButtonDown(0, GAMEPAD_BUTTON_RIGHT_FACE_DOWN)) {
                    DrawText("BUTTON PRESSED", 190, 350, 20, PURPLE);
                }
            }

        EndDrawing();
    }
    CloseWindow();        

    return 0;
}

Provide minimal reproduction code to test the issue. Please, format the code properly and try to keep it as simple as possible, just focusing on the experienced issue.

@NitroPlum GLFW or SDL?

Either way:

1. Regarding Nintendo Switch Pro Controller, it's on the mappings list (L950-L951) for Mac OS X.
   No button input being detected could be a binding issue.

2. Regarding Xbox One Series X, couldn't find it on the mappings list and neither on the SDL_GameControllerDB.
   Probably why it's not being detected.

Edits: 1. added more information; 2. updated info, formatting.

[NitroPlum]

After GLFW, I also tried the SDL backend. Is there a way for me to fix the binding issue locally @ubkp ?

[NitroPlum]

Oh, another bit of info that may help. I did try in the browser examples on the Raylib site and both controllers work there.

After GLFW, I also tried the SDL backend. Is there a way for me to fix the binding issue locally @ubkp ?

@NitroPlum Sure, create your own binds (you may want to take a look at SDL_GameControllerDB) and add it to your local src/external/glfw/src/mappings.h file.

Oh, another bit of info that may help. I did try in the browser examples on the Raylib site and both controllers work there.

AFAIK, the web browser gamepad API is a completely different thing (ref1, ref2).

Edit 1: AFAIK sometimes firmware updates end up changing the device GUID, which causes it to no longer match the DB. I could be wrong, but I think that happened to some Xbox controllers.

Edit 2: Apparently you can even use Steam's Big Picture mode to generate binds these days (ref).

[SoloByte]

I have similar problems. I am using the c# bindings of raylib on MacOSX 14.2.1 Sonoma and gamepad input is no longer working. Raylib detects the connected gamepads but does not trigger any button/ trigger/ axis functions.

I have tested Xbox Elite Controller 2 & Xbox Series X Controller.

• I can connect them fine to my mac
• The input works with the raylib example in the browsers
• The input works with a gamepad test online
• Both gamepads work on windows with various games
• I have used the exact same setup before (in october I think) and everything has worked fine.

At same point it just stopped working for me....

The example I am using to test this all out works fine on windows (the gamepad is detected & the input is detected)

I think the only thing I did was update the firmware on my elite controller but the other controller I did not update...

I have tried to use custom bindings and bindings from SDL_GameControllerDB with the SetGamepadMappings function but it did not change anything.

[raysan5]

@SoloByte Thanks for reporting. Could you try with raylib latest master branch version?

raylib 5.0 (November 2023) implemented a big redesign for desktop platforms and despite everything was carefully tested, some things could not work as expected.

I don't have a macOS, neither those mentioned gamepads, I need help to fix this issue.

[SoloByte]

@raysan5
I have just tested it on my MacBook with raylib cs 6.0.0. (I can only test raylib cs) I have used 3 xbox one controllers (elite series2, new-ish xbox one, old xbox one).

All three are detected by my MacBook, all three work on windows, all three work with a gamepad tester. I have tested them with the raylib input gamepad example and they are detected and the input works (even when more than 1 is connected) but it seems that the triggers are not detected at all (Left/Right Trigger). The joystick axis work fine.

I have tested it with my simple raylib cs gamepad tester project and the controllers are detected but no input is registered.

• Raylib.IsGamepadAvailable(0) returns true (also for 2nd, 3rd connected gamepad)
• Raylib.IsGamepadButtonDown(0, GamepadButton.RightFaceDown) always returns false
• Raylib.GetGamepadButtonPressed() > 0 always returns false

It would be helpful if someone could test this on a Mac with raylib, because I can only test it with raylib C# bindings.

I will post my simple project here. It is possible that I am doing something wrong or missing a step.

//Using Raylib Cs 6.0.0 (Released 20 January 2024)
using Raylib_cs;


namespace GamepadCs
{
    public static class Program
    {
        public static int Main(string[] args)
        {
            //Init
            Raylib.InitWindow(800, 800, "Raylib cs Gamepad Test");
            Raylib.InitAudioDevice();
            Raylib.ClearWindowState(ConfigFlags.VSyncHint);
            Raylib.SetTargetFPS(60);

            var defaultFont = Raylib.GetFontDefault();
            
            //Gameloop
            while (!Raylib.WindowShouldClose())
            {
                Raylib.BeginDrawing();

                //Gamepad connected
                if (Raylib.IsGamepadAvailable(0))
                {
                    
                    //Xbox A button down
                    if (Raylib.IsGamepadButtonDown(0, GamepadButton.RightFaceDown))
                    {
                        Raylib.ClearBackground(Color.Green);
                    }
                    //any gamepad button pressed
                    else if (Raylib.GetGamepadButtonPressed() > 0)
                    {
                        Raylib.ClearBackground(Color.Yellow);
                    }
                    else //no gamepad button pressed
                    {
                        
                        //Left Mouse Button or Space is held down
                        if (Raylib.IsMouseButtonDown(MouseButton.Left) || Raylib.IsKeyDown(KeyboardKey.Space))
                        {
                            Raylib.ClearBackground(Color.Blue);
                        }
                        
                        //nothing pressed 
                        else
                        {
                            Raylib.ClearBackground(Color.DarkGray);
                        }
                    }
                }
                
                // no gamepad connected
                else 
                {

                    //Left Mouse Button or Space is held down
                    if (Raylib.IsMouseButtonDown(MouseButton.Left) || Raylib.IsKeyDown(KeyboardKey.Space))
                    {
                        Raylib.ClearBackground(Color.Purple);
                    }
                    
                    //nothing pressed 
                    else 
                    {
                        Raylib.ClearBackground(Color.Black);
                    }
                }
                
                Raylib.EndDrawing();
            }
            
            
            //End
            Raylib.CloseAudioDevice();
            Raylib.CloseWindow();
            return 0;
        }
    }
}

[JupiterRider]

@SoloByte
Your Raylib-cs example works fine on Linux.

I also cannot find any platform specific macos code in raylib. Maybe a newer version of GFLW will fix this.

[raysan5]

It seems this issue is specific to a binding, I'm afraid I'm closing it for raylib C side.

[konsumer]

I have a similar issue with plain C, on mac M1 (Sonoma.) On web, it works fine, but with this code, I only get the name, but no button-events, on native raylib 5.5:

#include "raylib.h"

int main(void) {
  InitWindow(320, 240, "gamepad test");
  SetTargetFPS(60);

  while (!WindowShouldClose()) {
    BeginDrawing();
    ClearBackground(RAYWHITE);

    char* gpText = "No gampepad";
    
    for (int gamepad=0; gamepad < 5; gamepad++) {
      if (IsGamepadAvailable(gamepad)) {
        gpText = TextFormat("GP%d: %s", gamepad, GetGamepadName(gamepad));
        for (int gamepadButton = GAMEPAD_BUTTON_UNKNOWN; gamepadButton <= GAMEPAD_BUTTON_RIGHT_THUMB; gamepadButton++) {
          if (IsGamepadButtonDown(gamepad, gamepadButton)) {
            DrawCircle((gamepadButton*17) + 9, 120, 8, RED);
          } else {
            DrawCircle((gamepadButton*17) + 9, 120, 8, GRAY);          }
        }
      }
    }

    DrawText(gpText, 10, 10, 10, BLACK);
    
    EndDrawing();
  }

  CloseWindow();
  return 0;
}

I tested with 2 controllers:

official PS5 controller, paired over bluetooth

• works on general web tester
• works on raylib web tester
• native: only name, no events

PXN-P50S, connected over bluetooth, as "Pro Controller"

• works on general web tester
• works on raylib web tester
• native: only name, no events

I am happy to test anything you like. I have 2 macs for testing (intel and M1.)

Update, after re-pairing a couple times, I got the PS5 controller to work, but not the PXN-P50S:

Update

I made a similar tester in GLFW (3.4) and got similar results.

#include <GLFW/glfw3.h>
#include <stdio.h>

#ifdef EMSCRIPTEN
#include <emscripten.h>
#endif

void joystick_connect_callback(int jid, int event) {
  if (event == GLFW_CONNECTED) {
    printf("connected: %d: %s\n", jid, glfwGetJoystickName(jid));
  } else if (event == GLFW_DISCONNECTED){
    printf("disconnected: %d: %s\n", jid, glfwGetJoystickName(jid));
  }
}

GLFWwindow *window = NULL;

void mainLoop() {
  glClearColor(0.0f, 0.0f, 0.0f, 1.0f);
  glClear(GL_COLOR_BUFFER_BIT);
  glfwSwapBuffers(window);
  glfwPollEvents();

  for (int jid = GLFW_JOYSTICK_1; jid<GLFW_JOYSTICK_4;jid++) {
    if (glfwJoystickPresent(jid)) {
      int count = 0;
      const unsigned char* buttons = glfwGetJoystickButtons(jid, &count);
      for (int b=0;b<count;b++) {
        if (buttons[b]) {
          printf("%d %u: DOWN\n", jid, b);
        } else {
          printf("%d %u: UP\n", jid, b);
        }
      }
    }
  }
}

int main() {
  if (!glfwInit()) {
    return 1;
  }

  window = glfwCreateWindow(320, 240, "gamepad tester", NULL, NULL);
  if (!window) {
    glfwTerminate();
    return 1;
  }

  glfwMakeContextCurrent(window);
  glfwSetJoystickCallback(joystick_connect_callback);

  for (int jid = GLFW_JOYSTICK_1; jid<GLFW_JOYSTICK_4;jid++) {
    if (glfwJoystickPresent(jid)) {
      printf("present: %d: %s\n", jid, glfwGetJoystickName(jid));
    }
  }


#ifdef EMSCRIPTEN
  emscripten_set_main_loop(&mainLoop, 0, 1);
#else
  while (!glfwWindowShouldClose(window)) {
    mainLoop();
  }
#endif

  glfwDestroyWindow(window);
  glfwTerminate();

  return 0;
}

Both were seen initially, but only PS5 updated it's buttons. Like, I saw this, with some buttons pressed on both:

present: 0: Pro Controller
present: 1: DualSense Wireless Controller
0 0: UP
0 1: UP
0 2: UP
0 3: UP
0 4: UP
0 5: UP
0 6: UP
0 7: UP
0 8: UP
0 9: UP
0 10: UP
0 11: UP
0 12: UP
0 13: UP
0 14: UP
0 15: UP
0 16: UP
0 17: UP
0 18: UP
0 19: UP

1 0: DOWN
1 1: UP
1 2: UP
1 3: DOWN
1 4: UP
1 5: UP
1 6: UP
1 7: UP
1 8: UP
1 9: UP
1 10: UP
1 11: UP
1 12: UP
1 13: UP
1 14: UP
1 15: UP
1 16: UP
1 17: UP