However, the guest OS still doesĪlso, the "Display adapters" section of the Device Manager in the guest OS shows "Microsoft RemoteFX GRaphics Device - WDDM" just like it should.Īt this point, I'm beginning to wonder if it could be a bug in RemoteFX's implementation. I can confirm the actual graphics hardware is being used by the guest OS (using GPU-Z on the host machine). The most disturbing thing is I am able to access OpenCL 1.1 functionality, just like advertised in the above link. ASTC is in OpenGL 4.4 as well as in OpenGL ES 3.1, so it is an advanced technology that is used in popular 3D video games. RemoteFX 3D Video Adapter: 1G VRAM allocated (max) AMD FirePro W7100 (qualifies for RemoteFX vGPU) However, this should not be the case my configuration qualifies for all the needed prerequisites. If you use OpenGL directly, youll still find SDL, SFML, or something else (like GLFW) useful to abstract the platform away and make it easier to. Both have an accelerated 2D rendering API that uses OpenGL under the hood (SDL can also use DIrect3D). My configuration only allows me to access OpenGL 1.1 functionality. For 2D games, you can do well enough with either SDL or SFML. As advertised in the technet blog entry called "RemoteFX vGPU Updates in Windows Server Next", I would like to access OpenGL 4.4 functionality inside a VM configured with Hyper-V.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |