Jump to content
LaunchBox Community Forums

Aimnos

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Aimnos

  1. As I stated above (post from May 2, 2019), I switched my input driver from dinput to raw to solve issues with altering the system volume while playing. But yeah, I don't have problems after the controller disconects unless I have menu input/max no. of users set to a certain value.
  2. What kind of controller are you using? I use a PS4 controller with the DS4Windows software for xinput. I also enabled an option that hides the dinput device to avoid double inputs. The problem with that is, whenever my controller gets disconected, the software is unable to hide the dinput device, since RA captures it. If I have maximum users set to 1, then I become unable to use my controller because the dinput device fills in port 1, and I have to restart RA. I also remember there being an option somewhere that limits menu control to the first player only, which would also give trouble in this situation. Otherwise, aside from the fact that I have 2 controllers detected in RA and my xinput device being in the 2nd port, I don't have any issues with not being able to reuse the controller after disconecting.
  3. For me, changing the input driver to raw solved the problem. At first, changing the system volume with a hotkey would eject the disc. Then, one day, it initiated netplay whenever I tried to change the system volume. My input driver was set to dinput and changing it to sdl2 had no effect, but changing it to raw solved it with no apparent side effects whatsoever.
×
×
  • Create New...