#Get opengl 4.6 on a amd drivers
#Get opengl 4.6 on a amd driver
#Get opengl 4.6 on a amd code
#Get opengl 4.6 on a amd windows

#Get opengl 4.6 on a amd driver

In both cases, an additional attempt to create a context adds about 4 ms to the application's startup time on my system, whereas the whole context + window creation is about 300 ms with a native driver or 70 ms with Mesa. It seems like only the first context creation is slow. I assume that it works the same with other vendors on Android.Requesting any OpenGL ES version between 2.0-3.2 results in a 3.2 context.

#Get opengl 4.6 on a amd drivers

I assume it works the same on Linux open-source drivers.Requesting any context version above 3.1 results in a 4.5 Core context.Requesting any context version up to 3.1 results in a 3.1 context.It probably works the same on Intel and NVidia but I can't test it now.I assume it works the same on Linux proprietary drivers.Requesting any context version above 2.1 results in the context of the requested version.Requesting any context version up to 2.1 results in a 4.6 Compatibility context.Just try to create a 3.2 core profile version, and if that doesn't work, create a 2.0 version. Which means you don't need a way to do what you're asking to do. And since you have two versions of your code, you'll have to check to see which version to use for that context. You have to have a 2.0 version and a 3.2 core version of your code.

#Get opengl 4.6 on a amd code

If you want to support both core and any 'compatibility' version of OpenGL, then you have to write specialized code for each pathway. If the implementation doesn't support the compatibility profile, then this will not be the highest core profile version of OpenGL supported. As such, if you ask for OpenGL version 2.0, then the implementation will have to give you the highest version of OpenGL that is compatible with GL 2.0. And the compatibility profile is backwards-compatible with all prior versions of OpenGL.Д«ut implementations are not required to support the compatibility profile of OpenGL, only the core profile. So 3.2 core profile is backwards-compatible with 4.6, and everything in-between. Now, all versions of OpenGL for each profile are backwards-compatible with all lower versions of the API for that profile. For example, 2.0 lacks vertex array objects, and core profile OpenGL cannot work without them. Indeed, this is the entire point of the core/compatibility distinction: the compatibility profile provides access to the higher features of the API while being backwards compatible with existing code. However, the core profile of OpenGL 3.2+ is not backwards compatible with 2.0. That is, to ask for X.Y means 'I have written my code against GL version X.Y, so don't give me something that would break my code.'

If you ask for OpenGL version X.Y, the system can give you any supported version of OpenGL which is backwards compatible with X.Y. If there is no better general solution, I would like to know how it works in practice with different drivers on different platforms. How do I handle this problem? Do I have to try all the versions 4.6, 4.5, 4.4, 4.3, 4.2, 4.1, 4.0, 3.3, 3.2, 3.1, 3.0, 2.1, 2.0 in a loop until the context is successfully created? Or is there a better solution? There I have to request a core forward compatible context of some specific version, even though I don't want a specific version, I want the latest one.

#Get opengl 4.6 on a amd windows

It seems that on Windows there won't be a problem, because I can just omit the version and the profile and automatically get a compatibility context with the latest supported version.Д«ut things work differently on macOS and with Mesa. This means that it can live with 2.0 but prefers the latest supported version to be able to use all the available features from OpenGL 3.x-4.x.ДЄlso, it handles all the differences between core and compatibility contexts, so it should work with any profile. I'm developing an application that can use any OpenGL version from 4.6 down to 2.0 by gradually disabling some features and optimizations.