direct3d
Here are 95 public repositories matching this topic...
Release Type: Github
Version: master
Describe the bug
The documentation states "The index of the component to access. Use 0 for the alpha component, 1 for the red component, 2 for the green component, and 3 for the blue component".
The actual implementation uses:
switch (index)
{
case 0: return R;
case 1: return G;
case 2: return B;
case 3: return A;
}
Reticketed from apitrace/apitrace#413
Compilation fails without X11 on fresh Linux system while https://github.com/apitrace/apitrace/blob/master/docs/INSTALL.markdown#linux docs says it is optional.
Log from fresh Ubuntu container:
lxc launch ilo:ubuntu/wily/amd64 apitrace
lxc exec apitrace bash
# apt-get install g++ cmake git python
# git clone https://github.com/ap
It would be really nice to have a more complete set of tutorials/samples to work with.
E.g. None of the samples use Geometry Instancing,Indirect Buffers.
From the Vulkan/Metal docs it is also not clear, because each API handles this slightly differently.
Best,
Marc
Made Man issues
-
Bifurcation of objects
D9VK


We use PIX labels to organize the events in a single frame (e.g. Z PrePass, GBuffer, Alpha, etc). These can get quite deep/nested.
It would be useful if we could see a 'path' for the event currently selected, e.g.
Camera 1\3D Stage\GBuffer\TreeBark Material
It would be extra nice if clicking on any of these would take you to the beginning of that section.
(think folders in Windows Explor