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 I stream the screen to my pad using the virtual screen in Sunshine Moonlight, I also want it to appear on pc monitor at the same time, so I use desktop extensions in my window display settings. But every time I run Moonlight, the settings reset, is there a way to fix this?
Can I make sure that the virtual screen is maintained even when the Moonlight is shut down? I don't like that the virtual screen driver is turned off and on.
The text was updated successfully, but these errors were encountered:
You can’t directly get the virtual screen to your main monitor without doing manual change. A workaround to do every time you start a streaming session is to mirroring or extend your desktop with the keys combination Windows + P and select the desired mode to get your monitors back.
I don’t understand why you want to keep the virtual monitor available when you don’t use it. First it consumes useless GPU/CPU/RAM ressources to display a non-existent screen that you will never use unless you stream this screen to another device. Second if you extend your desktop with the VDD on, you will have some "issues" with your mouse "disappear" and go on the virtual monitor.
But if you want to do this for any reasons, you have to do this manually until i add an option for this. But with my current tests, it’s not that easy to implement right now.
When I stream the screen to my pad using the virtual screen in Sunshine Moonlight, I also want it to appear on pc monitor at the same time, so I use desktop extensions in my window display settings. But every time I run Moonlight, the settings reset, is there a way to fix this?
Can I make sure that the virtual screen is maintained even when the Moonlight is shut down? I don't like that the virtual screen driver is turned off and on.
The text was updated successfully, but these errors were encountered: