Windows: Progressive FPS degradation in Persona 5 Royal with virtual Xbox Series controller; disconnecting controller restores performance
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 12/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- cpp
- Área
- desktop-dev
Línea de trabajo
The payload names no source files or tests, so start by reproducing the slowdown with the Windows libvirtualhid driver and the Sunshine virtual Xbox Series controller, then compare controller create and destroy paths against the reported recovery on reconnect. Sunshine logs showing the controller being recreated are the main clue. Done would mean isolating whether the fault lies in libvirtualhid or its Windows, Steam Input or game interaction; this needs maintainer input and is not a first-timer task.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the Bug
While streaming Persona 5 Royal through Sunshine to Moonlight on an Xbox Series X, the game's actual rendering FPS gradually deteriorates when using a controller through libvirtualhid.
Disconnecting the controller immediately restores approximately 120 FPS. Performance remains restored after reconnecting it, without restarting the game or Sunshine. I reproduced this behavior more than once.
This affects the Steam FPS counter and the game on the physical PC monitor, so it is a host-side rendering slowdown rather than only dropped streaming frames.
Environment
- OS: Windows 10 Pro, build 19045
- libvirtualhid Windows driver: 2026.914.1218.10
- Sunshine: 2026.914.233613
- Sunshine gamepad driver setting:
virtualhid - Virtual gamepad: Xbox Series, automatically selected
- CPU: AMD Ryzen 5 3600
- GPU: NVIDIA RTX 3070 Ti, 8 GB VRAM
- NVIDIA driver: 581.29
- RAM: 32 GB
- Client: Moonlight UWP on Xbox Series X
- Game: Persona 5 Royal, Steam version
- Streaming encoder: H.264 NVENC, P1, approximately 60 FPS
Steps to reproduce
- Start Sunshine with the Virtual HID backend and Xbox Series gamepad emulation.
- Connect from Moonlight on an Xbox Series X.
- Launch Persona 5 Royal and play using the Xbox controller.
- Continue playing for approximately 30–60 minutes.
- Observe progressively declining FPS in Steam's FPS counter and on the PC monitor.
- Disconnect the controller while leaving the game, Sunshine, and Moonlight running.
- Reconnect the controller.
Actual behavior
- Playing locally without Sunshine gives stable performance around 120 FPS.
- Streaming sessions initially run around 80–100 FPS, then gradually deteriorate.
- One session reached approximately 27 FPS after around 30 minutes.
- Another reached approximately 16 FPS after around an hour.
- More intensive controller use, particularly holding buttons, appears to accelerate the degradation. This is an observation rather than a measured input-rate comparison.
- Disconnecting the controller immediately restores approximately 120 FPS.
- FPS remains restored after reconnecting the controller.
- Sunshine logs show the virtual Xbox Series controller being created again around the recovery. The game process remains the same.
Diagnostics during the slowdown
- Persona's main thread was almost fully occupying one logical CPU, with most of that time spent in kernel mode.
- GPU utilization was only approximately 14–17%.
- GPU temperature was approximately 45°C, with no thermal throttling reported.
- GPU memory usage was approximately 2.2–2.3 GB out of 8 GB.
- Approximately 20 GB of system RAM remained available.
- After controller reconnection, the game's kernel CPU usage fell substantially and GPU utilization increased to approximately 54%, alongside the FPS recovery.
Other tests
- Disabling Sunshine's "Present OpenGL/Vulkan on top of DXGI" option did not resolve the issue.
- Stopping the Nahimic audio service while the slowdown was occurring did not restore performance.
- In an earlier occurrence, disconnecting the Moonlight client alone did not restore FPS, but fully exiting Sunshine did.
The controller disconnect/reconnect test is currently the most reliable way to clear the slowdown. I suspect an issue in the virtual controller/input path, but have not yet isolated whether the cause is libvirtualhid itself or its interaction with Windows, Steam Input, or the game.
Expected Behavior
Controller input, including sustained button presses, should not cause progressively increasing host-side CPU overhead or declining game FPS.
Performance should remain stable throughout long streaming sessions, without requiring the controller to be disconnected and reconnected to restore normal FPS.
Additional Context
When using vigembus driver all works fine and FPS is not dropping, so it's libvirtualhid driver issue in my honest opinion.
- Lenguaje dominante
- C++
- Estrellas
- 93
- Forks
- 25
- Merge medio
- 15 h 16 min
- PR fusionados (30 d)
- 30
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de LizardByte/libvirtualhid
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
LizardByte/libvirtualhid#204 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
LizardByte/libvirtualhid#206 ·
Los mantenedores suelen responder en 1 día
-
Windows: driver host process crashes ~1s after DualSense virtual gamepad creation; all libvirtualhid devices become invalid until rebootPosiblemente ocupada @ReenigneArcher la tomó hace 5 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 43/100
LizardByte/libvirtualhid#199 · 9 comentarios ·
Los mantenedores suelen responder en 1 día
-
Experiencing Complete Control Loss After Close/DC of Moonlight And Reconnect with DualSensePosiblemente ocupada @ReenigneArcher la tomó hace 5 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
LizardByte/libvirtualhid#196 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
-
Impulse trigger vibration not functioning on Moonlight 6.2.0Posiblemente ocupada @ReenigneArcher la tomó hace 11 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 18/100
LizardByte/libvirtualhid#193 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de LizardByte/libvirtualhid
Issues similares
-
crash lld:COFF
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
llvm/llvm-project#235970 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: iOS textarea wraps text mid-word because LynxUIBaseInput hardcodes NSLineBreakByCharWrappingAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
lynx-family/lynx#10455 ·
Los mantenedores suelen responder en 1 día
-
A-tools P-low S-blocked task
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
cv::checkRange fails with "Unsupported matrix depth" for fp8 depthsPosiblemente ocupada @sshivensolanki la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Rifle-variant weapon offsets are saved under the pistol's name [FRIK-093]Posiblemente ocupada @rollingrock la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
rollingrock/Fallout-4-VR-Body#182 ·