I've been investigating an issue we've been experiencing with machines that use Intel Graphics 3000 GPUs with Direct3D11. The issue manifests itself as certain meshes randomly being rotated incorrectly and/or flickering. Can see below screenshots of different frames when meshes are visible and not, respectively. These were taken when running the StaticShadowMaps example in the latest 2.1 branch. I get similar behaviour in the Forward3D, InstantRadiosity, ShadowMapDebugging, and ShadowMapFromCode samples.
I've been using Visual Studio's Graphics Debugging Tools to try and find the cause. I tried RenderDoc initially, but it requires D3D Feature Level 11, and this machine only has 10. This causes it to default to using WARP, which works perfectly fine, and I didn't want it to interfere with the results. I'm not sure I trust VS's results either tbh, but I'll explain what I've found with it so far.
When I capture frames with VS, it will always, always, capture the frame as if the objects that are flickering are not visible. Capturing sequential frames doesn't help either. The objects will become invisible until VS has finished capturing its frames.
Once I've found a draw call for one of the missing objects and check the Pipeline Stages info, I notice a few oddities. The Input Assembler stage seems fine, it shows the mesh, in this case a cube. The Vertex Shader stage seems like it's run, but the visual output is just blank. Checking the numbers for the Vertex Shader, the inputs seem reasonable, and stepping through the shader produces reasonable output. However, the output that VS displays for the shader does not match what I saw when stepping through the shader. Each vertex seems to have the same output. As can be seen below. The pixel shader was not run at all, according to VS.
I've tried changing the cull mode to none, and disabling depth testing, but it didn't make a difference.
Is the Intel Graphics 3000 GPU supported by 2.1?
Thanks
