Hi Mikhail,
You are right. I managed to build the WDDM drivers and OpenGL driver
without any problem.
Currently my understanding is that chromium commands is a command packet
wrapper in which OpenGL state values are packed. The packer
(GuestHost\OpenGL\packer) is built as VBoxOGLpackspu.dll that V
Hi Dong,
We do not use ICD SDK atm, so it should be possible to build all asutt using
standard WDK/SDK headers/libs & tools.
We use XPDM-complient ICD interface to implement OpenGL support on windows.
As for D3D, VBox WineD3D version is using VBoxOGL directly rather than via
Opengl32 + ICD.
WDD
Hi Mikhail & Klaus,
Thanks a lot for your information. It is very helpful.
I had wrong impression that VBox 3D implementation is on top SVGA, which
leaded me to the wrong place in the repository where has an uncompleted
SVGA.
Now I kinda have a big picture how VBox D3D&OpenGL driver works.
src\VBo
Just to get a bit more precise info on the current 3D source code location:
Guest-side code is located in
src/VBox/Additions/common/crOpenGL
src/VBox/Additions/WINNT/Graphics/Video (WDDM stuff)
src/VBox/Additions/WINNT/Graphics/Wine_new
Host-side code is in
src/VBox/HostServices/SharedOpenGL
Gue
Hi Dong,
On 01.04.2014 00:53, DONG HE wrote:
> Hello VBox developers,
>
> Recently I have great interest in figuring out how VBox implement 3D
> support for D3D and OpenGL. The learning work finally can not proceed as
> a few files are missing from the SVN trunk check-out, which
> are DevVGA-SVGA3
