Suchergebnisse für '1'

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

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

[angels11_6]

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 *:*

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

[WDD]

I also just lost the ability to use the touch screen on my Android Fire. It has been working fine before. I reinstalled the latest driver on my Windows 10 64 bit PC, and reinstalled the latest app on the Kindle/Fire. I have enabled Absolute Touch on the Fire settings, same as before, but nothing seems to be working. I have the latest NVIDA drivers for my 3060 graphics card.

[parasite]

dear developer:
I’m using this software with my win10 lapptop + ipad pro.when I lanch it,the laptop’s fans will spin very fastly.so I open the task manager,find that gpu doesn’t work and cpu is full running.so this driver is basicly using cpu rather than gpu?But I think gpu encode(nvenc vce or quicksync)is very powerful and easily.so I wanna know why don’t use gpu encode.If it is in the develop plan,when I could use it?
Last but not least,thanks for your development!

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

[M.N.C Games]

when i was try to connect to my laptop i got the coming error
(Dissconnected by server error
Error Code: 2-5
Error Info: 0-5
Connected time: 00:00:01)
pls i need answer

[Fred]

Hello, thanks for helping but the auto-connect was already disabled, I deleted the app and installed the updated version 1.0.9 and nothing changed. It always repeat the unplug sound without connecting the device. I runned that command and I’m posting the results below.

Attachments:

You must be logged in to view attached files.

[Paul16]

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.

[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 @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 2 Jahren, 11 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.

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

Yes, they are connected on the same network. I tried to ping the IP address and the computers are probably not mutually reachable wrote it: 4 sent 0 received 4 lost ( loss 100% ) Otherwise the main PC is connected via Ethernet (cable) and the other computer via Wifi to the same router I tried even wired connection of the device to each other via cabel ethernet.

Thankyou.

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

[spacedesk Lea]

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?

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

[spacedesk Lea]

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.

[Paul16]

Hey Lea,
thanks for your support. Yes i’m using v1.0.9.

The secondary is telling me, that it is connected, but with display off. So there is nothing special to wait for.
I used the debugger like discribed. In addition I restarted the driver in the device-manager while step 5 (with no changes at all, still error code 31).

Hope i’ve done it right.

Attachments:

You must be logged in to view attached files.

[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 2 Jahren, 11 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.

[yfzhao]

By the way, I have updated Spacedesk Server to 1.0.9.

Best wishes!

[yfzhao]

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！

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

[somnus7]

Yes, I am using the latest version – v1.0.42

Understood that this issue is not common. Let me just use the guided access for now as a workaround.

Thanks.

[spacedesk Lea]

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

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

[spacedesk Lea]

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

[spacedesk Lea]

Hi @aoneter12,
Does this issue started to happen right after you install spacedesk on your machine?

[spacedesk Lea]

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.

[spacedesk Lea]

Hi @aoneter12,
Did you already check the custom resolution list on the viewer settings?
What is your viewer app type? Android/iOS/Windows?

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

[aoneter12]

I purchased a new computer in August 2020, and until about a week ago I had no issue with the computer going idle after 15 minutes of being AFK; the monitors dimmed and turned off, my Razer keyboard and mouse turned off their RGB lighting, and all was well. Now, though, none of that happens anymore and I cannot figure out why.

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

[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 2 Jahren, 11 Monaten von spacedesk Marcel.
• Diese Antwort wurde geändert vor 2 Jahren, 11 Monaten von spacedesk Marcel.
• Diese Antwort wurde geändert vor 2 Jahren, 11 Monaten von spacedesk Marcel.