Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Can't use real display after closing Moonlight #277

Open
ClementNerma opened this issue Jan 31, 2025 · 12 comments
Open

[Bug]: Can't use real display after closing Moonlight #277

ClementNerma opened this issue Jan 31, 2025 · 12 comments
Assignees
Labels
bug Something isn't working

Comments

@ClementNerma
Copy link

Which OS?

Win11 Pro

Which release?

24H2

Describe the bug

Hi there!

I have a very weird problem going on with the latest release of VDD:

I have a real display (TV) and a fake display (VDD). When I stream the computer's screen to my laptop using Moonlight and the fake display, everything works fine. Then I tell Windows to project only on my main screen in order to use it on my TV.

But when I exit Moonlight, suddenly the TV tells me "no signal". When I go back to Moonlight, I see that Windows decided to only display on the second screen (VDD), the reason being that the first screen is "not active".

So basically, everything works fine until I start close Moonlight, at this point the first screen appears disconnected to Windows.

I don't know why this problem happens.

  • My TV is a 4K HDR screen, plugged into my Nvidia RTX GPU
  • I tried to setup VDD with both the "Auto" and "RTX" GPU options

Steps to reproduce

No response

Expected behavior

No response

Log File

No response

Contact Details

No response

@ClementNerma ClementNerma added the bug Something isn't working label Jan 31, 2025
@DomDussa
Copy link

What i do on my side ( i have an Oled monitor plug to pc and VDD as second screen ).
Go to windows display settings. Make sure to both are detected by windows and select only use screen 1.
That way when you want to be on TV it will always work and when you close you TV it will switch automatically to Screen 2 ( VDD ). When you'll open your tv again windows will remember to only use 1 when will close 2 ( VDD ).

@ClementNerma
Copy link
Author

That's not the problem unfortunately ; the bug appears when I close Moonlight, as Windows considers the first screen to be disconnected. If I'm projecting on the main screen, I can use Moonlight and can see the computer's display both on the TV and on my laptop. When I close Moonlight the TV shows a black screen.

@itsmikethetech
Copy link
Member

Is the resolution being cast to Moonlight different than the Virtual Display's default?

@ClementNerma
Copy link
Author

I don't know what's the default resolution for the display?

Also i forgot to mention another bug: when I use the fake display and stop streaming on moonlight, then start streaming again, the fake displays settings are reset.

I set it to a specific resolution and no HDR, but when I go back it's back to 4K HDR. I don't know why. This is the same settings as my real display (tv) don't know if this is related.

I set the custom EDID option but nothing changed.

@Nonary
Copy link

Nonary commented Feb 5, 2025

Not a bug with VDD, this is just an issue in general with TV Monitors. When the display goes into a deep sleep, it often changes its EDID or become completely offline, making it impossible to restore back to it until you power it up from sleep again.

Fortunately it is easily resolved with a script: https://github.com/Nonary/MonitorSwapAutomation/releases/latest

@ClementNerma
Copy link
Author

ClementNerma commented Feb 5, 2025

The weird thing is that it didn't happen before the december update. It's only since the recent updates that I have this issue.

@Nonary
Copy link

Nonary commented Feb 8, 2025

The weird thing is that it didn't happen before the december update. It's only since the recent updates that I have this issue.

To be fair I hear that with everything in life in general. Like the day I got a call about email encryption stopped working in their phone after they dropped their phone in the hot tub.

@HunterAhlquist
Copy link

I'm having the same problem, I'm not using a TV as a monitor.

@ClementNerma
Copy link
Author

I rolled back to 2023's IddSampleDriver release, configured the option.txt and manually installed the .inf file - it works flawlessly knows (just like before).

It's really an update that causes these issues.

@Nonary
Copy link

Nonary commented Feb 10, 2025

Is it a laptop? Might be just that the old version is attached to igpu which would use quicksync instead of nvenc, more reliable for laptops but has like three times the encoding latency.

There are tricks to get it to work always with nvenc but requires scripting basically.

The newer version of VDD prefers attaching to dGPU which could cause issues with laptop users that do not have the capability to turn off their MUX switch

@ClementNerma
Copy link
Author

No, i'ts a desktop computer, and the integrated graphics are disabled. Plus I manually selected the dGPU during install.

@JDKay2019
Copy link

Hello,

I've got the same issue which I've managed to mitigate by going into the sunshine options and just disabling all auto-device config settings under audio/video.

Now if I want to stream I just turn the monitor off instead of having sunshine/moonlight do it automatically.
Definitely an issue with it though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants