Skip to content

[BUG] 1s+ delay in-game in Dolphin Emulator(and others?) #8

@olioski

Description

@olioski

Bug Description

I'm having a high amount of input delay(motion and buttons) while in-game in primarily Dolphin Emulator. It makes games that require the pointer or motion unplayable.

Steps to Reproduce

  1. Open Dolphin Emulator
  2. Run PSMove-DSU
  3. Set up Dolphin Emulator with the DSU Client and map the controller and motion
  4. Have a huge amount of input delay with pointing in-game.

Expected Behavior

Little to no delay

Actual Behavior

Full on 1 second delay

System Information

  • OS: Windows 11
  • Architecture: x64
  • PSMove-DSU Version: v2.1.0
  • Controller Model: CECH-ZCM1E
  • Connection Type: Bluetooth

Performance Information

If related to latency/performance:

  • Latency warnings in logs: Yes, but aren't often. Logs below:
    [DEBUG] Client requesting controller info [DEBUG] Replied INFO for slot 0 (connected: yes) [DEBUG] Replied INFO for slot 1 (connected: no) [DEBUG] Replied INFO for slot 2 (connected: no) [DEBUG] Replied INFO for slot 3 (connected: no) [DEBUG] Sent DATA for 1 controllers to 3 clients (loop: 180µs) [WARN] High end-to-end latency for slot 0: 15124µs [DEBUG] Client requesting controller info [DEBUG] Replied INFO for slot 0 (connected: yes) [DEBUG] Replied INFO for slot 1 (connected: no) [DEBUG] Replied INFO for slot 2 (connected: no) [DEBUG] Replied INFO for slot 3 (connected: no) [WARN] Windows: Flushed 50 buffered packets from slot 0
  • CPU usage during issue: 8%
  • Other running applications: Chrome, Whatsapp, Avast One Antivirus, Logitech G Hub

Verbose Logs

[INFO] DSU server starting...
[INFO] Make sure your controllers are paired using --pair mode first.
[INFO] Windows 1ms timer resolution enabled
[DEBUG] PSMove manager started with background scanning (zero-latency)
[INFO] UDP server started on port 26760 (optimized for low latency)
[INFO] DSU server started successfully (optimized for low latency)
[INFO] Multi-controller DSU server running (optimized timing)...
[DEBUG] Polling thread pinned to CPU core 0
[DEBUG] === BACKGROUND CONTROLLER SCAN START ===
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: no)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Replied INFO for slot 3 (connected: no)
[DEBUG] Found e0:ae:5e:cb:60:14 (BT)
[INFO] Windows: Drained 4 initial buffered packets from e0:ae:5e:cb:60:14
[INFO] Queued e0:ae:5e:cb:60:14 for assignment to Slot 0
[DEBUG] === BACKGROUND SCAN COMPLETE ===
[INFO] Integrated e0:ae:5e:cb:60:14 -> Slot 0
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Replied INFO for slot 3 (connected: no)
[INFO] Client subscribed to DATA. Total: 1
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Replied INFO for slot 3 (connected: no)
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Replied INFO for slot 3 (connected: no)
[DEBUG] Sent DATA for 1 controllers to 1 clients (loop: 14µs)
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Replied INFO for slot 3 (connected: no)
[DEBUG] === BACKGROUND CONTROLLER SCAN START ===
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Skipping e0:ae:5e:cb:60:14 - already connected
[DEBUG] Replied INFO for slot 3 (connected: no)
[DEBUG] === BACKGROUND SCAN COMPLETE ===
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Sent DATA for 1 controllers to 1 clients (loop: 5971µs)
[DEBUG] Replied INFO for slot 3 (connected: no)
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Replied INFO for slot 3 (connected: no)
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Replied INFO for slot 3 (connected: no)
[DEBUG] Sent DATA for 1 controllers to 1 clients (loop: 15233µs)
[DEBUG] Client requesting controller info
[DEBUG] Replied INFO for slot 0 (connected: yes)
[DEBUG] Replied INFO for slot 1 (connected: no)
[DEBUG] Replied INFO for slot 2 (connected: no)
[DEBUG] Replied INFO for slot 3 (connected: no)

Troubleshooting Attempted

What have you already tried?

  • [✓] Restarted the application
  • [✓] Re-paired the controller (--pair mode)
  • [✓] Checked Bluetooth connection
  • [NA] Tested with different USB cable (if applicable)
  • [✓] Checked port 26760 availability
  • [✓] Tested with other DSU clients (Dolphin, Cemu, etc.)(I was not able to accurately test the delay with cemu since button mapping through dsu does not work for me, but it seems that the delay applies there too)
  • Tested on different computer/OS

Urgency Level

  • Critical - Application crashes or completely unusable
  • [✓] High - Major functionality broken, workaround exists(workaround being struggling with the delay)
  • Medium - Minor functionality issues or performance problems
  • Low - Small inconveniences or feature improvements

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions