By contrast macOS does stop you from using the hardware you got to the fullest, as it's stuck on 4. And, as we've established at this point, it's not Window's stopping you from leveraging the full extent of the hardware you have. It still supports all the modern good stuff. Ok, so? 4.5 isn't really outdated, either. Meanwhile, they support the latest DirectX 12 for several years already. Even the latest generation UHD Graphics 620/630 only support GL 4.5. In reality, I’m only stuck with GL version Also, you can see in that article that no intel GPU supports GL 4.6 mentioned by GP. If that would be the case, I would be stuck with G元.0 regardless on the GPU. As you see in that table, Intel says HD Graphics 3000/2000 only support OpenGL 3.1, which is exactly what I’m getting from the GLEW library I’m using in that project.Īlso, you can see in that article that no intel GPU supports GL 4.6 mentioned by GP. Specifically, please expand “2nd Generation Intel® Core™ Processors” section. This test uses one command list, one PSO, one HLSL. Even on Intel HD 4000 laptop, OpenGL 4.0 worked just fine with the same code.Ģ. 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. On my desktop PC (Maxwell at the time I’ve wrote that demo) OpenGL 4.0 worked just fine in that very project. In reality, I’m only stuck with GL version < 4.0 on HD2000 and VmWare. No, you're getting stuck at 3.0 because you're hitting the deprecation strategy.ġ.

Directx 12 vs opengl 4.4