[spacedesk Lea]

Hi @flyingmonkey,

We have a previous spacedesk users that verified that MS Flight Simulator does NOT support/recognize touchscreen input in general.
And according to that user, it can only recognize mouse pointer input from a remote display.

We can only suggest either of the following:
1. Use mouse touch which automatically activates on your second viewer connection.
Current spacedesk’s touchscreen only supports in first spacedesk display, so on your first viewer app just activate touch screen first, then connect a second viewer app where you can move your flight simulator app and try to send the mouse touch input from there.

2. Select relative touch input in your viewer app settings (the touch input will behave as mouse pad for your primary machine).

As for Windows calc and MS Edge, it should recognize the remote touch input (absolute).
Are you sure it did not work with these apps?

[spacedesk Lea]

Hi @flyingmonkey,

Thanks for the feedback.
I think the simulator app is not automatically rescaling its user interface everytime there’s a display change event in the primary machine.

Remote touch input from spacedesk Android Viewer app should work.
Did you enable the Touch screen control (with Absolute touch type) in the viewer’s Input Devices settings?

[spacedesk Lea]

Hi @samb2023,
Thanks for the feedback.
If possible, can you provide a short video of this issue?

[spacedesk Lea]

Hi @samb2023,

Have you tried dragging the opened window to the extension display?
Just open the display settings window so that you can see the position of the spacedesk display from your main display then drag the window to that direction.

[spacedesk Lea]

Hi @flyingmonkey,

Ok. Can you quickly check if the display scaling in your main monitor before and after spacedesk connect is always set to 150%?

Also try to reopen the simulator app after spacedesk connect, and check if the offset issue still occurs.

• This reply was modified 1 day, 2 hours ago by spacedesk Lea.

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @rodders1947,

Can you please send us the screenshot of the windowed size spacedesk viewer?
Which spacedesk Windows Viewer are you using? Windows 10 (from Microsoft Store)?
Or the Windows 7 desktop version v0.9.39?

[spacedesk Lea]

Hi @johnliem,

Thank you very much for the feedback.

We are currently investigating this issue and trying to reproduce it.
Can you further describe what is happening?
Does it show black screen in the viewer app upon USB connection?
Can you easily reproduce this issue? Will it eventually work after a few times of USB cable plug-unplug?
Could you please send us the steps on how to reproduce it?

[spacedesk Lea]

Hi @tartiak22,

Thanks for sending the diagnostic logs.
Could you please try with the most recent spacedesk Driver v1057 which we recently released and send us the updated diagnostic logs.
Please 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)
– connect all viewer apps and wait until the disconnect issue happen
– switch Diagnostic Collection OFF
– click Save All Information button (click YES if the message box asks you to restart the console app as administrator)
– spacedesk Driver Console will restart for a few seconds, then proceed by clicking the Save All Information button again
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.

[spacedesk Lea]

Hi @titasbog,
Thanks for sending the diagnostic logs.
Unfortunately, some log files are missing (e.g. spacedeskDiag.txt, Debugview.log, etc.).

Could you please try the most recent spacedesk Driver v1057 which we released today and check if you still get the same issue.
If the same issue persist, please send us the updated and complete diagnostic logs.

[spacedesk Lea]

Hi @flyingmonkey,
Thank you very much for sending the diagnostic logs.
On which display does the offset issue happen?
Is it in your actual main monitor (3440 x 1440)/display 1?
Or is it in spacedesk display connected (display 2 or 3)?

[spacedesk Lea]

Hi @klopeckx,

For further analysis, could you please send us the diagnostic logs for this issue?
– open the spacedesk Driver Console window app by clicking the spacedesk tray icon on your task bar’s notification area
– click the Diagnostics on the left side panel
– 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 (15 sec freeze until it disconnects)
– 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.

[spacedesk Lea]

Hi @mastb,

Thanks for confirmation.
This is actually a Windows behavior. It could also happen in any secondary display not just spacedesk.
Please try the suggestions from this article:

Desktop icons moved from Primary Monitor to Secondary Monitor in Windows 11/10

If it did not help, you can just simply select all the icons on the secondary display and drag back to your main display.

[spacedesk Lea]

Hi @bluescreen_error,
Can you please try the most recent spacedesk Driver v1056 and generate an updated diagnostic logs (via spacedesk Driver Console -> Diagnostics -> Save All Information).
Please make sure that spacedeskDiag.txt will be included in the diagnostic folder.

Hi @ozzymanborn,
Is it a blue screen crash?
Can you please try again with spacedesk installed and save the diagnostic logs?
Just open the spacedesk Driver Console -> Diagnostics -> Save All Information.

PS: Saving all information will take a few seconds, then please send us the whole folder (2023-01-XX-XXXXX-spacedeskRuntimeDiagnostics) 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.

[spacedesk Lea]

Hi @flyingmonkey,

Thank you very much for sending a video clip of the issue.
Are you clicking the Flight Simulator buttons from your primary monitor using the mouse pointer of your primary machine?

Next, could you please send us the following:
1. screenshot of the Windows display settings with spacedesk display connected
2. diagnostic logs while offset issue is happening
To generate the logs, please follow the steps below:
– open the spacedesk Driver Console window by clicking the spacedesk tray icon on your task bar’s notification area
– click the Diagnostics on the left side panel
– 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 mouse pointer offset 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.

[spacedesk Lea]

Hi @mastb,

But, is it still the same user account? with only less number of icons?
Did you notice if the other missing icons were being transferred to your other display (e.g.spacedesk display)?

For analysis, could you please send us the diagnostic logs of your primary machine.
Just connect your viewer app (to reproduce the behavior), then open the spacedesk Driver Console in your primary machine, then click Diagnostics -> “Save All Information”.
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.

[Author]

Posts