>> I'm sure this is what you are working on (integrating the VGX fast remoting APIs) and why its not officially supported yet.
This was done a long time ago I have used a vDGA desktop as my primary for 12 months now. I think ( Could be wrong ) the bits are actually in the latest released builds I assume so since I have seen some really nice customer benchmarks lately comparing different configurations I recall them being based on 5.2 but would need to look back. You are right its not yet officially supported. I have never seen any lag with vDGA except in the really early development. I really do not have lag with vSGA either depending on the workload though. I am not a super heavy 3D user but during development I hammered it a lot and know where most the bottlenecks are. vDGA is faster than my Core Duo Mac I know that Image may be NSFW.
Clik here to view.
. There are new APIs beyond the originals we used, for K2.
>> Another idea we have been tossing around in an effort to stay all VMware view at the endpoints (utilizing zero clients) is the idea of running a VM with XenApp and a dedicated GPU (to publish our 3D apps to multiple users) and then integrating that into View. It looks like you would >>connect into a View VM which has shortcuts on the desktop presenting the XenApp published apps through citrix receiver (would install the citrix receiver plug-in on the virtual machine your zero client is connecting to). However with this approach I'm not sure how well the remote >>session's experience (FPS/lag) would be going through all these levels.
It technically would work, but I do not think the performance would be that great. You would have to cut back on your virtual desktop consolidation as well most likely. The Citrix receiver requirements for 3D pro are beefy. For the client decode they recommend a Dual Core 3Ghz Client with at least 2 GB of RAM. That is before you include any other apps on the Virtual Desktop. I am not sure I would want the add complexity. Unless there is a compelling reason to mix VDI and SBC I would just go straight XenApp on ESX with Direct-Pass GPUs based on what you are describing. If there is a compelling reason to have both I might sway that direction.
WP
