Bug 1084 - Mapped GLProfile's (e.g. GL2ES2, GL2GL3) select software renderer GL4 instead of hardware renderer GL3
Summary: Mapped GLProfile's (e.g. GL2ES2, GL2GL3) select software renderer GL4 instead...
Status: RESOLVED FIXED
Alias: None
Product: Jogl
Classification: JogAmp
Component: core (show other bugs)
Version: 2.3.0
Hardware: All all
: --- major
Assignee: Sven Gothel
URL:
Depends on:
Blocks:
 
Reported: 2014-10-01 22:26 CEST by Sven Gothel
Modified: 2019-03-29 17:54 CET (History)
1 user (show)

See Also:
Type: ---
SCM Refs:
c85e0566c55cdc99668dd373e6b6b8b66a557c8e
Workaround: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Gothel 2014-10-01 22:26:21 CEST 
GLProfile's mapping code does not consider the following combination:
  - GL4 software
  - GL3 hardware

and hence maps GL4-software -> [GL2ES2, GL2GL3], 
where GL3-hardware -> [GL2ES2, GL2GL3] is desired.

This combination has recently been observed on 
Mac OSX 10.9.5, which includes a software GL 4.1 implementation.

However, other systems could be affected as well.
Comment 1 Sven Gothel 2014-10-01 23:52:16 CEST 
Commit c85e0566c55cdc99668dd373e6b6b8b66a557c8e:

Fix GLProfile.computeProfileImpl(..):

Only use the higher profile, if hardware-accelerated or none of the 
lower profiles offers hardware-acceleration!

This extra condition was missing for certain profiles,
e.g. GL4, GL4bc, GL3, GL3bc and GL2.