Frequently Asked Questions¶
How does Looking Glass work?¶
This YouTube video featured created by the author features a detailed explanation:
Can I feed the VM directly into OBS?¶
Looking Glass now features a functional OBS plugin, which acts as another Looking Glass client, but instead feeds the captured frames into OBS.
Why is my UPS (Updates Per Second) so low?¶
There are several reasons why this can happen, the most common are your capture resolution, or refresh rate. The windows capture methods currently struggle to capture high resolutions under certain circumstances.
Some titles do some strange things at early initialization that cause capture performance issues. One such title is the Unigine Valley benchmark where the capture rate is limited to 1/2 the actual rate. For an unknown reason to both myself and the Unigine developers a simple task switch (alt+tab) in and out resolves the issue. This is not a Looking Glass bug.
Is my GPU supported?¶
Your guest GPU almost certainly supports DXGI. Use DxDiag to confirm that you have support for WDDM 1.2 or greater.
The server-side (guest) probing error “Capture is not possible,
unsupported device or driver” indicates NVidia duplication has failed,
not that DXGI has failed. You can fix the error by specifying
Why do I need Spice if I don’t want a Spice display device?¶
You don’t need Display Spice enabled. Looking Glass has a Spice client built in to provide some conveniences, but you can disable it with the “-s” argument.
Without Spice, Looking Glass cannot send mouse/keyboard input to the guest and clipboard synchronization is disabled.
Where is the host application for Linux?¶
The “Windows host application” is actually the display server, which
runs in the guest VM. The only thing that needs to run in your Linux
host OS is the
You can build a version of the host for Linux as well.
Why is there no title bar on GNOME? / Why can’t I resize the window on GNOME?¶
This happens because GNOME on Wayland doesn’t support the standard protocol for server-side decorations, and Looking Glass doesn’t implement its own decorations.
You can then build the the client with libdecor support by passing
An alternative solution is to hold down the Super key (Windows key on most keyboards), then right click Looking Glass. This should bring up a menu, which will allow you to move the window and resize it.
Libdecor support is provided for the convenience of our Wayland users on GNOME, however it is not a priority feature and may break, please seek alternatives if you require stable operation.
The mouse is jumpy, slow, laggy when using SPICE¶
Please be sure to install the SPICE guest tools from https://www.spice-space.org/download.html#windows-binaries.
The mouse position is wrong when entering the window¶
This is due to windows mouse acceleration, it can be disabled by following one of these methods:
Disabling pointer precision (Control Panel > Mouse > Pointer Options > Uncheck Enhance pointer precision)
By changing the acceleration behavior with the following registry magic: http://donewmouseaccel.blogspot.com.au/2010/03/markc-windows-7-mouse-acceleration-fix.html (Contrary to the title this works just fine on Windows 10)
The cursor position doesn’t update until I click¶
Make sure you have removed the Virtual Tablet Device from the Virtual Machine. Due to the design of Windows, absolute pointing devices break applications/games that require cursor capture, and as such Looking Glass does not support them.
Looking Glass does not support audio routing. The preferred solution is to pass through QEMU’s audio to your host’s audio system.
Another popular solution is to use Scream, a virtual sound card which pipes audio through the network. A guide for setting up scream is available on the wiki: https://looking-glass.io/wiki/Using_Scream_over_LAN
NvFBC (NVIDIA Capture API) doesn’t work¶
NvFBC is only supported on professional-grade GPUs, and will not function on consumer-grade cards like those from the GeForce series.
If you have a supported card, you can enable NVFBC by adding the following
to the host ini file, found at
%ProgramFiles%\Looking Glass (host)\looking-glass-host.ini
(create one if it doesn’t exist):
The screen stops updating when left idle for a time¶
Windows is likely turning off the display to save power, you can prevent
this by adjusting the
Power Options in the control panel.
Where is the log?¶
The log file for the host application is located at:
%ProgramData%\Looking Glass (host)\looking-glass-host.txt
You can also open the log file by right clicking on the Looking Glass system tray icon, then clicking Open Log File. This opens the log file in Notepad.
The log file for the looking glass service is located at:
%ProgramData%\Looking Glass (host)\looking-glass-host-service.txt
This is useful for troubleshooting errors related to the host application not starting.
High priority capture using DXGI and Secure Desktop (UAC) capture support¶
By default Windows gives priority to the foreground application for any
GPU work which causes issues with capture if the foreground application
is consuming 100% of the available GPU resources. The looking glass host
application is able to increase the kernel GPU thread to realtime
priority which fixes this, but in order to do so it must run as the
SYSTEM user account. To do this, Looking Glass needs to run as a
service. This can be accomplished by either using the NSIS installer
which will do this for you, or you can use the following command to
Install the service manually:
To remove the service use the following command:
This will also enable the host application to capture the secure desktop which includes things like the lock screen and UAC prompts.
Why does the host require Administrator privileges?¶
This is intentional for several reasons.
NvFBC requires a system wide hook to correctly obtain the cursor position as NVIDIA decided to not provide this as part of the cursor updates.
NvFBC requires administrator level access to enable the interface in the first place.
General capture performance is boosted by taking advantage of high priority scheduling with SYSTEM level privileges.
NvFBC (NVIDIA Frame Buffer Capture)¶
Why can’t I compile NvFBC support into the host?¶
You must download and install the NVidia Capture SDK. Please note that by doing so you will be agreeing to NVIDIA’s SDK License agreement.
Why doesn’t Looking Glass work with Scream over IVSHMEM?¶
Using IVSHMEM with Scream may interfere with Looking Glass, as they may try to use the same device.
Please do not use the IVSHMEM plugin for Scream. To fix this issue, use the default network transfer method. The IVSHMEM method induces additional latency that is built into its implementation. When using VirtIO for a network device the VM is already using a highly optimized memory copy anyway so there is no need to make another one.
If you insist on using IVSHMEM for Scream—despite its inferiority to the
default network implementation—the Windows Host Application can be told
what device to use. Edit the file
%ProgramFiles%\Looking Glass (host)\looking-glass-host.ini,
(create one if it doesn’t exist)
then, you can add the
os:shmDevice option like so: