Posted by Sven Gothel on Sep 26, 2014; 6:20pm
URL: https://forum.jogamp.org/Jogl-Using-Wrong-Generic-Graphics-Adapter-tp4033216p4033218.html

On 09/26/2014 05:09 PM, sfriend [via jogamp] wrote:
> When opening several windows JFrame with GLCanvas, on occasion the Wrong
> Graphics adapter is used.
> GL_VENDOR: Microsoft Corporation
> GL_RENDERER: GDI Generic
> GL_VERSION: 1.1.0
looks like as if the driver falls back to GDI renderer .. hmm.

>
> The problem is happening when the GLCanvas is added to the container. I print
> the GL_VENDOR in GLEventListener init. I disabled arb context using
> disable.openarbcontext due to failure inside contest creation for the same
> reason wrong graphics adapter.
pretty much a driver bug, and arbcontext should work.

> This same problem was reported in World Wind and I have verified I am having
> the exact problem. The world wind issue is described here:
> http://forum.worldwindcentral.com/showthread.php?43356-Multi-window-GLContext-initialization-problem.
>
> I believe it may also be related to :
> http://forum.jogamp.org/Problem-since-Jogl-2-2-1-td4033169.html
Nope, that is an issue w/ Intel driver using pbuffer and failing.

>
> I have the problem Running on Windows 7 or XP . Jogl 2.2.1 and older. Is
> anyone else having these problems or have any suggestions on a work around ?  
sadly not, but then we are using a fairly new AMD driver
on our windows test machines.

> GL_VENDOR: ATI Technologies Inc.
> GL_RENDERER: AMD Radeon E6760
> GL_VERSION: 4.4.12874

Is that a current driver version ? Looks like.

'AMD Radeon E6760' refers to which GPU ?

I will setup another test machine w/ latest AMD driver,
since our remote test machine w/ AMD Windows works.

Hope it's not GPU related (as in code path per GPU type in driver).

~Sven