Created attachment 92380 [details] glxinfo output GL3.txt reports that radionsi support opengl 3.1 version. But glxinfo reports about 3.0 only for hardware and core profile about 3.1.
Created attachment 92381 [details] xorg.log
Everything looks fine in your glxinfo: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.0.1 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) For OpenGL versions higher than 3.0 the devs are only supporting core profile. So this is not a bug.
(In reply to comment #2) > Everything looks fine in your glxinfo: > > OpenGL vendor string: X.Org > OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE > OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.0.1 > OpenGL core profile shading language version string: 1.40 > OpenGL core profile context flags: (none) > > For OpenGL versions higher than 3.0 the devs are only supporting core > profile. So this is not a bug. Closing.
(In reply to comment #2) > For OpenGL versions higher than 3.0 the devs are only supporting core > profile. So this is not a bug. What does it mean "the devs"?
(In reply to comment #4) > (In reply to comment #2) > > For OpenGL versions higher than 3.0 the devs are only supporting core > > profile. So this is not a bug. > > What does it mean "the devs"? The developers.
Sorry for my buzz. I want to play Natural Selection 2 and don't want to think. You wrote about it already http://cgit.freedesktop.org/mesa/mesa/tree/docs/GL3.txt?h=10.0&id=12484d2582a478b3ef126efe12f24c8e4a4d4db7#n10 OpenGL 3.1 and later versions are only supported with the Core profile. There are no plans to support GL_ARB_compatibility. Developers want to earn money from unknownworlds and don't want to code. Community of ns2 discusses mesa and waits for nothing http://forums.unknownworlds.com/discussion/132731/linux-intel-hd-4000-opengl-3-1-core-profile
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.