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.
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
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.
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?
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.
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.
Hi,
Is it possible to use Spacedesk on a computer through Windows Remote Desktop ?
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?
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.
Lütfe yardım edin tabletde baktım olmuyo hiç bir sunucu gözükmüyor nasıl yapıcam
Boa Tarde!
Instalei server no meu Windows 10 64bits;
Instalei space no meu Galaxy Tab A10;
Meu computador não aparece no tablet mesmo estando na mesma rede.
Tentei inserir meu ip manualmente mas ele fica “IP-Validation in progress…” e não conclui nunca.
Dai através do SmartView e da conexão do Windons 10 apos eu espelhar o tablet no notebook apareceu o notebook no spacedesk do tablet com ip diferente do que aparecia no server.
Quando eu conecto eu clico no tablet pra conectar ele fica alguns segundos e em seguida desconecta e aparece a seguinte mensagem de erro:
Disconnected by server error
Error Code: 2-5-6
Error Info 0-5-8
Connected time: 00:00:41
Pode me ajudar por gentileza.
-
该话题由Galo 于 3年、 2月前 修正。
Hello there!
I would like some help with regards to my iOS keyboard I’m using for input into a PC over Spacedesk.
I’m using a Brydge Pro Max+ Keyboard (iOS) connected through Bluetooth to my iPad (not pc)(see link):
https://www.brydge.co.uk/products/brydge-12-9-max-plus (very similar to magic Keyboard).
General input for letter keys and numbers works just fine, however, TAB, SPACEBAR, ENTER, BACKSPACE and ARROW KEYS don’t seem to register. I’m assuming it is because this is an iOS keyboard that the PC doesn’t recognize fully.
How can I make them work? Is there a way to map the keys or make it work? Is there a method to emulate or anything like that? I feel like I am so close to having an iPad as my main screen to my PC, but these keys don’t work and it’s a bit of a disappointment.
Can anyone help me with this issue? Is there a way I can make it work?
Kind regards,
V
when I use the software keyborad on my phone ,the software prompts “in order to use the software keyboard input feature for your spacedesk server please install at least spacedesk driver version 0.9.61 for windows 10!”
the driver on Android version is 0.9.74,and on windows 10 is the least version 1.0.9
please tell me how to use the software keyboard.
OK its a Galaxy Tab-E. And the wifi stops even though its on. I have trouble shot every setting that could make it stop. It omly stops when I am using Spacedesk have a window maximised in the Tablet, and moving the mouse in the Tablet space.
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.
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.
As we had a post on the old forum about Spacedesk on Linux, here it is again 😀
What does work quite good at the moment:
Run spacedesk Msi installer for Windows 7 (seems discontinued) -> works quite well
Spacedesk UWP/Microsoft Store App for Windows 10 -> does not run in Wine.
Maybe @Spacedesk you could still provide a msi for the Linux Users as on Linux the Windows Client using Wine is ways faster than the Html5 one.
HI,
Thanks for getting back to me. Please see my responses below:
“Is there any issue on spacedesk discovery on your side?” Yes, there is an issue as the remote Spacedesk clients can’t connect to the main PC. Please see my previous post with the network diagnostics clearly showing the clients trying to connect and the server not responding
“Were you able to remove/uninstall the incompatible display driver detected by the spacedesk server?” Yes, only the standard Intel/NAVIDA drivers are installed, which according to your website are supported
“Please confirm if you have splashtop WiredX display or Duet Display software on your primary machine.” – Neither of these are installed on the main PC
Any help is appreciated.
Thanks!
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.
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)
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.
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.
everytime i connect i device to my computer with spacedesk and i use my instant replay, the video of the instant replay just start blinking and breaking up
Hi,
Thanks for your response. We’ve investogated this further and Android devices running Spacedesk can’t connect to the main PC. They’re on the same network and both devices can ping each other. We ran a pcap on the main PC and can see the Android Spacedesk trying to connect on UDP/28252 but the server isn’t responding. Please see attached pcap file for your reference. We also checked the main PC and can see it listening on 0.0.0.0:28252 but not on it’s IP address 192.168.1.133;
UDP 0.0.0.0:28252 *:*
UDP 0.0.0.0:49668 *:*
UDP 0.0.0.0:49914 *:*
UDP 0.0.0.0:52061 *:*
UDP 0.0.0.0:53097 *:*
UDP 0.0.0.0:54478 *:*
UDP 0.0.0.0:58413 *:*
UDP 0.0.0.0:59339 *:*
UDP 0.0.0.0:60187 *:*
UDP 0.0.0.0:61075 *:*
UDP 0.0.0.0:61076 *:*
UDP 0.0.0.0:61676 *:*
UDP 0.0.0.0:62728 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:10010 *:*
UDP 127.0.0.1:49670 *:*
UDP 127.0.0.1:59338 *:*
UDP 127.0.0.1:61675 *:*
UDP 192.168.1.133:137 *:*
UDP 192.168.1.133:138 *:*
UDP 192.168.1.133:1900 *:*
UDP 192.168.1.133:5353 *:*
UDP 192.168.1.133:5353 *:*
UDP 192.168.1.133:61674 *:*
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 ?
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?
Hi, i’ve some trouble in configuring spacedesk on a computer that use monitor’s portrait display settings.
It seems that if the computer with spacedesk client has been configured to use portrait display settings is not possible to project server’s monitor correctly portrait rotated
🙈 Thanks.
The two different on/off switches always confused me – spacedesk driver and Video Wall Engine.
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.
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.
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.
Hi @fred,
Do you maybe have Nvidia ShadowPlay / screen recording / Instant replay enabled?
If yes, please disable it before connecting spacedesk.
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
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.
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.
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
Well I found a solution to this.
Make a text file with a .ps1 suffix. This mean it is a Powershell script.
In the file write a line
Start-Process -WindowStyle Minimized SpacedeskServiceTray.exe
Nothing more. Save the file to your disk and create a shortcut of it to your Windows startup folder (usually C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp).
This will start the Spacedesk server minimized. Hope this helps to other people looking for solution.
There are some posts more than 2 years ago complaining that spacedesk Viewer won’t connect to the server running on the same computer (localhost). Despite OP’s various legitimate reason, the answers were always that spacedesk client won’t support connection to localhost and HTML5 viewer is the only way.
Will this functionality never be implemented? My reason to use this functionality is to create a virtual monitor when my laptop lid is closed so that start menus and some apps can render properly in remote session (I use Google Chrome Remote Desktop). Although using HTML5 viewer is viable, it would be very cumbersome to automate the activation and hide the session at background. This app seems very promising to be used as a dummy virtual monitor driver, and it’s such a pity that it can’t just because this functionality lacks.
Hey Lena,
1. I used Regedit and found the spacedeskDisplayUmode key where it belongs.
2. There are no crash files in \Temp. As far as I can tell, spacedesk haven’t crashed at all.
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.
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.
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.
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.
Hey Lea,
I tried this too, but no changes again.
Yes it is the first time i tried spacedesk.
i am having this error so i google the solution and i followed this link and then I did exactly what the article said but it still doesn’t work can anyone help me? these are the ss of the current system drivers.
-
该话题由Dev 于 3年、 3月前 修正。
I have the same problem. I’ve been using spacedesk for months and its worked well with my non-touchscreen laptop running the server and my touchscreen laptop running the client. Just this week though the touchscreen is not responding. I tried the different mouse and touch settings but still nothing. I also tried the client on my Android phone which used to work fine and I get no touchscreen response either.
Hi @paul16,
Thanks for the feedback.
Could you please try this one:
– on device manager, while spacedesk Graphics Adapter has Code 31 please right-click uninstall the device
– run spacedesk MSI installer then click the Repair button
– try again with spacedesk, and check if the issue still persist
By the way, is this the first time you install and try spacedesk?
Hi @cant94,
Using spacedesk Windows Viewer from Microsoft Store, you cannot select a custom resolution bigger than the machine’s native resolution.
However, using the desktop version of spacedesk Windows Viewer (v0.9.30 for Windows 7) downloadable from website, you can set a custom resolution up to 4096×2160.
Please keep in mind that when using the desktop version of the viewer app, some features are not updated anymore compared to features in Microsoft Store version.
Hi @pfield69,
Multi-touch gestures like pinch to zoom is not yet supported on spacedesk Android/iOS viewer app.
Currently, zooming the screen (via mouse scroll) is only supported on spacedesk Windows Viewer app from Microsoft Store.
Hi @paul16,
Thanks for sending the requested logs.
We are currently analyzing it.
Yes, the Code 31 error in our spacedesk driver in device manager was the cause of display off status upon connect.
Could you please try the steps below:
– uninstall spacedesk completely then reboot your primary machine
– open device manager
– click View tab -> Devices by Connection and Show hidden devices
– check on the device list if you can find any hidden spacedesk devices or Unknown devices then just right-click uninstall the device, if you find any.
After the steps above, please try to reinstall spacedesk driver then try again.
Please also check and install any pending Windows update on your settings.