Re: Help Interpreting a JOGL profile not found error.
Posted by Sven Gothel on Oct 17, 2013; 1:48pm
URL: https://forum.jogamp.org/Help-Interpreting-a-JOGL-profile-not-found-error-tp4030269p4030289.html
On 10/17/2013 03:02 PM, nick.collier [via jogamp] wrote:
> Thanks. My concern was that his card, being newish, had dropped support for
> the GL2 profile. I take it from your response that this is not the case, and
> the error message indicates a driver or jogl issue. We don't see this problem
> on any of our test machines so I'm inclined to think its a driver issue.
>
> We are using one of the earlier interim builds as we needed some fixes in OSX,
> I think. The info I have for it:
>
> gluegen and jogl from
> http://jogamp.org/deployment/archive/master/gluegen_666-joal_432-jogl_981-jocl_788-signed/archive/
> gluegen_666
> jogl_981
>
> As far as getting debug info, the issue was reported by a user of our
> software. I don't have access to the machine, but I will ask him to update
> jogl and see what happens.That would be great.
It would help if you and user may create a test case
or can describe whether even our tests/applets fail,
i.e. best to follow Wiki/FAQ/Bugeport.
(Yeah .. logs w/ debug flags set .. would help a lot when crashing).
IMHO it should be possible to reproduce the scenario
w/o the mentioned user involved.
>
> Lastly, we are hoping to update our software to the latest stable release that
> does require testing and some release engineering on our end.
~Sven
URL: https://forum.jogamp.org/Help-Interpreting-a-JOGL-profile-not-found-error-tp4030269p4030289.html
On 10/17/2013 03:02 PM, nick.collier [via jogamp] wrote:
> Thanks. My concern was that his card, being newish, had dropped support for
> the GL2 profile. I take it from your response that this is not the case, and
> the error message indicates a driver or jogl issue. We don't see this problem
> on any of our test machines so I'm inclined to think its a driver issue.
>
> We are using one of the earlier interim builds as we needed some fixes in OSX,
> I think. The info I have for it:
>
> gluegen and jogl from
> http://jogamp.org/deployment/archive/master/gluegen_666-joal_432-jogl_981-jocl_788-signed/archive/
> gluegen_666
> jogl_981
>
> As far as getting debug info, the issue was reported by a user of our
> software. I don't have access to the machine, but I will ask him to update
> jogl and see what happens.
It would help if you and user may create a test case
or can describe whether even our tests/applets fail,
i.e. best to follow Wiki/FAQ/Bugeport.
(Yeah .. logs w/ debug flags set .. would help a lot when crashing).
IMHO it should be possible to reproduce the scenario
w/o the mentioned user involved.
>
> Lastly, we are hoping to update our software to the latest stable release that
> does require testing and some release engineering on our end.
~Sven
signature.asc (911 bytes) | Free forum by Nabble | Edit this page |