The FPS in the following tables are the average framerates. CPU: Intel Core i5 6600K Motherboard: ASUS Z170 Pro GamingĬlock speeds: stock values for the CPU, memory and graphics cards.I will update this post as soon as I find bugs or bring some optimizations in GeeXLab that can change the results.
#BLUESTACKS OPEN GL VS DIRECT X DRIVERS#
The results of this test should be taken with caution because it’s my first implementation of a Direct3D 12 plugin for GeeXLab and graphics drivers are also constantly updated. You can change the number of polygons by editing the source code of both files: lines 76-84 (09-lighting-mesh-d3d12.xml) and 47-54 (09-lighting-mesh-gl32.xml).
The test is available in the host_api/Direct3D12_vs_OpenGL/ folder of the code sample pack (files: 09-lighting-mesh-d3d12.xml and 09-lighting-mesh-gl32.xml). You can download both GeeXLab (version 0.9.3.0+ is recommended) and the test from THIS PAGE. This test uses one command list, one PSO, one HLSL program, one mesh and one texture. Since GeeXLab is now available with an OpenGL and a Direct3D 12 renderers, here is a quick benchmark that shows the difference of performance between Direct3D 12 and OpenGL 3.2 in a very simple scene: a phong-textured mesh (a torus to be original) is rendered with various polygon density. It’s not a full support but most of the basic things are available: command lists (CL), pipeline state objects (PSO), constant buffers (CB) and HLSL shaders.Īn introduction to Direct3D programming with GeeXLab is available HERE. GeeXLab, the successor of GLSL Hacker, comes with the support of Direct3D 12.
0 kommentar(er)
