Clarify VirGL vs emuGL support

canonical · May 8, 2024 · 4d3fd37 · 4d3fd37
1 parent 857a6ab
commit 4d3fd37
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/explanation/rendering-architecture.md b/explanation/rendering-architecture.md
@@ -22,7 +22,7 @@ As the Venus Vulkan driver only provides Vulkan API support for Android, we use
 
 In terms of performance, this could be perceived to have some transmission overhead when compared to the rendering on Intel and AMD GPUs. However, Anbox Cloud is optimised to keep this overhead minimal and the additional overhead due to the transmission of Vulkan API calls from the Android space to the Ubuntu side renderer is not significant enough to affect most use cases.
 
-In older versions, Anbox Cloud used a similar rendering pipeline for NVIDIA GPUs which only supports OpenGL ES and EGL but cannot provide Vulkan API support.
+In older versions, Anbox Cloud used a similar rendering pipeline for NVIDIA GPUs which only supports OpenGL ES and EGL but could not provide Vulkan API support. Since the 1.21.0 release, VirGL was also available as a rendering option but had to be enabled explicitly.
 
 Starting 1.22.0, Anbox Cloud uses VirGL as the default renderer for NVIDIA GPUs. If VirGL is not compatible for your use case (and you require the older implementation), [contact us](https://anbox-cloud.io/contact-us).