> On Feb 20, 2018, at 2:07 PM, Jonas Maebe wrote:
>
> If you first create a context and it then still returns false, it may
> also mean that you did not create the context properly.
It’s up to SDL then I guess but it says I’m getting a 4.1 context (GL_VERSION),
which is the highest fully impl
Ryan Joseph wrote:
>> On Feb 20, 2018, at 4:24 AM, Jonas Maebe wrote:
>>
>> My guess is that the Load_GL_VERSION_3_3x() function is broken since it
>> appears to call glGetString before a context has been created, and that it
>> just happens to work on some (most?) implementations by pure chanc
> On Feb 20, 2018, at 4:24 AM, Jonas Maebe wrote:
>
> My guess is that the Load_GL_VERSION_3_3x() function is broken since it
> appears to call glGetString before a context has been created, and that it
> just happens to work on some (most?) implementations by pure chance.
After a context is
On 19/02/18 03:21, Ryan Joseph wrote:
Maybe SDL has a bug then because glGetString should never crash.
glGetString is not an SDL function, but an OpenGL framework version.
When are the land Load_GL_VERSION_XXX functions meant to be called in the
pipeline? I was calling them before the openGL
Maybe SDL has a bug then because glGetString should never crash.
When are the land Load_GL_VERSION_XXX functions meant to be called in the
pipeline? I was calling them before the openGL context is created (which works
except for 3.x on the old MacBook) but I just tried calling Load_GL_VERSION_3
On 18/02/18 02:59, Ryan Joseph wrote:
I tried using a core OpenGL context on my old MacBook (2010) and got a crash
from glGetString from the Pascal bindings (a legacy 2.x context doesn’t crash).
I pulled out the related functions from glext.pp where it crashes in
Load_GL_ARB_blend_func_extende
