Windows: Progressive FPS degradation in Persona 5 Royal with virtual Xbox Series controller; disconnecting controller restores performance
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 12/100
- Type d'issue
- Bug
- Clarté
- À clarifier
- Activité
- Active
- Stack technique
- cpp
- Domaine
- desktop-dev
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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.
- Langage dominant
- C++
- Étoiles
- 93
- Forks
- 25
- Merge moyen
- 13 h 57 min
- PR mergées (30 j)
- 33
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de LizardByte/libvirtualhid
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
LizardByte/libvirtualhid#204 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Windows: driver host process crashes ~1s after DualSense virtual gamepad creation; all libvirtualhid devices become invalid until rebootPeut-être pris @ReenigneArcher l’a pris il y a 2 jours. Ouverte
Difficulté 4/5 3-5 jours Accessibilité débutants 43/100
LizardByte/libvirtualhid#199 · 9 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
Experiencing Complete Control Loss After Close/DC of Moonlight And Reconnect with DualSensePeut-être pris @ReenigneArcher l’a pris il y a 2 jours. Ouverte
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
LizardByte/libvirtualhid#196 · 4 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
Impulse trigger vibration not functioning on Moonlight 6.2.0Peut-être pris @ReenigneArcher l’a pris il y a 8 jours. Ouverte
Difficulté 4/5 3-5 jours Accessibilité débutants 18/100
LizardByte/libvirtualhid#193 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Windows: Xbox Series Share button is unavailable through Steam's VHF/XInput pathPeut-être à nouveau libre @LizardByte-bot l’a pris il y a 58 jours, et aucune pull request n’est ouverte. Ouverte
LizardByte/libvirtualhid#106 · 1 personne assignée ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de LizardByte/libvirtualhid
Issues similaires
-
[mimalloc] update to 3.6.0Ouvertecategory:port-update
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
Les mainteneurs répondent en général sous 2 jours
-
MinGW build faillureOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 67/100
facebookresearch/faiss#5775 · 1 commentaire ·
Les mainteneurs répondent en général sous 2 jours
-
Eval bug: minimax-m3: build_moe_ffn() drops the per-expert NVFP4 scale → garbled output (M3.1 Flash)Ouvertebug-unconfirmed
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
Les mainteneurs répondent en général sous 1 jour
-
bug triage
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
secondlife/viewer#6507 ·
Les mainteneurs répondent en général sous 1 jour
-
clang:frontend code-cleanup HLSL
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
llvm/llvm-project#235100 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour