- #WILL VNC CONNECT TO A COMPUTER ASLEEP DRIVERS#
- #WILL VNC CONNECT TO A COMPUTER ASLEEP DRIVER#
- #WILL VNC CONNECT TO A COMPUTER ASLEEP WINDOWS#
Perhaps this is a power-saving feature of 3D graphics processors which activates when no screens are detected, or perhaps this is related to the framebuffer being unaware of the supported output resolutions and so disables access to the GPU for the Windows shell, which causes Windows to revert to software-only rendering or some other reason. I think I've also experienced similar problems when attempting to run applications which depend upon 3D acceleration within a Linux environment using the Wine compatibility layer ( ) I have noticed this issue commonly relates to Java applications when the primary monitor is no-longer attached to the device such as certain laptops which "disconnect" the built-in screen when the lid is shut - corroborated by or workstations when no screens are attached.īased upon the behaviour of applications with and without a monitor attached, a surface level understanding of graphics accelerators ( ), and experiences in the forum posts I've referenced below, I believe the cause of the contentless windows is the result of application dependencies upon either the DirectDraw or Direct3D sub-systems - which interface with 3D acceleration hardware - when the accelerators are disabled as a result of the disconnection of a monitor. browser content or 3D applications / games) are no longer drawn (you cannot see the application)'. This answer expands upon second point 'Window contents that are drawn hardware-accelerated (e.g. But it would most likely have something to do with the energy-saving mode.
#WILL VNC CONNECT TO A COMPUTER ASLEEP DRIVER#
Other graphic card driver settings could help, but we do not know what settings that could be exactly.
#WILL VNC CONNECT TO A COMPUTER ASLEEP DRIVERS#
In theory, it may also help to use a different version of the graphic card drivers or a fixed-resolution monitor driver to solve the black screen problem or the problem with the hardware acceleration. via DVI instead of HDMI, or with another adapter, if one was used).Īlternatively, a dummyplug can also help. It may also help to connect the monitor in another way (e.g. This can be achieved either by the fact that the monitor is always on or by using a monitor that is recognized by Windows even when it’s turned off. The only workable solution here is to prevent the monitor from being not detected. Unfortunately, we cannot do anything against that. In other words, if Windows did not draw anything, TeamViewer cannot grab the screen, so you will only see a black screen. TeamViewer grabs the screen as it is currently displayed.
browser content or 3D applications / games) are no longer drawn (you cannot see the application).ģ) Nothing is drawn anymore (screen is black). There have been 3 cases detected thus far:ġ) Everything works as before, but with minor restrictions on the available resolutions.Ģ) Window contents that are drawn hardware-accelerated (e.g. In this case, the graphic driver shall decide what it wants to do when the monitor is not detected.
Unfortunately, there are some monitors that will only pass their data to the graphic card when they are turned on/have power. The monitor itself does not need any power, as the HDMI / DVI / VGA cable itself provides enough power.
Typically, monitors or notebooks display shall report their data (such as what resolution they support) to the graphic card once they are connected.
0 kommentar(er)
