Hi Rudolfs, In order to provide 3D acceleration, VBox HGCM/OpenGL host service should be running. It is currently a part of VirtualBoxVM process (ShCrOpenGL thread). In order to provide 3D acceleration support for your frontend, I am afraid, you need to adapt stuff from this thread for your code. And I am afraid this might be not that easy (there is a bit of magic when VBox GUI conversates w/ 3D stuff). Please refer to src/VBox/HostServices/SharedOpenGL and src/VBox/GuestHost/OpenGL sources.
Btw, if you describe a little bit more why do you need this and what you already have done, maybe I could explain you more things/steps you need to do in order to reach the goal. VBox.log also might be helpful. Vadim > On 24 Jan 2015, at 14:14, Rūdolfs Bundulis <[email protected]> wrote: > > Hi, > > I'm having a bit of a hard time understanding why my custom framebuffer > cannot use the 3D acceleration feature. I have a Windows 7 guest machine (3D > acceleration enabled, guest additions installed) and a Unity demo > application. Under the default QT GUI the application launches fine, while > under my frontend Unity is not able to create the D3D device. First I though > that this could be due to incorrect implementation of IFramebuffer, but when > I looked at UIFrameBuffer::Notify3DEvent(ULONG uType, BYTE *pData) in > UIFrameBuffer.cpp there wasn't any special magic there. Are there any hints > to guide me towards understanding the cause of this? Is there any tracing > facilities for the guest miniport driver? Also, I don't have a window handle > for my frontend since there is no actual window. If I am returning 0 in > get_WinId in my framebuffer can that mess things up? > > Best Regards, > Rudolfs Bundulis > _______________________________________________ > vbox-dev mailing list > [email protected] > https://www.virtualbox.org/mailman/listinfo/vbox-dev _______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
