Invalid texture coordinates on Mac OS X

[gdm85]

(spun from #1)

Texture coordinates do not appear to be working on darwin systems. I have setup branch debug/tex-coords to test the texture coordinate parameters that are being passed to OpenGL via go-gl, this is my output: https://gist.github.com/gdm85/98f7af432ead9045b238

If somebody is willing to test with that branch and the output differs, please post a gist. Texture coordinates should always be the same.

Samples

As originally reported by @scottjbarr:

And @glycerine:

[gdm85]

As reported in go-gl/gl#40 it seems like only OpenGL 4.1 is supposed to work good on Mac OS X...

[gdm85]

For the records, it works fine on a Macbook Pro running Linux:

WolfenGo v0.1.1, Copyright (C) 2016 gdm85
https://github.com/gdm85/wolfengo
WolfenGo comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under GNU/GPLv2 license.
3.0 Mesa 11.0.2
63 FPS
60 FPS
60 FPS
64 FPS

[gdm85]

I have updated the project to use latest gl and glfw packages; I could reproduce the issue on Mac OS X and generate by myself the debug output as per OP (nobody submitted it so far).

The texture coordinates are identical on Linux and Mac OS X, so it's not that.

Also as reported here, it's likely not an issue of OpenGL 2.1 support on Mac OS X.

I will try to test the Java version now.

If anybody knows how to run Mac OS X' OpenGL Driver Monitor, suggestions and/or support is welcome :)

[kot13]

It seems that it is identical: https://gist.github.com/kot13/64620a77986cb866ab39bb5d55071a4e

[gdm85]

@kot13 so basically you are able to reproduce the problem reported here?

[kot13]

@gdm85 yes, i able to reproduce.

[gdm85]

@jmcclell I have merged to master some conditional build which switches the GL version being built and should work on Mac OS X, can you please give it a try?

[jmcclell]

@gdm85 Looks great on a 2018 MacBook Pro running macOS 10.14.6