Replies: 5 comments 4 replies
-
If you're still not getting any image, please share your system information and I'll try to see what's wrong. |
Beta Was this translation helpful? Give feedback.
2 replies
-
So, I did set the Virtual Display as primary and watched it take over a
couple times before walking away for a few hours. Then when I tried again
and woke the host device up it was back to black screen on the client side.
…On Mon, Nov 18, 2024 at 8:59 AM Yukino Song ***@***.***> wrote:
If you're seeing a black screen on login UI and the virtual display isn't
primary, that's expected. Windows only show login on primary display.
—
Reply to this email directly, view it on GitHub
<#110 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWGIJVIJQUFI2UADY2JIRBD2BIFFFAVCNFSM6AAAAABR5KFSICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMRZGM4TAMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
That is something I was thinking about as well, yeah... I'll need to do a
bit of testing when I get home tonight.
…On Mon, Nov 18, 2024 at 9:53 AM Yukino Song ***@***.***> wrote:
You mentioned that you have two physical monitors, that might cause
problems when one of the goes to sleep/disconnect, in that case the display
configuration changed, so Windows might changed the primary display back to
one of the other physical display that is still awake.
—
Reply to this email directly, view it on GitHub
<#110 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWGIJVO5ZY4KORFSUBSIVDT2BILQHAVCNFSM6AAAAABR5KFSICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMRZGQ2TCMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Ok, I think I solved the problem. After a bunch of failed attempts I was
looking through the logs and noticed that it kept referencing an AMD
Display driver. So I disabled the IGPU in the BIOS and uninstalled the AMD
Adrenaline software. Boom, works like a charm now. It was trying to use the
wrong GPU for the output.
With the multi-monitor aspect I just set screen 3 (virtual display) as the
primary while I was streaming to a client and moved the playnite app over
to that one. Now when I launch things in moonlight it all comes up fine,
even after being asleep. It even picks up the virtual display for me to put
my windows PIN in without issue.
Thanks again!
QuadT
…On Mon, Nov 18, 2024 at 9:55 AM Tony Eccles ***@***.***> wrote:
That is something I was thinking about as well, yeah... I'll need to do a
bit of testing when I get home tonight.
On Mon, Nov 18, 2024 at 9:53 AM Yukino Song ***@***.***>
wrote:
> You mentioned that you have two physical monitors, that might cause
> problems when one of the goes to sleep/disconnect, in that case the display
> configuration changed, so Windows might changed the primary display back to
> one of the other physical display that is still awake.
>
> —
> Reply to this email directly, view it on GitHub
> <#110 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AWGIJVO5ZY4KORFSUBSIVDT2BILQHAVCNFSM6AAAAABR5KFSICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMRZGQ2TCMY>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Yeah, since I'm not using it I'm fine with disabling it. Thanks again!
…On Wed, Nov 20, 2024 at 11:16 AM Yukino Song ***@***.***> wrote:
Ah, in this case you can just set the adapter name to your dgpu, but you
won't be able to stream displays connected to your igpu then. But it seems
you're not using igpu anyway so it should be fine.
—
Reply to this email directly, view it on GitHub
<#110 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWGIJVL2NW2XLCDKDOGWAGD2BTGXDAVCNFSM6AAAAABR5KFSICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZSG4YTENI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Having a weird situation with the 0.2.6-Aplha2 build. First time trying out Apollo so its probably something I'm doing wrong. It appears to install fine and the sudamaker VDA shows up in my device manager but everytime I try to stream to a moonlight device I only get sound and no video. if I turn on my monitor I can see what should be sent to the client device. Any idea what's going on here?
Beta Was this translation helpful? Give feedback.
All reactions