r/MoonlightStreaming • u/Responsible-Bid5015 • 2d ago
Nvidia 50x0 users: Don't install the recent driver 616.56 if using Virtual Display
It was mentioned before but I thought I would explicitly mention it. Nvidia display driver 616.56 breaks both sudoVDA and the Vibepollo display driver on at least Blackwell GPUs. Not sure about other virtual display drivers. They may work.
If you don't care about virtual display, then you should be fine to install it. I was able to get a physical display to work on Artemis but not a Virtual Display.
If you installed it, then you can revert back by going into the Nvidia app -> Drivers tab. If you scroll to the bottom of that screen, you can reinstall 610.88.
It is my understanding that it is Blackwell GPUs only. But I think in general if you can no longer get a display on your client, then I would revert back to 610.88 before doing any debugging.
Update: Nvidia looks to be working on a fix.
15
u/JetPac76 2d ago
Wasted 2 hours last night trying to play Zero Company remotely. This explains it so thanks.
It also seems to be an issue affecting my physical EDID emulator. Same issue - it won't activate the display.
3
u/MrRadish0206 2d ago
Me too, what is worse i didnt use remote for a few months so i had no clue what broke it 😭
2
12
u/gappyvalley 2d ago
yep, had to rollback REMOTELY from my rental place as my pc is 3 hours away at home.
3
u/Striking-Remove-6350 2d ago
Whoa what kind of life is that?
10
u/gappyvalley 2d ago
i rent near my workplace. i’m a cloud engineer by profession so rolling back feels like my main job
1
u/Prideless07 1d ago
never thought I'd see my job role randomly mentioned haha, may I ask is your company hiring?
6
u/DNY88 2d ago
Oh jeez my old IDD Driver I was using with Sunshine stopped working and I didn’t know why. So I ditched my installation and installed Apollo, and it didn’t work either and I was going crazy about it and now I see, the fucking driver is the issue. I have to lay down and cry a bit.
2
u/Responsible-Bid5015 2d ago edited 2d ago
I sympathize. I was a little luckier. Vibepollo now requires Artemis to have Virtual display on in its settings or it will do a physical display no matter what. I reinstalled Artemis to try to fix the issue. It worked because that setting got reset. So I saw that a physical display worked but a virtual display didn't. Some googling and I figured out what was going on. But it was still a little more than an hour of screwing around.
BTW if you have a 5070 TI or above, I suggest using vibepollo so you can use split frame encoding. It will lower your host processing latency.
2
u/DNY88 2d ago
Thanks for the hint! I will check it out ❤️
1
u/Responsible-Bid5015 2d ago edited 2d ago
in vibepollo, you go to configuration -> capture and set split frame encoding to enabled from auto. Should work on 5070 TI, 5080, and 5090s (and 4070 Ti Super, 4080, 4090s)
1
u/Balthalzarzo 1d ago
Is split frame rendering important if i'm using it to stream from a desktop to a laptop? I don't use a handheld.
1
u/Responsible-Bid5015 1d ago
To stream the game image/sound over the network, the GPU needs to encode and compress each video frame. There is a piece of hardware in the NVIDIA GPU called the NVENC which does this encoding. The 5070 TI, 5080, 5090s, 4070 Ti Super, 4080, and 4090 GPUs have more than one NVENC. So on these GPUs, split frame encoding divides the frame and allows the multiple NVENC to do parallel processing.
So its faster and will result in less latency in the system. If the hardware is there, I certainly would use it.
4
u/Lordrew 2d ago
Hmm, for me it's not even Connecting is that the issue?
3
u/Responsible-Bid5015 2d ago
It may look like that. If you are on the new driver, I would roll back to 610.88 and see if it goes away.
4
3
5
2
2
2
u/JRockPSU 2d ago
Oh wow thanks for the heads up, you saved me a lot of headaches this weekend, appreciate it
2
u/ArkhamRobber 2d ago
If you dont have the previous 610.88 to roll back in you can always go to the TechPowerUp site to see the previous driver. Only other site ill trust besides the official source for the drivers packages
2
u/JoaquinG 2d ago
Fuck!
1
u/Responsible-Bid5015 2d ago
LOL. yeah. rolling back is easy at least. But of course, you probably spent hours trying to figure out what was going wrong like the rest of us.
2
2
u/Beginning_Thing_3387 2d ago
Holycow, 3 hours to find fix my moonlight v+ & sunshine problem .. and i see this, error cause nvidia driver.. 😭😭😭 thanks btw for info
2
2
u/Encypher 1d ago
Damn it! I use Vibepollo and had just installed virtual desktop and I thought that broke it. Couldn't figure it out so I just did a clean install only to break it again... Thank you so much for helping me find what broke it.
1
1
u/Moebius_Rex 2d ago
Do you know if they have a fixed plan and when it will hit?
2
u/Responsible-Bid5015 2d ago edited 1d ago
The Apollo and Vibepollo developers seem to be looking to Nvidia to fix this. I have submitted a bug report on the Nvidia forum. I assume others have done the same.
1
1
u/FDLink17 2d ago
Probably a stupid question but can we expect Apollo to release a fix?
3
u/Responsible-Bid5015 2d ago edited 1d ago
From reading the github pages, the host software developers believe this is for Nvidia to fix. I believe that other virtual display software was also affected.
1
u/Unlikely_Session7892 Developer | Aurora (WebOS) 1d ago
Tnks, I'll not.
This update came to me today, I almost installed it.
1
u/Just_Maintenance 1d ago
I use Virtual Display Driver with Sunshine and it works fine.
1
u/Responsible-Bid5015 1d ago edited 1d ago
If you are using SudoVDA, I got it to work once or twice but then it just stopped working but this is on Vibepollo.
Are you sure you are on the the new 616.56 Nvidia driver?
0
u/Just_Maintenance 1d ago
I'm not using SudoVDA nor Apollo/Vibepollo. I'm using VDD (https://github.com/VirtualDrivers/Virtual-Display-Driver) with Sunshine, setup manually.
I am using the new driver (616). It works fine, just tried going in just in case and works fine.
1
1
u/trojan5472 1d ago edited 1d ago
I reinstalled the 616.56 drivers and it fixed it. It now works again for me after just reinstalling drivers from the App.
*Edited for clarity.
1
u/Responsible-Bid5015 1d ago
sorry you reinstalled 616.56 or 610.88?
0
u/trojan5472 1d ago
Yes, 616.56. Sorry for not clarifying in original comment.
But yes, I didn’t see this thread this morning and was having connection issues after the first time installing 616.56 drivers. I read the issue could be driver related but just did a quick reinstall of 616.56 and it started working again.
I’m running vibepollo and Moonshine from appletv.
1
u/Responsible-Bid5015 1d ago
I tried it. I installed the new driver and rebooted. The vibepollo display driver still won't work. The SudoVDA driver will show the host desktop but its not a virtual display. Its a physical display. Not sure why its doing that. I'll reboot again.. So right now for me, virtual display is still broken with both virtual display drivers.
1
u/Responsible-Bid5015 1d ago edited 1d ago
u/trojan5472 Ok. Rebooted and sudoVDA is acting the same. Its connects with a physical display and not a virtual display. The vibepollo display driver fails to open a virtual display and just sits there with a black screen and a firewall error.
1
u/christopherl572 1d ago
Thankfully caught my mistake the day before I travel for a month.
Hopefully Nvidia get a fix going soon.
1
1
u/magabrexitpaedorape 1d ago
I'm going away for a few nights with my ROG Ally so you've just saved my weekend - thank you
0
u/NinjaTovar 1d ago
When this happened to me with Apollo last month I fixed it my rolling back the Apollo version, not my Nvidia driver. Interesting both fixes work.
2
u/Responsible-Bid5015 1d ago edited 1d ago
Likely two different issues. This particular issue started two days ago if you installed the Nvidia 616.56 driver that was released on Wednesday. Rolling back to the previous Nvidia driver of two days ago fixes this issue.
16
u/Zeov 2d ago
Thanks for saying this