Closed schw4rzlicht closed 8 months ago
Same issue for me. Logs don't seem to show much. There does seem to be a connection being made.
I tried connecting without QUIC using web sockets instead and through the browser but got the same result.
RDP and Parsec work (with correct ports being opened)
I did not have the time to go over the registry entries for DCV though. Maybe something is not happening during the installation.
So I think there is an issue with the registry entries in the cds/lib/base.ts file based on the last commit.
I tested on the g5 and g4ad and the issue was the same.
On the g4ad instance registry entries, I commented out target-fps, enable-q, frame-queue-weights and connectivity-console-session. I also added back automatic-console-session.
I basically rolled back the last commit for that block of code but kept the quic entry.
With that, I was able to connect with quic.
I assume all those regedits are for performance tweaks and improvements but not sure which one is causing the issue.
Hi @schw4rzlicht,
thanks for raising this. @Seblat5ch, seems that regression was introduced in by your commits - can you please have a look at it?
Hi, I will take a look at this. I think it is because of the latest version of NiceDCV. Let me test this and ether hard code the NiceDCV version or something else.
This did the same thing on my end. What I had to do was uninstall NiceDCV Server and NiceDCV Virtual Display Driver which were preinstalled on my remote machine. I reinstalled them and this fixed the issue.
Hey there,
I was following along the readmes and got everything working - but DCV. I am trying to connect with the macOS client but I don't see anything besides the loading screen.
Sometimes I hear a windows chime that must come through DCV but nothing else. Logs have only info messages but nothing else.