You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<linkrel="chapter" href="index.html#hd002" title="2 Conventions Used in This Document">
@@ -30,7 +30,7 @@
30
30
<body>
31
31
<aname="#pagetop"></a>
32
32
<divclass="title">
33
-
<pclass="title">User’s Guide for VirtualGL 3.1.3</p>
33
+
<pclass="title">User’s Guide for VirtualGL 3.1.4</p>
34
34
</div>
35
35
<aname="file000"></a>
36
36
<p><em>Intended audience:</em> System Administrators, Graphics Programmers,
@@ -746,7 +746,7 @@ <h2 id="hd005001">5.1 Installing VirtualGL on Linux</h2>
746
746
packages are provided for Linux distributions that contain GLIBC 2.17 or
747
747
later. <br/>
748
748
<divclass="important"><pclass="important">
749
-
If you want to run both 32-bit and 64-bit OpenGL applications with VirtualGL on 64-bit x86 Linux systems, then you will need to install both <strongclass="filename">VirtualGL-3.1.3.x86_64.rpm</strong> and <strongclass="filename">VirtualGL-3.1.3.i386.rpm</strong>, or both <strongclass="filename">virtualgl_3.1.3_amd64.deb</strong> and <strongclass="filename">virtualgl32_3.1.3_amd64.deb</strong>. (<strongclass="filename">virtualgl32_3.1.3_amd64.deb</strong> is a supplementary package that contains only the 32-bit server components.)
749
+
If you want to run both 32-bit and 64-bit OpenGL applications with VirtualGL on 64-bit x86 Linux systems, then you will need to install both <strongclass="filename">VirtualGL-3.1.4.x86_64.rpm</strong> and <strongclass="filename">VirtualGL-3.1.4.i386.rpm</strong>, or both <strongclass="filename">virtualgl_3.1.4_amd64.deb</strong> and <strongclass="filename">virtualgl32_3.1.4_amd64.deb</strong>. (<strongclass="filename">virtualgl32_3.1.4_amd64.deb</strong> is a supplementary package that contains only the 32-bit server components.)
750
750
</p></div>
751
751
</li>
752
752
<liclass="Ordered-1 Ordered" value="2">
@@ -804,15 +804,15 @@ <h2 id="hd005002">5.2 Installing the VirtualGL Client on OS X/macOS</h2>
804
804
<olclass="Ordered numeric">
805
805
<liclass="Ordered-1 Ordered">
806
806
Download the VirtualGL Mac disk image
807
-
(<strongclass="filename">VirtualGL-3.1.3.dmg</strong>) from the
807
+
(<strongclass="filename">VirtualGL-3.1.4.dmg</strong>) from the
<tdclass="standard">The <code>--in-process-gpu</code> option causes Chrome/Chromium to use a thread rather than a separate process for 3D rendering, which prevents it from complaining about the X11 function calls that the VirtualGL Faker makes. The <code>--use-gl=egl</code> option forces Chrome/Chromium to use desktop OpenGL rather than ANGLE, which works around an issue whereby, when using ANGLE, Chrome/Chromium assumes that every X visual has an EGL framebuffer configuration associated with it. <br/><br/> As of this writing, there are no known workarounds that allow Chrome v129 and later to be used with VirtualGL.</td>
2134
+
<tdclass="standard">The <code>--in-process-gpu</code> option causes Chrome/Chromium to use a thread rather than a separate process for 3D rendering, which prevents it from complaining about the X11 function calls that the VirtualGL Faker makes. The <code>--use-gl=egl</code> option forces Chrome/Chromium to use desktop OpenGL rather than ANGLE, which works around the X visual selection issue described below.</td>
2135
+
</tr>
2136
+
<trclass="standard">
2137
+
<tdclass="standard">Google Chrome/Chromium</td>
2138
+
<tdclass="standard">v129 and later</td>
2139
+
<tdclass="standard">Linux</td>
2140
+
<tdclass="standard">Set the <code>VGL_CHROMEHACK</code> environment variable to <code>1</code>, then launch the application with <br/><br/><code>vglrun google-chrome --in-process-gpu</code><br/> or<br/><code>vglrun chromium --in-process-gpu</code></td>
2141
+
<tdclass="standard">Chrome uses ANGLE, an OpenGL ES emulator that translates OpenGL ES function calls into OpenGL, OpenGL ES, or Vulkan function calls. When using ANGLE’s OpenGL back end, Chrome chooses an X visual by sending raw GLX requests to the 2D X server, bypassing VirtualGL. Thus, the X visual it chooses has rendering attributes that are only relevant for the 2D X server’s OpenGL implementation. Chrome then expects to find a GLX or EGL framebuffer configuration to which the chosen X visual is assigned. That will normally never happen when using VirtualGL. <code>VGL_CHROMEHACK</code> works around this issue by emulating Chrome’s X visual selection mechanism and assigning the chosen visual to all GLX and EGL framebuffer configurations that have an 8-bit alpha channel. <br/><br/> When using nVidia’s proprietary Vulkan driver, which does something VirtualGL-like in an X proxy environment, or when using an X proxy that implements the DRI3 X extension, you can also enable GPU acceleration by passing <code>--use-angle=vulkan</code> to <code>google-chrome</code> or <code>chromium</code>. No additional arguments or environment variables are necessary in this case, nor is it necessary to launch the application with <code>vglrun</code>.</td>
<tdclass="standard">MATLAB will automatically use its built-in (unaccelerated) OpenGL implementation if it detects that it is running in a remote display environment. More specifically, it will always enable software OpenGL if the X server has an X extension called <code>VNC-EXTENSION</code>, which is the case with TurboVNC, TigerVNC, and RealVNC. <br/><br/> MATLAB R2025a and later use Vulkan rather than OpenGL, so it is not possible to use VirtualGL with these releases.</td>
2197
+
<tdclass="standard">MATLAB will automatically use its built-in (unaccelerated) OpenGL implementation if it detects that it is running in a remote display environment. More specifically, it will always enable software OpenGL if the X server has an X extension called <code>VNC-EXTENSION</code>, which is the case with TurboVNC, TigerVNC, and RealVNC.</td>
2198
+
</tr>
2199
+
<trclass="standard">
2200
+
<tdclass="standard">MATLAB</td>
2201
+
<tdclass="standard">R2025a and later</td>
2202
+
<tdclass="standard">Linux</td>
2203
+
<tdclass="standard">Set the <code>VGL_CHROMEHACK</code> environment variable to <code>1</code>, then launch the application with <br/><br/><code>vglrun /usr/local/MATLAB/<em>version</em>/bin/matlab \</code><br/><code> -nosoftwareopengl</code></td>
2204
+
<tdclass="standard">MATLAB R2025a and later use the Chromium Embedded Framework (CEF), so <code>VGL_CHROMEHACK</code> is necessary to work around Chrome’s X visual selection mechanism. (Refer to the application recipe for Chrome v129 and later.) <br/><br/> When using nVidia’s proprietary Vulkan driver, which does something VirtualGL-like in an X proxy environment, or when using an X proxy that implements the DRI3 X extension, you can also enable GPU acceleration by setting the <code>MW_CEF_STARTUP_OPTIONS</code> environment variable to <code>--use-angle=vulkan</code> prior to launching MATLAB. No additional arguments or environment variables are necessary in this case, nor is it necessary to launch the application with <code>vglrun</code>.</td>
0 commit comments