New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Abnormal display when the remote PC has no monitor turned on #6682
Comments
+1 same issue |
update: |
This issue is common for vnc and sometimes other remote access software. The hardware workaround is to use dumb monitor plugs you can buy - fake monitor plug, that will add fake monitor via hdmi/display port plug. In past I wasn't able to overcome thing becuase its windows and gpu related issue - some gpus wont even post pc on restart/power on if you dont have monitor turn on. But I would gladly see this resolved here. |
it works after installing a virtual monitor driver |
Could you provide name or link for that driver? |
I would like to ask which virtual driver you installed |
Please provide the name of said driver, I have tried many and none work. |
@wbright could you share driver name with us ? |
RustDeskIddDriver_x64 |
I have been using these, which this video explains how to use. |
close this since we have virtual display support now in 1.2.4. https://twitter.com/rustdesk/status/1781263566504653052?t=bnpFjiNHcvgxAvzKTkuciw&s=19 |
Bug Description
If there's no working monitors for the remote, some strange behaviors/glitches occured in rendering some windows.
The behavior: #6551
(Yes, the same, but find the most related reason and it is now reproducible)
How to Reproduce
Expected Behavior
Display normally, like where a monitor connected & turned-on
Operating system(s) on local side and remote side
Windows 11 23H2 (both)
RustDesk Version(s) on local side and remote side
1.2.3->1.2.3
Screenshots
Additional Context
Laptop: ASUS Redolbook14 with AMD CPU, integrated GPU Vega7, Windows11 23H2
Desktop: ASUS Motherboard + AMD 5800X + NVIDIA RTX 3080, Windows11 23H2
The text was updated successfully, but these errors were encountered: