Java 3D ERROR : OpenGL 1.2 or better is required (GL_VERSION=1.1) #18
Comments
|
For those who stumble across this issue: could you please comment here with your system configuration? In particular, OS version, Java version, and which graphics card you have? Maybe a pattern will emerge which helps us troubleshoot somehow. |
|
Here is the debug info for my windows 10 machine, on which I have this bug (to reproduce, open the flybrain.tif example, run the 3D viewer): os.arch => amd64 And for the graphic card: |
|
A side note: for debugging on of my plugin in Eclipse (MaMuT), I downloaded the jogl and jocl files from the jogl website and have the Eclipse launcher use them. This bug does not happen. |
Which version? Same as what ships with Fiji? Or newer? |
|
I followed these instructions: So the version I downloaded was this one:
|
|
OK, I downloaded it, just to check, and it is |
|
But:
It works from Eclipse, but not from Fiji. |
|
Can you diff the output of the "System Information" command to see what the differences are? |
|
Same problem with the 3D viewer as soon as I use Fiji with Java 8 (see settings below). Console error output: Information about my version of Java: os.arch => amd64 Graphic Card: NVIDIA GeForce GT 525M Activated update sites: |
|
I am seeing the same error but on Windows 7 64 bit: os.arch = amd64 java.runtime.name = Java(TM) SE Runtime Environment Graphics card id the |
|
There is some upstream discussion of this issue; see: |
|
For those affected by this bug: a developer on the JogAmp Java 3D forum posted the following suggestion:
I did not run it (I do not have an affected system), but if anyone else has a few spare minutes to try, it might be helpful! |
|
There is a hack you can now try, to see whether it fixes the issue on your system:
I tested this on a Windows 10 VM which suffers from this problem, and received the following (slightly different than before!) error: |
Thanks to Philip Jordan; see discussion at: http://forum.jogamp.org/Java-3D-crash-or-flickering-tp4035074p4036787.html This temporary workaround may avoid certain problems in the 3D_Viewer: * fiji/3D_Viewer#17 * fiji/3D_Viewer#18
|
Hi Curtis, same thing here. Attached the two error messages in comparison as info on Win7 (system is stated upstream in my last post): 3D [dev] 1.6.0-scijava-3-SNAPSHOT-pre11-daily-experimental daily org.scijava.java3d.IllegalRenderingStateException: Java 3D ERROR : OpenGL 1.2 or better is required (GL_VERSION=1.1) 3D [dev] 1.6.0-scijava-2-pre11-daily-experimental daily org.scijava.java3d.IllegalRenderingStateException: Java 3D ERROR : OpenGL 1.2 or better is required (GL_VERSION=1.1) |
|
Hi Curtis, I also encounter this error (see message below) making me enable to use the 3d viewer. Configuration: After having following your trick to replace jars/j3dcore-1.6.0-scijava-2.jar the Test Java3D is working(Plugins>Utilities>Debugging>Test Java3D) but not the 3d viewer Using the version Fiji Life-Line version, 2015 December 22, the problem does not occur even after having run the update so it seems to be due to the Java version (1.6 instead of 1.8).
|
|
Hello all. Configuration
The |
|
A quick update, because it works now on the same computer, but with windows 10 instead of windows 7 (I just upgraded Windows and reinstall Fiji). Configuration: -3D [dev] 1.6.0-scijava-2-pre11-daily-experimental daily |
|
Same issue (Exception occurred in RenderingErrorListener: java.lang.RuntimeException ). os.arch = amd64 Fiji build = 2.0.0-rc-49/1.51d) Graphics card: Geforce 770 with Geforce 368 WHQL drivers. If I change the j3dcore to the snapshot posted above, just produces a different error (J3dI18N: Error looking up: Renderer7). JOGL data: |
|
same problem here, but only when the nvidia graphics card is used win 10 pro 64bit laptop starting Fiji with integrated graphics works fine
hope this might help someone, seems like java 3D doesn't like my Nvidia card jogamp only recognizes the Intel graphics card, cant get it to work with nvidia |
|
I also get this error. With me the problem seems to be the second monitor, which I figured out today. If I unplug it from the HDMI port, it works. The problem kind of remains, but at least I know the source now. |
|
I just came across this, so in case this is helpful, same thing. Java 3D test works but 3D viewer does not. Latest updated version of Fiji (2.0.0-rc-54/1.51g;Java 1.8.0_66 [64-bit]) Java 3D properties |
|
I see the following line in 2 of the above listings. |
|
Same problem: Start Fiji, click on 3D Viewer, get this message. (Am I crazy or was this all working 2 days ago. I created a nice 3D .obj file from an image stack, one time, and since then I have not been able to get the code to run...???) 3D [dev] 1.6.0-scijava-2-pre11-daily-experimental daily org.scijava.java3d.IllegalRenderingStateException: Java 3D ERROR : OpenGL 1.2 or better is required (GL_VERSION=1.1) OS Name Microsoft Windows 10 Home |
|
I have this problem on I suspected it to be an issue with Java 8... |
|
There has been some progress on issue #17, which might be relevant here too. In short, @aschain compiled a new version of the ImageJ Launcher for Windows which behaves better with the new Java 3D. You can download it here. If you are a Windows user suffering from a non-working 3D Viewer with the latest Fiji, feel free to give that launcher a try and report your experiences here! |
|
I confirm that this fix works on Windows for at least:
|
|
The provided launcher fixes the 3D Viewer on my system, with details as reported earlier. |
|
Working great here. Many thanks!
…On Tue, Nov 29, 2016 at 1:03 PM, Curtis Rueden ***@***.***> wrote:
There has been some progress on issue #17
<#17>, which *might* be relevant
here too.
In short, @aschain <https://github.com/aschain> compiled a new version of
the ImageJ Launcher for Windows which behaves better with the new Java 3D.
You can download it here
<http://sites.imagej.net/Aschain/fiji-win64.exe-20161102105633>. If you
are a Windows user suffering from a non-working 3D Viewer with the latest
Fiji, feel free to give that launcher a try and report your experiences
here!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEbhnEjQrBdevJl7BlLDBiUDZfgt734mks5rDJMngaJpZM4ILKVw>
.
|
|
This is brilliant! It finally works, even the plain old 3D Viewer.
Windows7, 64bit here.
thanks,
Kieran
On Thu, Dec 1, 2016 at 6:40 AM, Tom Skillman <[email protected]>
wrote:
… Working great here. Many thanks!
On Tue, Nov 29, 2016 at 1:03 PM, Curtis Rueden ***@***.***>
wrote:
> There has been some progress on issue #17
> <#17>, which *might* be relevant
> here too.
>
> In short, @aschain <https://github.com/aschain> compiled a new version
of
> the ImageJ Launcher for Windows which behaves better with the new Java
3D.
> You can download it here
> <http://sites.imagej.net/Aschain/fiji-win64.exe-20161102105633>. If you
> are a Windows user suffering from a non-working 3D Viewer with the latest
> Fiji, feel free to give that launcher a try and report your experiences
> here!
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#18 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/
AEbhnEjQrBdevJl7BlLDBiUDZfgt734mks5rDJMngaJpZM4ILKVw>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHnE82x6tnmPY9Miv3bCJKRl0jdQy09dks5rDdFIgaJpZM4ILKVw>
.
|
|
Thanks, this new version of the ImageJ Launcher fixed also the problem for me on a fresh new installed Fiji running with a NVIDIA GTX 980Ti ! |
|
I concur, new launcher (fiji-win64-20161102105633) works for me on Win7-64, ImageJ 2.0.0-rc54/1.51h; Java 1.8.0_66 (64) on a laptop AMD Radeon HD 7520G. Thanks! |
|
This also fixed it for me on win10, Nvidia Quadro M4000. |
|
The launcher works fine for the 3D Viewer on |
|
Win10 x64, GTX 970, was having the OpenGl < 1.2 error but ctrueden's fix worked. |
|
The new launcher was uploaded to the Java-8 update site. This issue should no longer happen with an up-to-date Fiji. |
|
I just downloaded the new Fiji 64bit zip, loaded, updated (on 15th March,
2017), and it still crashes out.
Same for 32bit version, fresh download, fresh update.
So it still doesn't work.
…On Wed, Mar 15, 2017 at 6:02 AM, Curtis Rueden ***@***.***> wrote:
The new launcher was uploaded to the Java-8 update site. This issue should
no longer happen with an up-to-date Fiji.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHnE8-BBbQGXCVCOZYXCMd-569UpTCceks5rluQ4gaJpZM4ILKVw>
.
|
|
@kmshort By "it still crashes out" do you mean the 3D Viewer plugin specifically? Or Fiji does not start up at all? |
|
I have to recant what I said: |
|
Hi Curtis,
Sorry I should have been more specific.. but since this whole topic is on
3D failure, that's what I meant. Software loads fine, but Java3D error
still occurs.
"org.scijava.java3d.IllegalRenderingStateException: Java 3D ERROR : OpenGL
1.2 or better is required (GL_VERSION=1.1)
"
etc.etc.
cheers,
Kieran
…On Thu, Mar 16, 2017 at 6:09 AM, Curtis Rueden ***@***.***> wrote:
@kmshort <https://github.com/kmshort> By "it still crashes out" do you
mean the 3D Viewer plugin specifically? Or Fiji does not start up at all?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHnE837ZMDgZ-S0pOidjiGcTyg06rhx7ks5rmDdjgaJpZM4ILKVw>
.
|
|
I have to admit that I am confused now. A bunch of people above said that the new launcher fixed the issue for them. But now, people are saying that the latest launcher they get from the core ImageJ update site does not fix the problem. The two new launcher builds are:
Are you saying that the former Or is it simply the case that the above launcher builds fix the problem for some people, but not others? P.S. The 32-bit version is not currently fixed; we did not upload a new build for that. |
|
@ctrueden Good catch. So, on my local Fiji install, I have two .exe:
I got confused, because the icon I have on the desktop launched the fiji exe, which I changed manually a long time ago, and which was overwritten after an update yesterday. |
|
Hi
I tested the new launcher provided by the update site on several win64
systems (windows 10 as well as windows 7) and it worked like a charm.
Same was true for the older fiji-win64.exe.
Cheers,
Jan
Am 16.03.2017 19:50 schrieb "Curtis Rueden" <[email protected]>:
I have to admit that I am confused now. A bunch of people above said that
the new launcher fixed the issue for them. But now, people are saying that
the latest launcher they get from Fiji does *not* fix the problem.
The two new launcher builds are:
- http://sites.imagej.net/Aschain/fiji-win64.exe-20161102105633
- http://update.imagej.net/ImageJ-win64.exe-20170306221247
Are you saying that the former fiji-win64.exe build *does* fix the issue,
but that the latter ImageJ-win64.exe build does *not*?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AKOaGe64-s1pY5_dQfvRi4KwjhmssYU8ks5rmYSBgaJpZM4ILKVw>
.
|
|
Both of those launchers work fine on my Windows 10 64 bit machine, Java
version 8 update 121, ImageJ 1.51j. Thanks.
…On Thu, Mar 16, 2017 at 11:50 AM, Curtis Rueden ***@***.***> wrote:
I have to admit that I am confused now. A bunch of people above said that
the new launcher fixed the issue for them. But now, people are saying that
the latest launcher they get from Fiji does *not* fix the problem.
The two new launcher builds are:
- http://sites.imagej.net/Aschain/fiji-win64.exe-20161102105633
- http://update.imagej.net/ImageJ-win64.exe-20170306221247
Are you saying that the former fiji-win64.exe build *does* fix the issue,
but that the latter ImageJ-win64.exe build does *not*?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEbhnEitKqzXvgzAEvx9_x4OGxuafLOpks5rmYSBgaJpZM4ILKVw>
.
|
|
OK, using the builds available at:
- http://sites.imagej.net/Aschain/fiji-win64.exe-20161102105633
- http://update.imagej.net/ImageJ-win64.exe-20170306221247
seem to work fine here.
The default updated win32 build still fails.
cheers,
Kieran
On Fri, Mar 17, 2017 at 9:39 AM, Tom Skillman <[email protected]>
wrote:
… Both of those launchers work fine on my Windows 10 64 bit machine, Java
version 8 update 121, ImageJ 1.51j. Thanks.
On Thu, Mar 16, 2017 at 11:50 AM, Curtis Rueden ***@***.***>
wrote:
> I have to admit that I am confused now. A bunch of people above said that
> the new launcher fixed the issue for them. But now, people are saying
that
> the latest launcher they get from Fiji does *not* fix the problem.
>
> The two new launcher builds are:
>
> - http://sites.imagej.net/Aschain/fiji-win64.exe-20161102105633
> - http://update.imagej.net/ImageJ-win64.exe-20170306221247
>
> Are you saying that the former fiji-win64.exe build *does* fix the issue,
> but that the latter ImageJ-win64.exe build does *not*?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#18 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AEbhnEitKqzXvgzAEvx9_
x4OGxuafLOpks5rmYSBgaJpZM4ILKVw>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHnE8yCNerQbQBoNoqbSZ8_3lXeNe7Bvks5rmboFgaJpZM4ILKVw>
.
|
|
Hi, I get the following error while using the launcher (at http://sites.imagej.net/Aschain/fiji-win64.exe-20161102105633) on a virtual machine (Windows Server 2012 R2 Standard, Intel(R) Xeon(R) CPU E5 2690 - 4 processors): 3D [dev] 1.6.0-scijava-2-pre11-daily-experimental daily Is there a way to fix this error ? Thank you. |
|
@skanakiya Getting OpenGL support working in a VM can be tricky. Which virtual machine software do you use? Have you Googled the "OpenGL 1.2 or better is required" message together with the name of that software? |
|
Hi Curtis,
I am using Microsoft Remote Desktop to connect to the VM. I googled the
problem but haven't been able to solve it yet.
Regards,
Shreya
…On 8 May 2017 at 02:34, Curtis Rueden ***@***.***> wrote:
@skanakiya <https://github.com/skanakiya> Getting OpenGL support working
in a VM can be tricky. Which virtual machine software do you use? Have you
Googled the "OpenGL 1.2 or better is required" message together with the
name of that software?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AWDvq_-0DzMOrIYfhhSR9FZSgapsF344ks5r3daPgaJpZM4ILKVw>
.
|
|
@skanakiya It seems that only some cards support OpenGL over Remote Desktop. I learned this from this SO post. Maybe your drivers are too old. Or maybe your card does not support OpenGL over Remote Desktop. Running Fiji 3D plugins over remote desktop is IMHO a highly uncommon thing to do, so you are probably on your own with this one. |
|
Hi Curtis,
Thanks for your message. Even after updating the openGL version of the
VM, the Microsoft remote desktop app somehow did not allow to use the
updated version. So I have switched to a Linux VM now and the 3D viewer
works fine.
Regards,
Shreya
…On 31 May 2017 at 07:13, Curtis Rueden ***@***.***> wrote:
@skanakiya <https://github.com/skanakiya> It seems that only some cards
support OpenGL over Remote Desktop. I learned this from this SO post
<https://stackoverflow.com/q/41833949/1207769>. Maybe your drivers are
too old. Or maybe your card does not support OpenGL over Remote Desktop.
Running Fiji 3D plugins over remote desktop is IMHO a highly uncommon thing
to do, so you are probably on your own with this one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AWDvq3_tnH9Z7W-lM0tr0jdTxfS4-M8yks5r_GplgaJpZM4ILKVw>
.
|
|
Please use Reasons:
|
|
Keep in mind my fiji-win64.exe is simply the ImageJ-win64.exe with the Fiji icon and renamed. I'm not sure how to properly compile the Fiji launcher but I would be happy to do it. |
|
This is still a problem for people who have to use a remote desktop. I've tried installing a software implementation of OpenGL from here https://github.com/pal1000/mesa-dist-win/releases That works for all other applications but still doesn't work for ImageJ. I've tried installing it globally and also I've put all the opengl DLLs into folders inside ImageJ with no success. |
|
Hi, @ctrueden This is not an issue comment, just a question. I have tested two scenarios on two Windows PCs(win10, 64bit). Results on PC1 Results on PC2 Why does PC1 can boot the 3D Viewer well when booted from exe? I am glad if you could tell me. tatsuaki |
Several people have now reported the following error:
These reports indicate new systems with new high-quality graphics cards, so it seems unlikely that the version of OpenGL is actually that old. Need to investigate...
The text was updated successfully, but these errors were encountered: