You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using my Razer Edge (Android) in conjunction with the associated Razer Kishi V2 Pro in X-Input mode, Android crashes every few minutes and then restarts (cold start). However, if I use the Kishi V2 Pro in HID mode, this does not happen. However, the haptic feedback only works in X-Input mode. I also tried a PS5-style telescopic Bluetooth controller in X-Input mode. The exact same thing happens here. At first I thought it might be a Razer Edge-specific problem, but yesterday the exact same thing happened with my Lenovo Legio Y700 (2022) to which I had connected an Xbox Series X controller via a USB cable. I suspect it has something to do with the haptic feedback, as it always crashes when there is a lot of rumble.
Steps to reproduce
Use a Razer Edge or Lenovo Legion Y700 as a Moonlight client and use a controller with haptic feedback in X-Input mode (wired or via Bluetooth) and play Call Of Duty, Gears of War or any Nedd for Speed game.
Affected games
I suspect that it affects all games with rumble support. I am sure about Call of Duty MWIII, Gears of War 5 and Need for Speed Rivals.
Other Moonlight clients
PC
Moonlight adjusted settings
Yes
Moonlight adjusted settings (please complete the following information)
Native Resolution and Native FPS (2400x1080@144 and 2560x1600@120)
Bitrate 50
Frame Parcing: Ballanced
Force full range Video
Moonlight default settings
Yes
Gamepad-related connection issue
No
Gamepad-related input issue
Yes
Gamepad-related streaming issue
Yes
Android version
Razer Edge Android 12, Lenovo Y700 Android 12
Device model
Razer Edge and Lenovo Legion Y700 (2022)
Server PC OS version
Windows 11 23H2
Server PC GeForce Experience version
Sunshine
Server PC Nvidia GPU driver version
AMD Driver Version 24.7.1
Server PC antivirus and firewall software
Windwes Defender and Windows Firewall
Screenshots
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
When using my Razer Edge (Android) in conjunction with the associated Razer Kishi V2 Pro in X-Input mode, Android crashes every few minutes and then restarts (cold start). However, if I use the Kishi V2 Pro in HID mode, this does not happen. However, the haptic feedback only works in X-Input mode. I also tried a PS5-style telescopic Bluetooth controller in X-Input mode. The exact same thing happens here. At first I thought it might be a Razer Edge-specific problem, but yesterday the exact same thing happened with my Lenovo Legio Y700 (2022) to which I had connected an Xbox Series X controller via a USB cable. I suspect it has something to do with the haptic feedback, as it always crashes when there is a lot of rumble.
Steps to reproduce
Use a Razer Edge or Lenovo Legion Y700 as a Moonlight client and use a controller with haptic feedback in X-Input mode (wired or via Bluetooth) and play Call Of Duty, Gears of War or any Nedd for Speed game.
Affected games
I suspect that it affects all games with rumble support. I am sure about Call of Duty MWIII, Gears of War 5 and Need for Speed Rivals.
Other Moonlight clients
PC
Moonlight adjusted settings
Yes
Moonlight adjusted settings (please complete the following information)
Native Resolution and Native FPS (2400x1080@144 and 2560x1600@120)
Bitrate 50
Frame Parcing: Ballanced
Force full range Video
Moonlight default settings
Yes
Gamepad-related connection issue
No
Gamepad-related input issue
Yes
Gamepad-related streaming issue
Yes
Android version
Razer Edge Android 12, Lenovo Y700 Android 12
Device model
Razer Edge and Lenovo Legion Y700 (2022)
Server PC OS version
Windows 11 23H2
Server PC GeForce Experience version
Sunshine
Server PC Nvidia GPU driver version
AMD Driver Version 24.7.1
Server PC antivirus and firewall software
Windwes Defender and Windows Firewall
Screenshots
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: