Editing FAQ
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 7: | Line 7: | ||
https://www.youtube.com/watch?v=U44lihtNVVM | https://www.youtube.com/watch?v=U44lihtNVVM | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=== Why is my UPS (Updates Per Second) so low? === | === Why is my UPS (Updates Per Second) so low? === | ||
− | There are several reasons why this can happen, the most common is your capture resolution. At the time of this writing, the windows capture methods struggle to capture high resolutions under certain circumstances, as a general rule of thumb anything greater | + | There are several reasons why this can happen, the most common is your capture resolution. At the time of this writing, the windows capture methods struggle to capture high resolutions under certain circumstances, as a general rule of thumb anything greater then 1200p (1920x1200) starts to suffer from performance issues. |
Another cause can be how the game or application you are running is configured. Because of the way windows integrate with the WDM (Windows Desktop Manager) running applications in "Full Screen" mode may in some cases cause a large performance penalty. Try switching to windowed full-screen mode, the difference in performance can be like night and day. Titles known to be affected by this are Fallout76, The BattleField Series and SCUM. | Another cause can be how the game or application you are running is configured. Because of the way windows integrate with the WDM (Windows Desktop Manager) running applications in "Full Screen" mode may in some cases cause a large performance penalty. Try switching to windowed full-screen mode, the difference in performance can be like night and day. Titles known to be affected by this are Fallout76, The BattleField Series and SCUM. | ||
Line 28: | Line 20: | ||
The server-side (guest) probing error "Capture is not possible, unsupported device or driver" indicates NVidia duplication has failed, not that DXGI has failed. | 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 make the error go away by specifying "-c DXGI" | You can make the error go away by specifying "-c DXGI" | ||
− | + | 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. | 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. | ||
− | Note that without Spice, you will not be sending mouse/keyboard events to the guest | + | Note that without Spice, you will not be sending mouse/keyboard events to the guest. |
− | + | 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 `looking-glass-client` application | 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 `looking-glass-client` application | ||
− | == Mouse | + | == Mouse Issues == |
− | |||
− | + | === The mouse doesn't stay aligned with the host. === | |
+ | This is due to windows mouse acceleration, it can be disabled 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 | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Some other things to try: | Some other things to try: | ||
Line 83: | Line 41: | ||
=== The cursor position doesn't update until I click === | === 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. | 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. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |