Your System Does Not Use 3d Hardware Acceleration Blender Citrix

CTX202149

{{tooltipText}}

Known Issues or Configuration Reasons: OpenGL/DirectX/GPU Acceleration Not Used

Article | Display | {{likeCount}} found this helpful | Created: {{articleFormattedCreatedDate}} | Modified: {{articleFormattedModifiedDate}}

Information

Browsers are often an integral function of the operating system and are aware that they are virtualized. As such we would recommend finding those problems within a browser and also examination with a standalone criterion application to verify if it is a configuration issue with GPU/OpenGL usage in general or whether it is specific to that browser. It is also helpful if users verify whether the issue affects DX9, DX11 and OpenGL separately as the implementations differ.

Known Issues

• CTX202148 - Changes in Experimental Support for XenApp and Multiple GPUs
• CTX202010 - Internet Explorer is Not GPU-accelerated When Virtualized on XenServer 6.2
• CTX202065 - Mozilla Firefox Blocks GPU Acceleration for WebGL with XenApp on Windows 2012 R2/2008 R2
• CTX202066 - GPU-accelerated OpenGL on Amazon Web Services (AWS G2 instances) with NVIDIA GRID K520/K340 No Longer Works
• CTX202084 - Internet Explorer 9: Hardware Acceleration Does Not Work in Some Virtualization Environments (including vSphere/ESXi)
• CTX202106 - Publishing Chrome Browser for XenApp – and then that GPU acceleration is enabled
• CTX202276 - Google Chrome Browser (Chrome 45 and upwards) Blocks GPU Acceleration with XenApp on Windows 2012 R2/2008 R2
• CTX202839 - HDX - Certain Sets of Applications (Example: Office 2013) are Non Using the GPU
• CTX204161 - Net Explorer is Non GPU-Accelerated on XenApp for Windows Server (2012 R2 and 2008 R2)

Known Dependency for Net Explorer: CPU must back up SLAT (Second Level Accost Translation)

Known Mutual Configuration Issue: Under RDP/RDS for XenApp on Windows Server Operating Systems (Win 2008 R2, Win 2012 R2 etc) are configured to disable GPU acceleration.

• On Windows Server 2008 R2, DirectX and Direct3D require no special settings to utilise a single GPU.
• On Windows Server 2012,Remote Desktop Services (RDS) sessions on the RD Session Host server by default use the Microsoft Basic Render Driver and therefore do not use the GPU. This prevents 2D DirectX applications (such as Microsoft Office apps) from using GPU resources for rendering which tin can sometimes exist more efficiently performed in software. To run 3D applications that apply DirectX in RDS sessions, it is recommended that they are run on a dedicated server where 2d apps are not likely to compete for GPU resources.To use the GPU in RDS sessions on Windows Server 2012, enable the "Use the hardware default graphics adapter for all Remote Desktop Services sessions" setting in the group policy.

Local Figurer Policy > Computer Configuration > Authoritative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environs.

Note: There are some comments in the following Microsoft blog that fill in some details - Windows Server 2012 Remote Desktop Services (RDS)

Known Common Configuration Issue: Under RDP/RDS for XenApp on Windows Server Operating Systems (Win 2008 R2, Win 2012 R2 etc) WPF applications such as Autodesk have to be explicitly enabled

On both Windows Server 2008 R2 and Windows Server 2012 R2:
To enable WPF applications (such as Autodesks) to render using the server's GPU, in the registry of the server running the Windows Server OS sessions, create the following settings:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

• [HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_Dlls\ Multiple Monitor Hook] " EnableWPFHook" =dword:00000001
• [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\CtxHook\AppInit_Dlls\ Multiple Monitor Hook] " EnableWPFHook" =dword:00000001

The use of these registry keys is fully supported by Citrix, however customers should ensure care when editing them and Citrix will not bear responsibility for problems arising from incorrect editing of registry keys.

Known Monitoring Limitations: XenCenter Metrics show 0 for GPU-passthrough

Users should be aware of limitations in monitoring insight when using NVIDIA Grid technologies such as vGPU and GPU laissez passer-through: Limitations in monitoring shared NVIDIA GPU technologies. GPU laissez passer-through can just be monitored from within a guest and metrics within XenCenter or from XenServer will be shown as 0.

---

Additional Resources

---

Share this post