Announcement

Collapse
No announcement yet.

Random disconnect on auto profile switch

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Random disconnect on auto profile switch

    I'm using an Elite Series 2 with the XBox USB wireless adapter and heavy amounts of application autodetect and auto-profile switching. Everything was working perfectly until I did a Windows 11 fresh install. Since then, the controller will randomly disconnect and shut off when attempting to switch game profiles. Sometimes, it switches profiles without issue. When it does shut off, I can turn it back on and everything's fine. Any suggestions? Thanks.

  • #2
    Hello.
    Have you reinstalled the OS or upgraded to Windows 11?

    Try reinstalling reWASD following the steps below:
    1. Uninstall reWASD via Windows Apps & features
    2. Restart the PC
    3. Install the latest build from our website
    4. Restart the PC again.

    If that doesn't help, make sure you've set up Autodetect correctly.
    You can also clean up the data and set up Autodetect from scratch. To do this, do the following:
    Open → General → Clear data button. Confirm the action and wait for reWASD to restart.

    Comment


    • #3
      I think following your instructions and uninstalling/reinstalling reWASD has fixed the issue. Thanks!

      Comment


      • #4
        And of course, just after I post that, it starts happening again...

        This is occurring after a clean install of Windows 11 on new hardware. Previously, I was using Windows 10 with the same profiles that I backed up and restored to this new PC, and this never occurred on the old PC. I've attempted clearing data and re-setting up autodetect before reaching out to you.

        What I've determined since following your instructions is that the problem appears to go away after I reboot the computer and comes back after the computer's been on for a while. Like I said, the controller only shuts off sometimes when switching profiles, maybe 50% of the time.

        Comment


        • #5
          Hello! Please check power management setting:Open [Device Manager] (right-click on the Start button for option to appear).
          1. Set the [View] to [Devices by container].
          2. Find your controller.
          3. Check your Xbox Elite controller for a [Power Management] tab and disable [Allow the computer to turn off this device to save power] option there.
          After that, you might need to restart your PC once.

          Comment


          • #6
            I have ensured that every device listed under the Xbox One Wireless Controller and Xbox Wireless Adapter for Windows containers have "Allow the computer to turn off this device to save power" disabled, then restarted my PC. The issue is still occurring.
            Click image for larger version

Name:	Screenshot 2022-07-10 180643.png
Views:	280
Size:	81.0 KB
ID:	232904

            Comment


            • #7

              In this case, we need you to collect logs for us by following the steps:
              1. Run reWASD as administrator
              2. Open Preferences — General, and make sure you chose Standard logging, with Service/Driver logs and GUI/Agent logs
              3. Press Start log, and you will see a following message:

              4. Follow the instructions: press Yes, and reWASD will restart. Once that is done, reproduce the steps that lead to the issue (switch profiles until the controller is turned off)
              5. When finished, get back to Preferences — General, and click Stop log. You will see this message:

              6. Click Open file location, find the archive and *.txt file(s) that were created the last, and send them all to our support team.

              In case you have completed the steps above, but accidentally clicked Restart now instead of Open file location, you can still find the archive with logs and *.txt file(s) using this path: C:\Users\Public\Documents\reWASD\Logs.

              Comment


              • #8
                Thanks. I have collected the logs. Should I attach them to this thread, or is there a better way to get them to support?

                Comment


                • #9
                  As you wish, we will check them asap either here, or if you send them to help@rewasd.com email address.
                  There is nothing personal could be understood from the log, no worries.

                  Comment


                  • #10
                    Here you go. Much appreciated!
                    Attached Files

                    Comment


                    • #11
                      Thank you for the info.

                      At the moment, we can see that the system itself shuts the controller down. But we are not sure why it happens.

                      Am I right that you are using two configs (during the logging)? The first one emulates the virtual gamepad, and the second one uses keyboard and mouse mappings. Could you please send them too? We will need some time to reproduce the same issue from our side. Also, one more question: which physical slot was active at this moment and have you switched it anytime later/earlier?

                      Comment


                      • #12
                        I don't use any keyboard and mouse mappings. I have a default gamepad mapping, which then switches to a game-specific gamepad mapping via autodetect when I open the game (in this case, the game gets opened via a key combo in the default profile, but I believe this also occurs if I open the game by other means). I've attached the two configs involved during the logging, but I have plenty of others as well, and this issue seems to occur sporadically whenever I toggle between any of them via autodetect.

                        Regarding physical slots, my default profile is on slot 1, and all of my autodetect profiles are assigned to slot 4. I have it set up where I never need to manually switch slots.
                        Attached Files

                        Comment


                        • #13
                          Thank you for providing additional information. I will forward configs to our team to reproduce the same issue from our side.

                          Comment


                          • #14
                            Originally Posted by himynameiswill View Post
                            I don't use any keyboard and mouse mappings. I have a default gamepad mapping, which then switches to a game-specific gamepad mapping via autodetect when I open the game (in this case, the game gets opened via a key combo in the default profile, but I believe this also occurs if I open the game by other means). I've attached the two configs involved during the logging, but I have plenty of others as well, and this issue seems to occur sporadically whenever I toggle between any of them via autodetect.

                            Regarding physical slots, my default profile is on slot 1, and all of my autodetect profiles are assigned to slot 4. I have it set up where I never need to manually switch slots.
                            Your RetroArch config includes the keyboard and mouse mappings only, there is no controller mappings inside. Your Xbox One controller uses the virtual Xbox One controller, which, I think, it doesn't need. If you remove the virtual controller mappings and change them to Native mappings for paddles, then the config will work pretty much the same:

                            Click image for larger version  Name:	8ca8ab5970.png Views:	0 Size:	665.0 KB ID:	232989

                            If the same is true for other profiles you use, then, it would be a good idea to remove all other unnecessary virtual controllers.

                            When the virtual controller is used, reWASD hides the physical controller from the system and creates a virtual one. According to logs, when reWASD unhides your physical controller (when you are switching to the game), the system sends "power off" command, and from our side, we don't see any reasons to do so. And unfortunately, we could not reproduce the same issue from our side yet — using Xbox Elite 2, official dongle and your configs. If we remove the virtual controller from your configs, then reWASD won't need to hide and unhide the virtual controller, so it sounds like a solution in your case. Could you please try it?

                            The easiest way to remove all virtual controller mappings is using the Magic Wand icon under the controller's picture.

                            Comment

                            Working...
                            X