1. Home
  2. Discussion and Support
  3. Getting Double Controles Spawned

Getting Double Controles Spawned

  • N

    Hello Nefarius, and ViGEm people.
    I've followed all steps at risk to instal BthPS3.

    It's working nice and clean, but there's a doubt: should i have both DS4 virtual controller and XBOX 360 Controller spawned??

    9924ca0d-205c-427f-8a0b-35109141b4ce-image.png

    also, Shibari Server log:

    Configuration Result:
[Success] Name Shibari.Dom.Server
[Success] DisplayName Shibari Dom Server
[Success] Description Manages AirBender, FireShock & BthPS3 Devices.
[Success] ServiceName Shibari.Dom.Server
Topshelf v4.2.1.215, .NET Framework v4.0.30319.42000
[22:41:32 INF] Loaded sink plugin ViGEm DualShock 4 Sink
[22:41:32 INF] Loaded sink plugin ViGEm Xbox 360 Sink
[22:41:32 INF] Loaded bus emulator AirBender Bus Emulator
[22:41:32 INF] Starting bus emulator AirBender Bus Emulator
[22:41:32 INF] AirBender Bus Emulator started
[22:41:33 INF] Bus emulator AirBender Bus Emulator started successfully
[22:41:33 INF] Loaded bus emulator BthPS3 Bus Emulator
[22:41:33 INF] Starting bus emulator BthPS3 Bus Emulator
[22:41:33 INF] BthPS3 Bus Emulator started
[22:41:33 INF] Bus emulator BthPS3 Bus Emulator started successfully
[22:41:33 INF] Loaded bus emulator FireShock Bus Emulator
[22:41:33 INF] Starting bus emulator FireShock Bus Emulator
[22:41:33 INF] FireShock Bus Emulator started
[22:41:33 INF] Bus emulator FireShock Bus Emulator started successfully
[22:41:33 INF] listen://[::1]:26762/             1  Listener started
The Shibari.Dom.Server service is now running, press Control+C to exit.
[22:41:43 INF] Found FireShock device \\?\USB#VID_054C&PID_0268#7&2F93D522&0&3#{51AB481A-8D75-4BB6-9944-200A2F994E65} (USB\VID_054C&PID_0268\7&2F93D522&0&3)
[22:41:43 INF] Device is DualShock3 with address 64:D4:BD:3E:D1:EB currently paired to 5C:C9:D3:F0:7D:0A
[22:41:43 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got attached via USB
[22:41:43 INF] Auto-pairing device DualShock3 (64:D4:BD:3E:D1:EB) to 5C:C9:D3:F0:7D:0A
[22:41:43 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got attached
[22:41:44 INF] Connecting ViGEm target Nefarius.ViGEm.Client.Targets.DualShock4Controller
[22:41:44 INF] ViGEm target Nefarius.ViGEm.Client.Targets.DualShock4Controller connected successfully
[22:41:44 INF] Connecting ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller
[22:41:44 INF] ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller connected successfully
[22:44:29 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) disconnected
[22:44:29 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got removed via USB
[22:44:29 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got removed
[22:44:29 ERR] Shibari.Sub.Source.FireShock.Exceptions.FireShockReadInputReportFailedException: Failed to read input report. ---> PInvoke.Win32Exception: A operação de E/S foi anulada devido a uma saída de thread ou a uma requisição de aplicativo
   --- End of inner exception stack trace ---
   at Shibari.Sub.Source.FireShock.Core.FireShockDevice.RequestInputReportWorker(Object cancellationToken) in C:\projects\shibari\Sources\Shibari.Sub.Source.FireShock\Core\FireShockDevice.cs:line 157
[22:44:29 ERR] Shibari.Sub.Source.FireShock.Exceptions.FireShockReadInputReportFailedException: Failed to read input report. ---> PInvoke.Win32Exception: A operação de E/S foi anulada devido a uma saída de thread ou a uma requisição de aplicativo
   --- End of inner exception stack trace ---
   at Shibari.Sub.Source.FireShock.Core.FireShockDevice.RequestInputReportWorker(Object cancellationToken) in C:\projects\shibari\Sources\Shibari.Sub.Source.FireShock\Core\FireShockDevice.cs:line 157
[22:44:51 INF] Found FireShock device \\?\USB#VID_054C&PID_0268#7&2F93D522&0&3#{51AB481A-8D75-4BB6-9944-200A2F994E65} (USB\VID_054C&PID_0268\7&2F93D522&0&3)
[22:44:51 INF] Device is DualShock3 with address 64:D4:BD:3E:D1:EB currently paired to 5C:C9:D3:F0:7D:0A
[22:44:51 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got attached via USB
[22:44:51 INF] Auto-pairing device DualShock3 (64:D4:BD:3E:D1:EB) to 5C:C9:D3:F0:7D:0A
[22:44:51 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got attached
[22:44:51 INF] Connecting ViGEm target Nefarius.ViGEm.Client.Targets.DualShock4Controller
[22:44:51 INF] ViGEm target Nefarius.ViGEm.Client.Targets.DualShock4Controller connected successfully
[22:44:51 INF] Connecting ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller
[22:44:51 INF] ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller connected successfully
[22:45:00 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) disconnected
[22:45:00 ERR] Shibari.Sub.Source.FireShock.Exceptions.FireShockReadInputReportFailedException: Failed to read input report. ---> PInvoke.Win32Exception: A operação de E/S foi anulada devido a uma saída de thread ou a uma requisição de aplicativo
   --- End of inner exception stack trace ---
   at Shibari.Sub.Source.FireShock.Core.FireShockDevice.RequestInputReportWorker(Object cancellationToken) in C:\projects\shibari\Sources\Shibari.Sub.Source.FireShock\Core\FireShockDevice.cs:line 157
[22:45:00 ERR] Shibari.Sub.Source.FireShock.Exceptions.FireShockReadInputReportFailedException: Failed to read input report. ---> PInvoke.Win32Exception: A operação de E/S foi anulada devido a uma saída de thread ou a uma requisição de aplicativo
   --- End of inner exception stack trace ---
   at Shibari.Sub.Source.FireShock.Core.FireShockDevice.RequestInputReportWorker(Object cancellationToken) in C:\projects\shibari\Sources\Shibari.Sub.Source.FireShock\Core\FireShockDevice.cs:line 157
[22:45:00 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got removed via USB
[22:45:00 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got removed
[22:45:01 INF] Found SIXAXIS device \\?\BTHPS3BUS#{53F88889-1AAF-4353-A047-556B69EC6DA6}#9&372AD2D9&0&64D4BD3ED1EB#{7B0EAE3D-4414-4024-BCBD-1C21523768CE} (BTHPS3BUS\{53F88889-1AAF-4353-A047-556B69EC6DA6}\9&372AD2D9&0&64D4BD3ED1EB)
[22:45:01 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got attached via Bluetooth
[22:45:01 INF] Device DualShock3 (64:D4:BD:3E:D1:EB) got attached
[22:45:01 INF] Connecting ViGEm target Nefarius.ViGEm.Client.Targets.DualShock4Controller
[22:45:01 INF] ViGEm target Nefarius.ViGEm.Client.Targets.DualShock4Controller connected successfully
[22:45:01 INF] Connecting ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller
[22:45:02 INF] ViGEm target Nefarius.ViGEm.Client.Targets.Xbox360Controller connected successfully

    Till now, thanks for reading! Also Nefarius, absolutely magnificent work with this last tool, was just everything i was needing! When I get able, I'll donate you some value, for all these years you're involved in free and goood solutions for us

    0
  • Daltz333

    In the sinks folder of Shibari, delete the DS4 or XBox one. Keep the one of the joystick you want.

    0
  • nefarius

    Read the FAQ ☺️

    0
bthps3 2 shibari 2 bug 1
Log in to reply