Hello,

I have this small gamepad input test program. In the program, I poll the first 3 gamepad IDs, but all detection attempts return false. I know that my gamepad is an Xinput model. I have tried starting the program before and after the gamepad is plugged in, but there is no change.

Sample:

bool GP0_found = IsGamepadAvailable(0); // false
bool GP1_found = IsGamepadAvailable(1); // false
bool GP2_found = IsGamepadAvailable(2); // false

Has anyone else experienced this and know the fix?

On Wednesday, 30 November 2022 at 22:46:52 UTC, jwatson-CO-edu wrote:

bool GP0_found = IsGamepadAvailable(0); // false
bool GP1_found = IsGamepadAvailable(1); // false
bool GP2_found = IsGamepadAvailable(2); // false

Which OS and wich controllers are you using?

You might want to open an issue on the raylib-d repo: https://github.com/schveiguy/raylib-d/issues

On Wednesday, 30 November 2022 at 23:18:33 UTC, ryuukk_ wrote:

I tested on Ubuntu 22.04 and Linux Mint 20 with an older GameSir brand wired XBox controller. Built with Raylib 2.4.0 and raylib-d 2.4.1.

I know that the author monitors the forum. So, I will open an issue if he does not point out something obvious that I missed.

On 11/30/22 7:28 PM, jwatson-CO-edu wrote:

Do you have that version correct? I'm assuming you mean raylib 4.2.0 and raylib-d 4.2.1?

Highly recommend to update to raylib-d 4.2.4, and use the the Linux raylib-d:install as that now works (and will properly grab the correct raylib library from the repository for you).

For your specific problem, I would say that if it's not working, it's not a problem specifically with raylib-d, but with raylib. Such functions are just prototypes in raylib-d, the C library does the implementation.

This would probably be best actually to discuss either on the raylib discord (there's a raylib-d channel) or open an issue in my repository. Raylib does a lot of logging things, you can probably see if your gamepad is detected.

-Steve

On Thursday, 1 December 2022 at 01:12:17 UTC, Steven Schveighoffer wrote:

Yes, following your instructions I have raylib 4.2.0 and raylib-d 4.2.4 in the project directory. I am now using the latest version of raylib-d, but this did not resolve the gamepad issue. I can ask around on the raylib channels.

On 11/30/22 8:49 PM, jwatson-CO-edu wrote:

Oh, I think I know the issue -- you need to check inside the loop. The way raylib works is that it polls events from the glfw library. So unless you are actually calling BeginDrawing and EndDrawing, those flags won't change.

-Steve

On Thursday, 1 December 2022 at 02:06:43 UTC, Steven Schveighoffer wrote:

But probably not on every frame, have a delay between checks.

On 12/1/22 3:24 AM, bauss wrote:

It's not anything controllable by the user. The library does the check every frame regardless of whether you use it or not.

When you call the raylib function, you are not actually querying the device, you are checking a boolean in a struct.

https://github.com/raysan5/raylib/blob/387c06000618ef0aa3b15c5e46d1c525ba194c50/src/rcore.c#L3567

-Steve

On Thursday, 1 December 2022 at 01:49:09 UTC, jwatson-CO-edu wrote:

Can you try with this page: https://www.raylib.com/examples/core/loader.html?name=core_input_gamepad

Does it detect your gamepad?

On 12/1/22 11:10 AM, ryuukk_ wrote:

It should work because the IsGamepadAvailable function call is inside the loop. That's most certainly the problem with the OP code.

-Steve