Games and Apps May Not Detect Virtual Controller Properly...

[Miron4ik42]

I assume that it doesn't matter if the controller is virtual or physical. It depends only on the game and how the controller support is configured in it

[HaydenMccoy]

I stumbled upon an interesting issue – it seems like some games and apps are having a hard time recognizing virtual controllers properly. Has anyone else run into this? It's kinda funny when your virtual controller has a mind of its own, right? 😄 And, speaking of games, has anyone tried those legit games that pay real money instantly? Found some cool ones recently, they're a blast! 💰

[reWASDer]

We can't test each and every game and app, so that is why the first thing I have tried to reproduce your issue — is to check the same app (RetroArch was the easiest one to get). I can't reproduce the issue at all, that is why we can't actually debug this issue. Maybe, your config could help us.

Also, I don't know which drivers you have installed, so I can't say whether it is a driver conflict or not.

[lupo90]

I give up, just as a side note that my controller works with other software 100% of time and gives these problems only with reWASD.
I pointed out many other times, so here's one more, it is not a RetroArch problem, when reWASD doesn't work, it doesn't work with all the apps in my system except for joy.cpl, and it does it intermittently, and approximately 10-20% of times works when creating a virtual x360 controller.
I am disappointed, I paid the full packet, and visually reWASD is a pleasant software.
And I am disappointed to have to repeat multiple times that it is not a RetroArch problem, after also video proof served.
I give up.
Nonetheless, thanks for your time, I really appreciate your effort and I hope that reWASD will solve these problems as it seems a great software apart from these nuisances. For example no debugging have I been asked or such, I wonder how would you sort this out? Maybe with future updates?
I believe you should have caught the occasion while having an available to help (and with a relevant problem) customer.
Again, many thanks for living a day of trials with me
I hope reWASD can get back and sort out these driver issues in the future as it's a nice software.

[reWASDer]

Also, I see that you have Shortcuts on some buttons. With Shortcuts enabled, the single button press will work with a delay (it could be adjusted in Preferences -> Press time). Maybe you could send us your config to check it too? The easiest way to find it — use Open file location option in the context menu of the active config.

[reWASDer]

I am sorry, but I again, I can't understand what exactly happens here.

RetroArch doesn't detect the virtual gamepad from time to time? Yes, it may happen. It happens with any game and app. The app should be relaunched, and most often, it helps.

Or the virtual controller is recognized, but you do not get the input? Try to restart in this case too. If it doesn't help, I am not sure if we could help — as the gamepad is properly working in joy.cpl. Or not?

I am checking this app right now, switching remap on and off several times, re-launching the app and everything seems to be perfect.

[lupo90]

Just to be sure, I have the same exact behaviour as RetroArch in other apps (such as BSNES as shown in the video, but many others will do the exact, intermittently reWASD works, others no input received in the apps at all)

[lupo90]

reWASDer thanks for the help, I confirm my settings are right, in fact if you note on the video(s), intermittently reWASD mapping works, and when it works, it is recognised in RetroArch and all the inputs are rightly received, even all the complex ones.
I confirm I have big familiarity with RetroArch as well so I know how it works and how to set it up.
So it must be something else

[reWASDer]

Hm, at first, I thought that the gamepad is not detected by the app, however, yep, I see now. So it is recognized but is not working? But it does work with a physical one? Pretty strange, moreover, I have just checked RetroArch, and I have no issues with it at all

Could you please re-check the settings the controller has in RetroArch, here are they. Maybe you have different mappings inside the app itself?

[lupo90]

reWASDer just to be sure that I understood correctly,

right after you restarted RetroArch, it detected the controller at once.

Retroarch behaved the same before and after restart, if sees the controller in the right way (X360 Virtual controller). The problem is that no input flows to the Apps, both RetroArch and BSNES.
You can watch the video carefully and you will notice that once in the state "Remap is ON", RetroArch correctly sees the X360 Virtual controller and disconnects the real XOne Controller (I am using a XOne wireless controller in these tests). Viceversa when in the state "Remap is OFF", the real XOne is connected and the virtual X360 is gone.

your first gamepad is detected in the system, and when you create a virtual one while the tools/games are on, they may work or may not.

The behaviour I see and that you can see in the video is that regardless that it is physical or virtual, it is seen as just 1 controller connected, so each time the connected controller numbers equals 1.
But at times the virtual X360 Controller sends the right inputs, many other times not (approx. 10-20% from what you can see in the video, and that's the same stat I shared above).

Please let me know if the meaning was different and thanks in advance.

I believe that we are beating around the bush, and that the issue is somewhere that is not yet visible to our eyes, maybe someone has a new idea?

[reWASDer]

As I can see, right after you restarted RetroArch, it detected the controller at once. If you have two or more physical gamepads reconnected during the play, you will probably get the same situation — your first gamepad is detected in the system, and when you create a virtual one while the tools/games are on, they may work or may not.

I am not sure if we can do anything here.

[lupo90]

Hello reWASDer , I confirm that I closed and reopened different tools, for example antimicro, retroarch, bsnes, etc, at times the joypad it is not recognised other times it is recognised, but the experience is the same with all the tools, and what I mean is, if it doesn't work properly in RetroArch, then it will malfunction in others too in my experience

Please find here a video where in the end I also close and reopen the apps, and with joy.cpl visible

https://youtu.be/7aLhE6ilbLM

[reWASDer]

Have you tried to restart the app after you applied a config? The games and tools often do not recognize the newly created device, and that may be an issue. Also, it is better to restart other launchers you may be using here.

[lupo90]

I would argue that it is inconclusive to say that because joy.cpl works, then the tool works fine - I tried other tools which work.
The only thing you can assume right now is that joy.cpl works and there's a misbehaviour somewhere.
Given that DS4Windows, AntiMicro, XPadder, work and reWASD intermittently works, then I cannot assume that it's not related to reWASD and you cannot as well.
Also reWASD works (approximately) 30-40% of times if I set a virtual output to be "Xbox One" and 10-20% if set to "Xbox 360". This proves that the Software changes variables inbetween.

I have no intention to reinstall Windows, the only tool that is not working as expected is reWASD right now.
What is the repair tools/diagnosis tools that you suggest, so that I can try?
Is there any other suggestion? For example, by removing drivers and how to do it?

[wookiepediologist]

joy.cpl is a Windows tool which is mainly responsible for the gamepads' output in games.

Thus, joy.cpl is the only thing which is mandatory in remapping.

If everything works fine in joy.cpl, there is nothing else we can do to fix the issue you are facing with, unfortunately.

If the issue is still happening, it is caused by the incompatibility issues between the joy.cpl, which is the main system tool for the gamepad input and the app you are using the gamepad in.

I can only suggest running the Windows repairing tools/diagnosis tools, etc. The windows' reinstallation might work, even without the personnel files' removal.