Problem in VTK 8.2 with defaultFormat() and QVTKOpenGLWidget on Windows 10/Intel

[estan (Elvis Stansvik)]

@Adam_Hendry

@estan

Even if the compatibility profile includes fixed-function APIs that were deprecated in OpenGL 3.0, while the core profile does not, surely those fixed-function APIs are hardware accelerated by the common OpenGL implementations (Intel, NVIDIA, AMD, …)?

I don’t believe so because you’re telling Qt: “I don’t have hardware to accelerate my graphics, so please use software rendering.” The “compatible” in “compatibility profile” means “use old opengl so we work.”

Can you share a reference that says core/compatibility has anything to do with hardware acceleration? I don’t think that is the case. I think the core profile is simply the compatibility profile with the fixed-function APIs deprecated in 3.0 removed.

For example, from the OpenGL 4.6 (Compatibility Profile) specification:

It does not say anything about whether it runs on the hardware or not, that would be up to the OpenGL implementation, but I’m pretty sure the fixed-function APIs runs on the hardware in the Intel/NVIDIA/AMD OpenGL implementations.

Regarding the issue in this thread, I think the investigation done by @lassoan and the Slicer team is the most exhaustive so far.