Re: Jogl Using Wrong (Generic) Graphics Adapter
Posted by Sven Gothel on Dec 01, 2014; 3:12pm
URL: https://forum.jogamp.org/Jogl-Using-Wrong-Generic-Graphics-Adapter-tp4033216p4033687.html
On 12/01/2014 03:06 PM, sfriend [via jogamp] wrote:
> For what its worth, I am still seeing this same issue and this does seem to be
> the same. I saw it on a ATI Graphics hardware, but if this user is seeing it
> on a Nvidia GeForce, maybe there is some other issue ( I believe WordWind user
> was seeing it on Nvidia) . In my case I had always passed a new GLCapabilities
> instance when creating my glcanvas. The problem I was seeing was happening
> somewhere before updateGraphicsConfiguration was being called because the
> native surface appeared to be the wrong one and was already defined with a
> pixel format. This then later caused the create context failure. What ever
> causes this problem, after the first time it happens, it continues to happens
> and you can never create another window/glcanvas without kill the application
> and restarting.
>
> I am unable to change video hardware due to being an embedded system, so I'm
> still looking for some way to resolve this. I am more then willing to do some
> addition testing on this issue. If there is any debug information needed or
> something you need to try I may be able to help.Great progress triaging this issue.
If you haven't done yet, please create a new bug report
w/ all the details incl. your last findings.
Switching screens/monitor with AWT IMHO assumes using the same GPU
or at least the same driver capabilities.
This is due to 'big desktop' which spans to all connected monitors,
I have elaborated on this issue in the forum some time ago.
It would be great to have a unit test to reproduce this issue,
if anyhow possible, please copy one of our unit tests and adapt it
for this issue. A git pull request or patch would be most welcome.
~Sven
URL: https://forum.jogamp.org/Jogl-Using-Wrong-Generic-Graphics-Adapter-tp4033216p4033687.html
On 12/01/2014 03:06 PM, sfriend [via jogamp] wrote:
> For what its worth, I am still seeing this same issue and this does seem to be
> the same. I saw it on a ATI Graphics hardware, but if this user is seeing it
> on a Nvidia GeForce, maybe there is some other issue ( I believe WordWind user
> was seeing it on Nvidia) . In my case I had always passed a new GLCapabilities
> instance when creating my glcanvas. The problem I was seeing was happening
> somewhere before updateGraphicsConfiguration was being called because the
> native surface appeared to be the wrong one and was already defined with a
> pixel format. This then later caused the create context failure. What ever
> causes this problem, after the first time it happens, it continues to happens
> and you can never create another window/glcanvas without kill the application
> and restarting.
>
> I am unable to change video hardware due to being an embedded system, so I'm
> still looking for some way to resolve this. I am more then willing to do some
> addition testing on this issue. If there is any debug information needed or
> something you need to try I may be able to help.
If you haven't done yet, please create a new bug report
w/ all the details incl. your last findings.
Switching screens/monitor with AWT IMHO assumes using the same GPU
or at least the same driver capabilities.
This is due to 'big desktop' which spans to all connected monitors,
I have elaborated on this issue in the forum some time ago.
It would be great to have a unit test to reproduce this issue,
if anyhow possible, please copy one of our unit tests and adapt it
for this issue. A git pull request or patch would be most welcome.
~Sven
signature.asc (828 bytes) | Free forum by Nabble | Edit this page |