Posted by
Sven Gothel on
Aug 23, 2019; 7:23am
URL: https://forum.jogamp.org/java11-release-progress-thread-also-review-tp4039948p4039991.html
This bug became Bug 1383: GLProfile fails to select default core profiles when
no compat profiles are available
<
https://jogamp.org/bugzilla/show_bug.cgi?id=1383>
and while working on it
fixing: Bug 1385: Limit Quirk GL3CompatNonCompliant to Mesa < 18.2.0
(yes, new Mesa gives proper GL version/profile replies)
feature: Bug 1384 - Allow GLRendererQuirks to be overridden by user properties
(allowing you to inject or ignore the quirks via 2 properties)
All the above is pushed into java11 branch.
Sadly we got a regression in Mesa:
'Bug 1386 - Mesa 18.3.6 hardware renderer (Intel/AMD) freezes after native
parenting'
Which I 'workaround' (not really) on our test machine
using software rendering only 'LIBGL_ALWAYS_SOFTWARE=true'.
Will post a manual unit test run result snapshot in a bit.
There is more work to do, but not really related to java11,
more related to issues with the updated systems (MacOS, Mesa, ..).
~Sven
On 8/20/19 5:39 PM, Sven Gothel [via jogamp] wrote:
> On 8/20/19 11:13 AM, gouessej [via jogamp] wrote:
>> :s You'll have to look at GLContextImpl, I suspect my last attempt of fixing
>> Mesa detection, maybe a renderer quirk has become unnecessary.
>
> Well, I was hunting witches it seems:
> - GLRendererQuirks.GLNonCompliant
> was triggered, i.e. intentionally set and hence the profile dropped.
>
> Our good old:
> * Non compliant GL context due to a buggy implementation not suitable for
> use.
> * <p>
> * Currently, Mesa >= 9.1.3 (may extend back as far as 9.0) OpenGL 3.1
> compatibility
> * context is not compliant. Most programs will give completely broken
> output (or no
> * output at all. For now, this context is not trusted.
> * </p>
> * The above has been confirmed for the following Mesa 9.* GL_RENDERER
> strings:
> * <ul>
> * <li>Mesa .* Intel(R) Sandybridge Desktop</li>
> * <li>Gallium 0.4 on AMD RS880</li>
> * </ul>
> * </p>
> * <p>
> May need to revalidate whether Mesa has re-enabled support for
> OpenGL compat profiles >= 3.1?
>
> The real bug here was that GLProfile didn't chose the right profile,
> i.e. the default choice should have been made for the core profile.
> So I need to fix that.