New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java3d-core 1.5.2 vs 1.6 #23
Comments
Ok so the problem is something specific to X11 context creation Certainly from a simplistic view of things your driver appears to be fine and capable and this is doesn't appear to be related to the common intel driver/ Java 8 issue, nor the pixel format one both mentioned extensively elsewhere. I'm not skilled enough in X11 drivers to understand why this particular set of circumstances is not allowed. It might take me a while to work it out, also I don't have a Linux machine nor anyway to play with an X11 driver. |
Is then something related to jogl or java3d? In the first case, do you think it is better to open a bug upstream there? I don't know anything about opengl so I cannot really help but I am available to test possible fixes (I have installed both java3d and jogl from sources compiling them). |
Broadly speaking it's an issue that can be solved faster by the core jogl guys, so opening a new topic here will probably be the best way to get an answer. However before you do that it'll help them a lot if you can do 2 more things (in addition to the excellent information you've already provided) One: extract this zip and run the test.bat file in /etc and provide the output. (Note you made need to modify the bat file slightly with regrads to paths) Two: it would be nice to provide a SSCCE (a simple test case), which should be possible given you've compiled the code for Java3d. In this case we want the smallest amount of code that invokes the line So perhaps just see if you can get the test.bat referred to in step one to fail. If Hello Universe doesn't fail then we can just start comparing the config passed to figure out the issue, that will actually be the easiest pathway forward. |
Here is the output of the test.sh script after having adapted to my distribution:
I get then the same error when trying to execute sweethome3d with java3d 1.6. Unfortunately I cannot provide a simple test case because I am not a java programmer and I don't know opengl. Moreover I cannot run the hello universe example because the link is not valid ( I get "Not found" error) |
Nice work, that's fantastic, it makes it all much simpler, it looks like the simple case with no jav3d in it fails on your set up. This should be solvable by the jogl core guys without any complication added by the java3d side. The next step would be to raise a topic on the jogl forum that describes the history but basically gives the out put of test.bat highlighting the error at the end of the log output. Then we can swap the discussion to that forum. |
Created a post here in the jogl forums |
I have finally solved the problem as described in the above jogl forum, current jogl-2.3.2 needs a patch that will be included in next version jogl-2.3.3 |
After upgrading from java3d-core-1.5.2 to version 1.6 I am not anymore able to run sweethome3d under Linux. I get the following error:
The OpenGL core profile is 3.3 while the compat and ES profiles seem to be only 3.0. I am using Mesa 17.2.7. Here is the dump from glxinfo:
I am wondering which are the changes from version 1.5.2 to 1.6 that caused a different behaviour. I have seen that now java3d-core uses jogl while in the past that was not the case. Any ideas?
The text was updated successfully, but these errors were encountered: