Verfasste Forenbeiträge
-
Hi @struct2009,
Theoretically, it should work with the use of an ethernet adapter, But please note that this feature has not been fully tested yet. so it may or may not work on some devices.
Another option that you can try is by using USB tethering on your iPad Pro, provided that the device supports it.
please check the chapter “Troubleshooting -> Network Connection” in the user manual https://forum.spacedesk.netuser-manual/#item_489.FYI: native iOS USB cable support is expected to be available in late 2023.
Hi @squale323,
Did the registry workaround fix we provided work on your side? Are you able to connect your iPad with spacedesk v1.0.73 now?
Regarding your question, We are still not sure about the cause of your PC suddenly switching to IPv6 address only,
Additional information may help in identifying the cause of this Issue. For further investigation, you could send us your diagnostic logs.
just follow the steps below:
– open spacedesk Driver Console -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app if applicable
– switch Diagnostic Collection OFF
– click Save All Information button (if a message box appears, just click No to proceed)
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.Hi @alei69,
comparing different machine and different version makes absolutely no sense and can give no result.
Either you try same version on different machines (usually we only support newest version) or you try different versions on the same machine.
For connection problems on your Windows 11 Enterprise machine, please try the suggestions underneath „Troubleshooting -> Network Connection“ chapter in the instruction manual https://manual.spacedesk.net/NetworkConnection.html
(Maybe third party firewall installed? Maybe VPN active? etc.)
If this does not help, then don’t hesitate to get back tu us again here.Hi @hermivore8151,
please do not step back to an old version! We fixed the bug in the new release of spacedesk Windows Driver. Please upgrade to BETA RC 1.0.73 from our download page http://www.spacedesk.net and let us know if this new version works for you.
Are you upgrading from v1.0.44 to v1.0.70?
Please try to uninstall first the old existing version that is installed on your primary Machine. You can do this via v1.0.44 msi installer (remove) or via the Control panel then try to install the latest spacedesk Windows Driver version.For further assistance, please refer to the chapters “UNINSTALL ON WINDOWS PRRIMARY MACHINE” paragraphs “Uninstall Using .Msi File” (https://manual.spacedesk.net/UninstallUsingMsiFile.html) and “Uninstall Using Windows Control Panel” (https://manual.spacedesk.net/UninstallUsingWindowsControlPane.html).
Hi @el_viejo,
in what way does the high CPU load usually occur? (video streaming/playing a game/etc..).
Can you also tell us what quality settings do you use in your spacedesk viewer? and maybe send us a screenshot/s of the high CPU load you are encountering?For further analysis, please also send us the diagnostic logs of the issue.
Just follow the steps below:
– open the spacedesk Driver Console -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app and reproduce the issue
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.Hi @talakazamadsa,
Thanks for reporting this issue, we will be investigating this on our side.
-Could you please check if there’s a recent *.dmp file found in “C:\Windows\minidump” folder and in “C:\ProgramData\Microsoft\WDF” folder. Just check the most recent one with timestamp today, zip it and send it to us.
-Could you also monitor the spacedeskService.exe’s Dedicated and Shared GPU Memory for any leaks before it crashes? or how high does it get before the crash? just go to task manager > details > right click on the column header > ’select columns‘ and check the Dedicated and Shared GPU memory.For the meantime, here are some things you can try for your game…
1. is your VPN active while playing the game? if so, please try to disable it and restart both programs.
2. try to allocate more system resources for the game by
– running the game > minimize it and go to task manager
> go to the details tab and locate the Valorant.exe > right click on that process and select ‚High‘ under the ’set priority option‘
3. try to recalibrate your in-game settings specifically in the graphics sections..if you are using high settings, try to use medium for all graphic settings.
4. check again for any pending driver update in Nvidia.
