![]() ![]() > I am running Windows 10 guest and the screen flickers when something is (re)drawn, On Thu, 11:40:35 +0100 Marius Mikucionis wrote: Versions of packages virtualbox suggests: Versions of packages virtualbox recommends: Versions of packages virtualbox depends on: Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8), LANGUAGE=en_DK.utf8 (charmap=UTF-8) Perhaps this patch can be included in Debian.ĪPT policy: (900, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') * here it forces rendering in WinCmd thread rather than a Main thread. * the CR_RENDER_FORCE_PRESENT_MAIN_THREAD is actually inherited from cocoa backend impl, Void renderspu_SystemVBoxPresentComposition( WindowInfo *window, const struct VBOXVR_SCR_COMPOSITOR_ENTRY *pChangedEntry ) #define CR_RENDER_FORCE_PRESENT_MAIN_THREAD No need to uninstall the “original” VirtualBox and install the self-compiled one. ![]() After recompilation is done, it is actually possible to just replace a single freshly compiled file, VBoxOGLrenderspu.so, which is located in /usr/lib/virtualbox/. The only workaround is to change (comment out actually) a single line in VirtualBox source and recompile it. picture to be shown) before rendering is completed by the client, hence the flickering. With nVidia drivers on the host, a race condition happens, causing buffers to be swapped (i.e. ![]() ![]() One workaround is to disable 3D acceleration, but here I found a better solution: I am running Windows 10 guest and the screen flickers when something is (re)drawn,Ģ) virtualbox guest additions with 3D acceleration enabled.ģ) enabled 3D accelaration in the Windows 10 machine settings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |