[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.

[spacedesk Lea]

Hi @headcloser,

So those nok games giving an error, like they do not recognizing the display, the driver, or smartphone some thing similar to this

Are they giving the same errors?
Did you connect the spacedesk before launching the games?
Or game is already running before connecting the spacedesk?
Are you trying to move your 3D games on spacedesk display for remote viewing?

As for the slow performance and high cpu usage, there are some factors that can cause it:
– if you have a big resolution on your viewer screen (e.g. 1920×1080 – above) spacedesk image compression can consume too much CPU load
– if spacedesk is connected over the wireless network, then routers can cause lags and latency.
Bypassing them always improves performance. Configure Windows PC or Android device as WiFi Access Point (Hotspot) and connect to it before connecting spacedesk.
USB Tethering achieves the same result.
Please check the chapter „Performance Tuning“ in the instruction manual: https://spacedesk.net/user-manual

[spacedesk Lea]

Hi @imtek,

Could you please try to update your Intel(R) UHD Graphics 600 graphics driver from their website.
Or via Intel Support Assistant

If the issue still persist after GPU update, 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 the viewer to show the image 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 @dev,
Do you have splashtop wired xdisplay installed?
If yes, just uninstall the virtual display driver via splashtop agent window -> Advanced window.

• Diese Antwort wurde geändert vor 1 Jahr von spacedesk Lea.

[spacedesk Lea]

Hi @aslcouple

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 try to send touchscreen inputs), 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 @paul16,
Thanks for trying.
Next:
1. Could you please run „regedit“ then navigate to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WUDF\Services
then check if you can find „spacedeskDisplayUmode“ key.
If you cannot find it could you please add it, just right-click the Services -> New -> Key then type „spacedeskDisplayUmode“.

2. Please also send us these app crash dump file/s if it’s available:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C31.tmp.dmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WERFDFD.tmp.dmp
Note: ProgramData folder is hidden by default, if you cannot find it in C:\ directory, just click the View tab of the File explorer, then check the „Hidden items“ check box.

[spacedesk Lea]

Hi @yusuf,
Could you please run devmgmt.msc then check on device manager if spacedesk Graphics Adapter (underneath Display adapters) has error or disabled?
Maybe send a screenshot of the spacedesk Graphics Adapter in device manager.

Then 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.

• Diese Antwort wurde geändert vor 1 Jahr von spacedesk Lea.

[spacedesk Lea]

Hi @martinnitro,
Are both primary and secondary machine connected on the same local area network?
Can you try to ping the IP address of primary machine from your secondary machine (and vice versa) to check if both machines are reachable to each other.
Just run Command Prompt then type the command: ping 192.168.x.x
then check if it will receive a reply from the other machine

By the way, can you also tell us the current network connection type on both machine (wired/wireless/USB tethering/WiFi Direct)?

[spacedesk Lea]

Hi @imtek,
Thanks for sending the screenshot. It’s the first time we saw this kind of issue.
Could you please send us the following info:
Primary Machine
– operating system (Windows 8.1/10)?
– graphics adapter (AMD/Intel/Nvidia)
– network connection type (wired/wireless/USB tethering/WiFi Direct)

Secondary Machine
– Viewer type (Android/iOS/Windows/HTML5)
– network connection type (wired/wireless/USB tethering/WiFi Direct)

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

• Diese Antwort wurde geändert vor 1 Jahr von spacedesk Lea.

[Autor]

Beiträge