Virtual display on cold boot isn't only display

[Wordsmith9091]

Bug Symptoms

I'm currently on 1.9.1. Typically, the first thing I do when I'm about to start a gaming session is use my phone to launch the virtual desktop, so that I can do the Windows login with my phone's keyboard.

I've noticed recently (though it's possible the behavior predates 1.9.1) that when I do, I'm getting a black screen If I'm coming from a cold boot, rather than a logged-in-but-locked Windows session. I can still input my pin, and it logs in, but the display I'm seeing at that point isn't the primary or only display, even though I have "exclusive" set in the client page, the app page and the general configuration page. It appears to be the "third" displayt (after my two physical monitors on the host).

Once I log out and start a new session, whether with "virtual desktop" or a game, the virtual display is the sole display, as expected.

Expected Behavior

See the Windows login screen on the virtual display, with all physical displays disabled.

Windows Version

25H2

Logs (Optional but Recommended)

No response

Screenshot (Optional)

[Nonary]

I believe this has been fixed in vibeshine just hasn't been backported to Vibepollo yet.

[Nonary]

Should be fixed in latest release

[Wordsmith9091]

It seems ... sort of fixed, sort of not. With 1.9.3, sometimes I get the Windows login screen streamed and sized to my client (typically my phone), as expected.

Sometimes I get the black screen until I interact with it by using the touchscreen, and then I get the Windows login screen, but in 16:9 ratio. even though I'm using my phone in portrait mode. I can log in, and sometimes it immediately disconnects (which was a behavior I saw on OG Apollo as well on Windows login). Sometimes it doesn't, and when it doesn't, I can go into Windows display settings and see that the virtual display exists but is turned off, and it's streaming my usual primary physical displays.

If I disconnect and reconnect, I then get the virtual display as enabled (and as the only enabled display) as expected.

[Nonary]

Actually I know why that happens, it has to do with how Windows handles dual monitors that are not primary when at the lock screen. They'll actually be blackened out until you wake them up with a click or tap. And yeah this only happens from cold starts, or log outs.

My main concern was that if I apply display profile settings at the System account, it would impact all user accounts on the computer and potentially cause the virtual screen to get stuck when returning back to the PC.

So I need to figure out some way of being able to apply a System level profile, but also in a way where if the user came back to the PC they wouldn't need to fumble around with Windows+P key because the display got stuck on the virtual configuration.

So it might be a few days before I can come up with a solution on that, if its even possible.

[Wordsmith9091]

Thanks for your attention to it. It's definitely not an experience-breaking issue though. As long as I can log in, I'm good!

[Nonary]

After more research I think I can apply display profiles at SYSTEM as long as I do not save to database, so on v1.10.3 (just released) I am now applying display settings at the login screen should hopefully fix that issue.

[blitz2kx]

Just popping in to say im having this issue too. I have SudaVDA set, but on cold boot login screen shows black screen (not main display). I have to login from another app, at PC, or temporarily set VibePollo to use a physical display to get past login.

Dont think this was an issue before, but having this problem on latest build.

[Wordsmith9091]

You may find that if you interact with that black screen (touching it on the phone, in my case) it'll actually show the display at that point.

[Nonary]

Profiles are being applied at System now, the only cause for black screens are if you've selected a virtual screen mode that is not primary or exclusive. As windows 11 intentionally blacks out dual monitors and shows the log in screen only on the primary one, until you click on it.

[Nonary]

Closing out as profiles apply at system level now