- This topic has 19 replies, 2 voices, and was last updated 4 years, 4 months ago by
.
-
Posts
-
Sorry, my mistake. I was mixing up two different topics. The fact you have to disable hardware decoding on the client side indicates a different issue. I’ll update this topic when I have some news from the developers. For now, please continue to use the workaround that fits your case.
Having “Disable client side hardware acceleration” checked when I connect doesn’t work either, then I have to click the check box twice for the image to appear.
We need to verify that you are referring to the”Disable client side decoding” box in the menu. Do you have to click the check box twice because the little tick doesn’t appear the first time at all?
I’m refering to the checkbox “Disable client side hardware decoding”.
I described two different scenarios:
1. I connect with “Disable client side hardware decoding” unchecked, if I the check it, I notice in the background with the settings menu up, that the screen contents appear. Then I can escape out of the settings menu without saving this change and it works. So just going from unchecked to checked helps me get it working.
2. I try to connect with “Disable client side hardware decoding” checked, but I still get a black screen. I enter into display settings, the change from checked to unchecked doesn’t help, so this time I have to click a second time to get the screen content appear in the background. So even this time going from unchecked to checked helps me get it working.
We’re going to send you a client side package which includes a patch. We’d like you to install this client version and use it to connect as you normally do. Tell us the outcome when connecting.
This topic was marked as solved, you can't post.