Suchergebnisse für ‚X‘

[lauren wadyko]

I think I reproduced the issue, being that the main problem is it saying „connection failure“ after having the connecting to [IP] screen. I have now turned off the in game overlay, but I’m still experiencing a connection failure. No error message, just „Connection failure. Unable to Connect!“. I have attempted with my phone and gotten the same error (again, after a much shorter period of time.)

I was able to produce an error I haven’t gotten while the diagnostic wasn’t running. Error code 2-5-6-5- and error info 0-5-8-9-, but now I can no longer run the diagnostic tool. I keep getting the error of „Data collector set already exists“, even after deleting the files and re-downloading it. I’m sorry 🙁

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

[tuxinator]

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.

[angels11_6]

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!

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

[lauren wadyko]

I’m trying to use my iPad as a second monitor for my windows pc, but it just shows the „connecting to [my computer’s IP]“ screen for like a full minute or so, and then says there was a connection failure. I think it might be an issue with my computer and not my iPad since I tested it with my phone and got a much faster connection failure, but I’m not very sure about it since everything seems to be set up perfectly fine on my pc (the app is allowed through the firewall, its turned on and refers to my pc as in idle in the driver window, all that.) Its the latest version, I just downloaded it not too long ago today so I don’t think that’s the issue. Both devices are connected to the same wireless network. My computer’s IP shows up in the list of devices I can connect to. I’ve gone through set up guides and as far as I can tell I’ve done everything right, so I’m very confused. Thanks in advance!

While writing this and going through the forms, it connected briefly (for about 57 seconds apparently), showing a black screen and then disconnecting and giving me a server error code. I’ve had it do something like this a few times. The first being error code 2-5-6-5- and error info 0-5-8-9- and lasting 22 seconds, the next being error code 2-5- and error info 0-5- and a connected time of one second, and this last time being error code 2-5-6- and error info 0-5-8-.

Since it seemed like a common troubleshooting question, I do not have Nvidia shadowplay/screen record running. I’ve attached my dxdiag.txt to this for the same reason.

Attachments:

You must be logged in to view attached files.

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

[angels11_6]

Your system didn’t like the pcap file dues security issues?? Weird…
No. Time Source Destination Protocol Length Info
137 2.456935 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
212 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
213 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
214 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
215 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
216 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
242 2.648084 192.168.1.133 192.168.1.123 ICMP 74 Echo (ping) request id=0x0001, seq=22/5632, ttl=128 (reply in 245)
245 2.652214 192.168.1.123 192.168.1.133 ICMP 74 Echo (ping) reply id=0x0001, seq=22/5632, ttl=64 (request in 242)
258 2.662746 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
259 2.663022 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
260 2.663174 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
261 2.663881 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
262 2.663881 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21

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

[DJGAB]

I tried several times to connect the IPv4 address, I’m sure I did everything right, but it gives the same error: “ invalid entry: local host „, can someone help me? Printscreen

[lobster]

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.

[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 3 Jahren, 2 Monaten 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 3 Jahren, 2 Monaten von spacedesk Lea.

[imtek]

The graphics hardware is an intel UHD Graphics 600

Secondary machine 1: Linux over ethernet
Secondary machine 2: Android over wifi

dxdiag.txt file is attached.

Many thanks for your help.

John

Attachments:

You must be logged in to view attached files.

[Dev]

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, 2 Monaten von Dev.

Attachments:

You must be logged in to view attached files.

[kjstech]

Hi, I just had to offer my feedback for this great application.

Even though I’m all Windows 10, I use the Windows 7 client on my two Windows 10 side PCs on either end of my main workstation. It runs all day and in fact its funny, I can log into my grafana and see exactly when I take lunch by looking at the bandwith on my switchports.

I thought, hey these are Windows 10, I see there is a Windows 10 native app. So I tried it, but after 10 or 15 minutes, the viewers go black (to sleep), and I wiggle the mouse and I have to unlock them. This does not happen with the Windows 7 app.

Therefore I will continue to just use the Windows 7 viewer on Windows 10.

[martinnitro]

Hi, where are the problems? I thought that the devices are connected to one network unfortunately but no less I have already fixed it and it works thank you very much for your help.

[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 3 Jahren, 2 Monaten von spacedesk Lea.

[imtek]

Here is one example of the problem. Thanks in advance for your help. John

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

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.

[HeadCloser]

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, 2 Monaten von HeadCloser.

[spacedesk Lea]

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.

[Johncoool]

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

[Paul16]

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.

[spacedesk Lea]

Hi @myron,
These are the binaries we are checking for splashtop virtual driver:
lci_proxykmd.sys
lci_proxywddm.sys

[spacedesk Lea]

Hi @endah,
Thanks for sending the requested files.
But unfortunately, we can only open the dxdiag file.
The 2 setup log files are not the actual files, only a shortcut file.
Please send it again.

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

[spacedesk Lea]

Hi @tihiron,
You can get the older spaacedesk driver v0.9.43 here.

[spacedesk Lea]

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

[spacedesk Lea]

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

[aoneter12]

The resolution set is 1024×768, which is extremely zoomed in and does not look very nice. However, when I go to change the resolution, the box is grayed out and will not let me click on it. Is there any way to fix this issue?

[Johncoool]

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.

[Andrew]

Hi,

I’ve been asked to look at an install running over 15 screens (1080p).

Is there anyone running anything like that who wouldn’t mind sharing their experiences with me?

I was only able to test over 5 screens before I ran out of test kit.

Thanks.

[Myron]

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?

[Myron]

Interesting. I wonder if it is possible to disable the unsupported driver. Where did you find the incompatible driver? Is this something that can be tweaked in the registry to disable it or maybe set the security ACL on the incompatible driver to prevent execution?

[spacedesk Marcel]

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…

• Diese Antwort wurde geändert vor 3 Jahren, 2 Monaten von spacedesk Marcel.
• Diese Antwort wurde geändert vor 3 Jahren, 2 Monaten von spacedesk Marcel.
• Diese Antwort wurde geändert vor 3 Jahren, 2 Monaten von spacedesk Marcel.