Your System Does Not Use 3d Hardware Acceleration Blender Citrix Xendesktop

CTX202149

{{tooltipText}}

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

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

Information

Browsers are often an integral part of the operating arrangement and are aware that they are virtualized. As such we would recommend finding those problems within a browser and besides test with a standalone benchmark application to verify if it is a configuration issue with GPU/OpenGL usage in full general or whether it is specific to that browser. It is also helpful if users verify whether the outcome 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 Non GPU-accelerated When Virtualized on XenServer half-dozen.two
• 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 - Cyberspace Explorer 9: Hardware Acceleration Does Non Work in Some Virtualization Environments (including vSphere/ESXi)
• CTX202106 - Publishing Chrome Browser for XenApp – so that GPU acceleration is enabled
• CTX202276 - Google Chrome Browser (Chrome 45 and upward) Blocks GPU Acceleration with XenApp on Windows 2012 R2/2008 R2
• CTX202839 - HDX - Sure Sets of Applications (Example: Function 2013) are Not Using the GPU
• CTX204161 - Net Explorer is Not GPU-Accelerated on XenApp for Windows Server (2012 R2 and 2008 R2)

Known Dependency for Internet Explorer: CPU must back up SLAT (2d Level Accost Translation)

Known Common Configuration Issue: Nether 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 crave no special settings to use a single GPU.
• On Windows Server 2012,Remote Desktop Services (RDS) sessions on the RD Session Host server by default employ the Microsoft Basic Render Driver and therefore do non employ the GPU. This prevents 2D DirectX applications (such as Microsoft Role apps) from using GPU resource for rendering which can sometimes be more efficiently performed in software. To run 3D applications that use DirectX in RDS sessions, information technology is recommended that they are run on a dedicated server where 2nd apps are non probable to compete for GPU resources.To employ 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 Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.

Note: At that place are some comments in the following Microsoft blog that make full in some details - Windows Server 2012 Remote Desktop Services (RDS)

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

On both Windows Server 2008 R2 and Windows Server 2012 R2:
To enable WPF applications (such as Autodesks) to return 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 earlier 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 apply of these registry keys is fully supported by Citrix, however customers should ensure care when editing them and Citrix volition non bear responsibility for issues 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 every bit vGPU and GPU pass-through: Limitations in monitoring shared NVIDIA GPU technologies. GPU pass-through can but be monitored from within a guest and metrics within XenCenter or from XenServer will be shown as 0.

---

Additional Resource

---

Share this post