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.
-
Diese Antwort wurde geändert vor 3 Jahren, 1 Monat von
spacedesk Lea.
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.
-
Dieses Thema wurde geändert vor 3 Jahren, 1 Monat von
Dev.
Attachments:
You must be
logged in to view attached files.
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.
Attachments:
You must be
logged in to view attached files.
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.
So, I have no idea so far, but it seems like some of 3d games doesn’t work with spacedesk…
I mean like some of those games are running fine and other not :s
Killing Floor 2 (TRIPWARE INTERACTIVE) ok
The Secret World Legends (FUNCOM) ok
Resident Evil 2 Remake (CAPCOM) ok
Play Club (Illusion) ok
Chronicles of Valkiria (SEGA) partly
the game exe ok, the launcher nok
The Witcher 3 (CD Project RED) nok
Left 4 Dead (Valve) nok
Anybody have got an ideas how to fix rest of games?
PS: So those nok games giving an error, like they do not recognizing the display, the driver, or smartphone some thing similar to this… Another time games are working, but still spacedesk not receiving every frame, so it around 1 frame for 5-10 seconds, very slow, mostly freezes. Usually freaks cpu, and my machine automatically rebooting itself.
-
Dieses Thema wurde geändert vor 3 Jahren, 1 Monat von
HeadCloser.
Hi @paul16,
Did you try our most recent spacedesk Driver v1.0.9?
If the problem still persist with the latest version, 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 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.
By the way, I have updated Spacedesk Server to 1.0.9.
Best wishes!
Hi,@spacedeskLea
I have updated my graphics driver and WLAN driver, either on my laptop (Lenovo laptop with AMD graphics) or on my Surface GO2 (Intel UHD 615 graphics). However the problem remains…
By the way, I found wired connection is OK.(。_。) (through network cable, but not usb cable)
Thanks！
Thank you for the response.
I will be updating this post once I have the results of the newer version of Winlock pro and that way you can have the information in your database. The update will be within 2-4 weeks because it takes time to be sure and accurate.
I have had Winlock for over one year and it did cause some issues with the older versions of the Spacedesk server. So I am not sure why it started happening more frequently with the more recent updates. It could be related to a recent Windows update that changed something in Windows explorer.
The current Winlock Pro version is 6.22 released in 2014.
The new one I will be testing with is version 8.47, released in 2021
Hello Support-Team,
I already searched the toubleshooting page but could not find something similar.
The connection between Primary (PC) and Secondary (IOS) works fine, but without working display. I found an error code 31 in device Manager which seems to cause the problem.
Here is a list of things I already checked:
– Win10 and GPU-Driver(RTX 2070) are latest versions
– Restarted Primary in device-manager and reinstalled spacedesk
– Tested on second IOS, same result
– No splashtop, duet, vpn or similar installed
– Firewalls do not block Spacedesk
Hope you have an idea what causes the problem. If you need anything else, pls let me know.
DXDiag is of course in attachement
Attachments:
You must be
logged in to view attached files.
Do you need any other actions from my side to trigger this?
I’m not sure. This minor issue seems difficult to troubleshoot on our side if we cannot reproduce it.
This is the scenario where the viewer is not failing in any type of functionality, it’s just not auto-hiding the home bar.
Since it’s only happening on your device (no other users so far is reporting this issue), maybe the cause of the issue is only somewhere in the settings of your device.
By the way, what is the current version of spacedesk iOS viewer app on your device? Is it the latest version 1.0.42?
-
Diese Antwort wurde geändert vor 3 Jahren, 1 Monat von spacedesk Lea.
Hi somnus7,
I’m not sure if enabling the iOS device’s Settings -> Privacy -> Analytics & Improvements -> “Share With App Developers” will help.
We only tell our user to enable this for application crash issue so our developer can receive the app logs.
By the way, what is the current version of spacedesk iOS viewer app on your device? Is it the latest version 1.0.42?
-
Diese Antwort wurde geändert vor 3 Jahren, 1 Monat von spacedesk Lea.
Hi @viviane,
Thanks for the feedback.
Currently the only option to improve performance is by eliminating the router.
If your Android tablet supports USB tethering, you can also try that with spacedesk.
If it did not help, then you’ll probably have to wait for our next performance improvement feature.
spacedesk will offer h264 hardware encoding very soon.
Hi @tihiron,
You can get the older spaacedesk driver v0.9.43 here.
Hi @jlbergier,
You can easily switch to desktop extension mode via display settings.
On the multiple displays drop down menu, just select „Extend these displays“.
For assistance, please also check the Configuration and Settings -> Windows PC (Primary Machine) chapter in our user manual https://forum.spacedesk.netuser-manual/.
Hi @aoneter12,
Does this issue started to happen right after you install spacedesk on your machine?
Hi @myron,
Please try our most recent spacedesk Driver v1.0.8 from our website https://forum.spacedesk.net.
Then let us know if the the same issue persist.
Hi @johncoool,
Thanks for the info – apologies for delayed feedback.
I think there’s no need for the dxdiag info to analyze this problem.
It seems that it’s a conflict between WinlockPro and Windows Explorer, we cannot do anything about it on our side.
Hopefully this new version of WinlockPro that you will try will fix its issue with the explorer.
Maybe you can also play around with the WinlockPro settings, I saw that it has various settings.
It probably has a specific settings there that directly affects the Windows Explorer.
By the way, spacedesk non Beta version will be released hopefully within this year.
It will be thru the viewer apps from various App Store (Apple App Store/Google Playstore/Microsoft Store).
The server/driver side will always be free to download (only viewer app will have a pay/Pro version).
I did not receive an feedback yet from the Spacedesk team after my last post a few days ago.
Here are the new updates from me.
I found a newer version for testing of the Winlock pro software and will be testing it over the next few weeks.
I will be updating this post within the next month depending on the new results.
I’ve not managed to nail exactly what’s causing the issue, but several times now when I’ve ended up using an Acer Tablet as a second screen and I’m using the 1.07 server.
The latest issue was that the second display on the Acer Tablet is showing the last image and all input and output is frozen on the screen. Actually, it’s just the static desktop, but I can’t move the mouse pointer into the second screen and the touch input is not responsive. I ended the server program and the Acer tablet didn’t notice that the server had gone off-line.
I could end the Android app and the second screen session normally. No error messages were shown.
If and when this happens again, and it will happen again, just don’t know when, is there a way where I can catch a snapshot of the state of the server on the Windows machine and a snapshot of the state of the app to send to you for investigation.
Is there a watchdog routine on the server and or Android app that would detect if either side malfunctions and if there is, to try capture diagnostic information?
So far the BSOD hasn’t occurred anymore. Regarding the connection, I’ve been using only the WiFi Access Point (Hotspot) since I installed Spacedesk for the first time.
splashtop wired XDisplay virtual display driver can be uninstalled and installed in their „Advanced“ menu option.
Then splashtop wired XDisplay cannot do Windows Desktop Extension any more (only Desktop Duplication / Mirroring).
Then splashtop wired XDisplay can coexist with spacedesk.
Currently splashtop wired XDisplay installs TWO virtual display drivers:
OLD: WDDM Filter Hook Driver (for Windows 10 1511 which is not even supported by Microsoft any more!)
NEW: WDDM IddCx Indirect Display Driver (for Windows 10 1607 and above)
If splashtop only removed their OLD unused virtual display driver (WDDM Filter Hook).
Then wired XDisplay could perfectly coexist with spacedesk and even do Windows Desktop Extension.
splashtop users – please tell them! Send them the link to this thread…
Hi @ertugrul,
Is it the resolution of your laptop monitor? Or spacedesk display?
If it’s spacedesk display, you have to enable the custom resolution in the viewer settings and select from the resolution list before connecting the spacedesk.
Hi @endah,
For further analysis, could you please send us the following:
– run dxdiag.exe on your primary machine, click “Save all information” and save the output file (dxdiag.txt)
– spacedeskSetup.log file located in C:\Users\Public
– setupapi.dev.log file located in C:\Windows\INF
Please save all requested files in one folder, then right-click -> Send to -> Compressed (zipped) folder, then attach the *.zip file on your next reply.
Hi louis3z,
For further analysis, could you please send us the following:
– run dxdiag.exe on your primary machine, click „Save all information“ and save the output file (dxdiag.txt)
– spacedeskSetup.log file located in C:\Users\Public
– setupapi.dev.log file located in C:\Windows\INF
Please save all requested files in one folder, then right-click -> Send to -> Compressed (zipped) folder, then attach the *.zip file on your next reply.
Hi somnus7,
Thank you very much for the positive feedback.
As for the spacedesk iOS viewer app, this seems strange, because on our side with our iPad device, spacedesk viewer screen is always auto-hiding the home bar.
Can you tell further details of your iPad device (e.g. iOS version, model) ?
Hi @viviane,
I assume your spacedesk is connected over WiFi network, is that correct?
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
By the way, does the BSOD upon settings OFF still happening on latest spacedesk version 1.0.8?
<<< Is it in the display settings window? Or spacedesk server menu settings?
Can you specify which settings exactly are you trying to change?
It was the menu Settings: I tried to turn the driver OFF, then it crashed.
<<<< Then try again to click/open the Windows start button.
Problem apparently solved, but pen still too laggy, even with the lowest quality settings all over.
Hi,
I installed spacedesk this morning and it worked perfectly, but when i tried opening it again an error popped up and i couldn’t run the software correctly.
I’ll pin the screen error here: https://prnt.sc/1hm92ex
Hi, @spacedesk Lea
I have updated my windows10 to the latest. And here is the Dxdiag report.
Thanks!!
Attachments:
You must be
logged in to view attached files.
