[spacedesk Lea]

Hi @multi-cat,
Ah I see.. currently spacedesk can only send one keyboard input at a time, it does not support entering words as a single input.

As for the disconnection issue upon entering special characters, we tried to reproduce it here but so far we are not successful.
To further analyze this issue, could you please download the spacedesk diagnostic script here, then extract it.
https://www.dropbox.com/s/z8h5llgi8c2ig3g/2021_spacedeskDiagnosticTool.zip?dl=0

Inside you will find spacedeskDiagnosticTool.cmd, just right-click it then run as administrator.
This script will start a debug view app to capture spacedesk debug traces.
On step 5 it will prompt you to reproduce the issue (by connecting the viewer app, send keyboard input with emojis or special characters to reproduce the disconnect issue), make sure to do this before pressing any key to continue.
After the script is done, a folder will be created on the same folder as the script file which contains various log files that we need for analysis.
Please right-click it -> Send to -> Compressed (zipped) folder, then attach the *.zip file on your next reply.

[spacedesk Lea]

Hi @xxperditorxx,
unfortunately, there’s no plan to develop spacedesk Server/Driver for Linux operating system.

[spacedesk Lea]

Hi @dah,
I assume it’s currently on desktop extension mode.
And you want to use spacedesk for desktop duplication/mirroring, is that right?

You can easily switch to/from extension to duplication via display settings window.
Just open the Windows Settings -> System -> Display, then on Multiple displays dropdown menu, just select „Duplicate these displays“.

[spacedesk Lea]

Hi @digitalmechanic,
we are glad that it worked on your side.
Thanks for the suggestion, we will take note of it.

[spacedesk Lea]

Hi @multi-cat,
Thanks for the feedback.

Using software keyboard, how do you enter a word?
Isn’t it you have to enter letter by letter?

By the way, could you please try our most recent spacedesk Driver v1.0.10 from our website and check if you get the same disconnection issue whenever you enter these special characters or emojis?

[spacedesk Lea]

Hi @angels11_6, glad to hear that it worked.

[spacedesk Lea]

Hi @brad_sask,
Thanks for the feedback.
By the way, did you try restart the viewer app and reconnect after you switch on/off the rotation lock?

[spacedesk Lea]

Hi @imtek,
Thanks for sending the requested files.
Based on your screenshot, it seems that the spacedesk display is detached.
Could you please click the grayed out display (#1), then attach it by selecting „Extend these displays“ on the Multiple displays dropdown menu below.

[spacedesk Lea]

Hi @edsonluis321,

Please try to disable the 10-bit Pixel Format in the AMD Radeon Software settings
Just open the Radeon Software window, click the Settings icon on the top right side, then “Graphics” -> “Advanced” -> disable the “10-bit Pixel Format” then reboot your primary machine to apply the changes.

[spacedesk Lea]

Hi @matewar,

Is it like an AMD Eyefinity or Nvidia Surround setup?

[spacedesk Lea]

Hi @brad_sask,
Could you please check the rotation lock in your windows tablet’s display settings if its enabled or disabled?

[spacedesk Lea]

Hi @edsonluis321,
This issue is different with the screen noise pattern issue.
This is a known issue with 10bit color format enabled on your Nvidia or AMD Control panel.
Which GPU is currently present on your primary machine? Nvidia or AMD?

[spacedesk Lea]

Hi @angels11_6,
Thanks for the info.
To verify if any OSBase is already removed on your machine, could you please run Command Prompt as admin, then type the command below to check if the any OSBase driver present in your system and if the status is Stopped or Running.

sc query ddmgr
sc query ddkmd

If you get the status Stopped or Running please follow it up with commands:

sc delete ddmgr
sc delete ddkmd

Then reboot your primary machine, then try again with spacedesk.

[spacedesk Lea]

Hi @imtek,
Apologies for delayed feedback.
We are still analyzing what could be the cause of this issue.
This is the first time we have seen it.

Based on the screenshot you sent, only the portion where the task bar does not have this black and white pattern.
The diagnostic logs does not show any indicators that causes this pattern over the screen.

We suspect that there’s a third party app on your machine that is messing up with the connected spacedesk display.
We would like to request for the following:
– take a screenshot of your whole primary machine displays (together with attached spacedesk displays showing the black and white pattern issue) via PrintScreen(PrtSc) key on your keyboard, then paste it on Microsoft Paint app save it and send it to us.
– screenshot of you display settings window while spacedesk is connected and showing the black and white pattern issue

[spacedesk Lea]

Hi @15212442377,
Could you please send us the screenshot of this issue?

[spacedesk Lea]

Hi @digitalmechanic,
Ah yes, with the latest spacedesk driver it’s a bit different now.
First, FYI the current spacedesk Driver now supports actual touchscreen input for the first viewer app only, and if you connect another viewer app it will fall back in using the old mouse touch input that you want to use.

This is the new workaround if you still want to use the mouse touch input instead of actual touch screen input.
– connect your viewer app first
– open the device manager then click “View” tab “Device by connection”
– go to spacedesk Virtual Bus and expand it
– initially you will find spacedesk Mouse and spacedesk virtual HID Device (HID Keyboard Device)
– try to send a touch input from your viewer app and you will find another spacedesk virtual HID Device with HID-compliant touch screen underneath
– Just right-click disable both spacedesk virtual HID Device and HID-compliant touch screen underneath it
Then you will notice on your next touch input it will now use the mouse touch input.

[spacedesk Lea]

Hi @angels11_6,
Thanks for sending the diagnostic logs.
It seems that you have an OSBase display driver on your primary machine.
There’s a possibility that it’s causing a conflict with spacedesk.
Are you using any USB display software while trying to connect a spacedesk? Or any similar software like spacedesk?

[spacedesk Lea]

Hi @multi-cat,
Did this message show up upon two-finger touch gesture to invoke the software keyboard?

[spacedesk Lea]

Hi @doombug90,
Thank you very much for reporting this issue.
We have confirmed the same issue on our side.
We will get back to you as soon as we have a fix for this issue.

[spacedesk Lea]

Hi @galo,

So the initial problem is that your android tablet cannot discover your Windows 10 computer, right?
Do you maybe have VPN (Virtual Private Network) active?
Do you have any third party firewall software that might probably blocking the spacedesk connection?
If yes, please make sure to add c:\Windows\system32\spacedeskService.exe on your exception list to allow incoming/outgoing connection.

For assistance, please also check Troubleshooting – Network Connection chapter in our user manual.

[spacedesk Lea]

Hi @baran,
Does your primary machine and tablet device connected on the same local area network?
Do you maybe have VPN (Virtual Private Network) active?
Do you have any third party firewall software that might probably blocking the spacedesk connection?
If yes, please make sure to add spacedesk or „c:\Windows\system32\spacedeskService.exe“ on your exception list to allow incoming/outgoing connection.

For assistance, please also check Troubleshooting – Network Connection chapter in our user manual.

[spacedesk Lea]

Hi @brad_sask,
Are you using the windows viewer app from Microsoft Store?
With current viewer app, display rotation is not yet being handled automatically.
What is the current display orientation of your windows tablet?

I can fool the tablet by setting it as portrait (flipped) but the display resolution appears wonky.

Can you send us the screenshot of this?

[spacedesk Lea]

Hi @angels11_6,
The zipped file you sent does not contain the diagnostic logs (debugview.log, *.etl logs, etc..) that we need for analysis.

[spacedesk Lea]

Hi @timothyber,

Thanks for reporting this issue.
Are you using the most recent spacedesk Driver and Viewer version?
We will check and try to reproduce it on our side.

What is the current quality/performance settings on your android viewer app?
Can you please tell us the current encoding type, custom fps and rendering color depth values?

Could you also please try to enable the auto-reconnect option on android viewer settings and check if it will help?

[spacedesk Lea]

Hi @jiachenzeng,

Currently multi-touch is not yet supported.
This is already in our feature list to be implemented but has low priority at the moment.

Are you using the spacedesk Windows Viewer from Microsoft Store?
If yes, you will be able to zoom in/out the screen via mouse scroll by enabling the scale feature in viewer’s settings -> display -> view transformation.

[spacedesk Lea]

Hi @lauren-wadyko,

Thanks for sending an updated diagnostic logs.
It’s confirmed that our spacedesk Graphics Adapter is crashing due to TDR(Timeout detection and recovery).
This usually happens if there’s any 3D app conflicting with our driver.
Do you have any other 3D application running while trying to connect a spacedesk viewer?
Any screen recording app, 3D games running?

Could you please right-click the spacedesk tray icon (in the task bar’s notification area) then select „Clear All Display Settings“, then try again with spacedesk.

[spacedesk Lea]

Hi @morris202,
spacedesk supports multiple viewer connection (up to 16 viewers) using our native viewer apps (Android/iOS/Windows). As long as your primary machine’s resources (GPU/CPU/Network) can handle it.
As for connection over another network, unfortunately it’s not possible.
spacedesk only supports connection over the same local area network.

• Diese Antwort wurde geändert vor 3 Jahren, 4 Monaten von spacedesk Lea.

[spacedesk Lea]

Hi @lauren-wadyko,
Ok, thanks for the feedback. Please try to reboot your primary machine then try again to run the diagnostic script.

[spacedesk Lea]

Hi @lauren-wadyko,
Thanks for sending the diagnostic logs, but we cannot find the important traces in the logs.
Are you sure that you tried to reproduce the issue on Step 5 before you continue the script?

Do you have the in-game overlay enabled on your Nvidia GeForce Experience settings?

[spacedesk Lea]

Hi @angels11_6,
OK, thanks for answering the questions.
Could you please send us again the updated diagnostic logs?

[spacedesk Lea]

Hi @eloy,
Thanks for sending the diagnostic logs.
Based on your dxdiag info, your Intel graphics adapter on your primary machine is an old version with WDDM 1.1 model.
Desktop duplication of primary monitor to other displays is disabled in Windows display settings of Windows 10 with old version of graphics adapter (< WDDM 2.0). Please try to update your Intel driver version from their official website or maybe go to https://www.intel.com/content/www/us/en/support/detect.html

[spacedesk Lea]

Hi @lauren-wadyko,
Thanks for your detailed input.

It seems like our spacedesk display driver is crashing, possibly a TDR(Timeout detection and recovery).
I’ve noticed an error code 43 on our spacedesk Graphics Adapter (you can also verify it on device manager).

Do you have the in-game overlay enabled on your Nvidia GeForce Experience settings?
Your NVIDIA GeForce RTX 3070 graphics driver is a few months outdated. Please download the latest driver from their website.
https://www.nvidia.com/Download/index.aspx

To further analyze this issue, please download the spacedesk diagnostic script here, then extract it.
https://www.dropbox.com/s/z8h5llgi8c2ig3g/2021_spacedeskDiagnosticTool.zip?dl=0

Inside you will find spacedeskDiagnosticTool.cmd, just right-click it then run as administrator.
This script will start a debug view app to capture spacedesk debug traces.
On step 5 it will prompt you to reproduce the issue (by connecting the viewer app and wait for the issue to happen), make sure to do this before pressing any key to continue.
After the script is done, a folder will be created on the same folder as the script file which contains various log files that we need for analysis.
Please right-click it -> Send to -> Compressed (zipped) folder, then attach the *.zip file on your next reply.

Looking forward to your feedback.
For further questions and/or discussions, please don’t hesitate to contact us.

[spacedesk Lea]

Hi @paul16,
Thanks for the feedback.
For now, we are still investigating what might be the cause of Code 31 on our driver on your machine.
We tried to reproduce it here with the same operating system (Windows 10 x64 for Workstations) and so far it’s working properly on our side.
We are not sure if this will help, but maybe you can also try to open Windows Settings -> Update & Security -> Troubleshoot -> Additional Troubleshooters, then run the troubleshooter for:
— Windows Update
— Program Compatibility Troubleshooter (then select spacedesk SERVER)

[spacedesk Lea]

Hi @louisdio,

Yes, this is currently a known incompatibility issue with spacedesk.
If any screen recording/in-game replay from AMD or Nvidia is enabled, spacedesk will not work properly and you will probably observed a screen flickering for a few times.
For now, we suggest to turn off this feature before connecting spacedesk.

[spacedesk Lea]

Hi @luckyidk,
Does it work now on your side?

[spacedesk Lea]

Hi @angels11_6,

Thanks for the info.
Is there any issue on spacedesk discovery on your side?
Based on the debugview log file you sent, the viewer were able to connect to the server’s IP address properly, it’s just that the server detects an incompatible display hook driver on your priamry machine which is the cause of display off status on your side.

Were you able to remove/uninstall the incompatible display driver detected by the spacedesk server?
Please confirm if you have splashtop WiredX display or Duet Display software on your primary machine.

[spacedesk Lea]

Hi @e2th,
Could you please further describe the setup and the rotation issue on your side?
What is your current viewer type? Android/iOS/Windows?
Which desktop mode are you using with spacedesk client? Is it duplication or extension mode?
Have you tried manually setting the display orientation via display settings window ?

[spacedesk Lea]

Hi @ew05yjs,
Thank you very much for your feedback.
We might consider the localhost connection on Windows viewer app in the future, but not anytime soon.
We cannot prioritize it at the moment as we are very busy with higher priority tasks.

For now, you can only use HTML5 viewer for localhost connection.

By the way, if we understood your reasoning correctly, does our spacedesk driver worked in a remote session?
Did you not encounter any display driver issue?

[spacedesk Lea]

Hi @luckyidk,
Did you notice any error notification on your primary machine upon connection attempt?
Do you maybe have splashtop WiredX display on your primary machine? If yes, please uninstall the virtual display on it’s advanced settings.

[spacedesk Lea]

Hi @angels11_6,
Thanks for sending the debug view log.
Based on the log file, you have incompatible display driver detected by spacedesk server.
Do you have splashtop WiredX display on your primary machine?
If yes, please uninstall the virtual display on it’s advanced settings.

[spacedesk Lea]

Hi @parasite,
Thank you very much for the feedback.
Current spacedesk is using JPEG (CPU) compression, that explains why spacedesk consumes CPU load.
We are actually planning on supporting H264 (GPU encoding) soon for performance improvement.
We don’t have a specific date of availability yet.

[spacedesk Lea]

Hi @twhaas,
Thanks for sending the diagnostic files.
Based on the registry file, you have video wall enabled.
Touch inputs currently does not work if video wall is enabled.
Please disable it then touch should work.

[spacedesk Lea]

Hi @djgab,
If you are trying to connect to your localhost then it will not work.
Connecting a Windows viewer app from the same primary machine is not supported.
You can only connect a Windows Viewer from another secondary machine to your primary machine.

If you want a local host connection, you can only do that using spacedesk HTML5 Viewer which operates thru web browsers.
Just open a web browser on your primary machine (e.g. Google Chrome) the go to http://viewer.spacedesk.net/, then try to connect to its own IP address.
Please keep in mind that spacedesk allows only 1 HTML5 viewer connection at a time.

[spacedesk Lea]

Hi @lobster,
Thank you very much for the info.
This is noted.

[spacedesk Lea]

Hi @fred,
Do you maybe have Nvidia ShadowPlay / screen recording / Instant replay enabled?
If yes, please disable it before connecting spacedesk.

[spacedesk Lea]

Hi @paul16,
Thanks for checking.
Next, please try this:
– run Command Prompt as Administrator
– type the command: REG ADD HKLM\SYSTEM\CurrentControlSet\Services\spacedeskService /v InstallOnBus /t REG_DWORD /d 1 /f
– run services.msc, find spacedeskService and Restart it
– then try to connect again with spacedesk

[spacedesk Lea]

Hi @m-n-c-games,
Did you notice any error notification on your primary machine upon connection attempt?
Do you maybe have splashtop WiredX display on your primary machine? If yes, please uninstall the virtual display on it’s advanced settings.

For further analysis, could you please run dxdiag.exe on your primary machine, click „Save All Information“, then attach the output file (dxdiag.txt) on your next reply.

[spacedesk Lea]

Hi @martinnitro,
We are glad to know that you were able to fix the connection issue on your side.
In case you encounter other spacedesk issue, just let us know.

[spacedesk Lea]

Hi @kjstech,

Thank you very much for your feedback.
Can you please try to enable the Settings -> Display -> „Keep display on“ option on Windows 10 Viewer, and check if it helps?

[spacedesk Lea]

Hi @yusuf,

Can you try to click the Settings -> OFF of the spacedesk Server window then check if you can run the display settings window now?
For further analysis, could you please run dxdiag.exe on your primary machine, click „Save All Information“, then attach the output file (dxdiag.txt) on your next reply.

[Autor]

Beiträge