[OX-647] Nodes not Visible anymore in classical mode on top Screens about webknossos

[tmbo]

[author="daniel", created="Wed, 22 May 2013 17:32:48 +0200"]

I've contacted Kevin who also had this problem once. Let's see whether he can give any advice

[tmbo]

[author="daniel", created="Wed, 22 May 2013 17:53:01 +0200"]

@helge:

Could you try to open Chrome with native/desktop OpenGL enabled, as described here:
https://github.com/mrdoob/three.js/wiki/How-to-use-OpenGL-or-ANGLE-rendering-on-Windows

You can see whether this was successful, when the lines at this link on the left picture look the same as in the right picture:
http://alteredqualia.com/tmp/webgl-linewidth-test/

Do you still experience the same problem?

[tmbo]

[author="", created="Wed, 22 May 2013 19:47:03 +0200"]

Well, as soon as I use the commands from the first link, Oxalis tells me, that WebGL is not enabled in my browser (because I tell Chrome to use an desktop OpenGL which is obviously not installed?!). Do I just need different Graphic drivers or install it manually? I'm just wondering, since I have the Up-to-date drivers for my Nvidia, which is quite decent.

[tmbo]

[author="daniel", created="Wed, 22 May 2013 19:57:15 +0200"]

Which graphics card and driver version are you using?
OpenGL should be included in the newest graphic drivers of most vendors and cards...

[tmbo]

[author="", created="Wed, 22 May 2013 20:17:03 +0200"]

I was using the 314.22 WHQL Nvidia Driver for my Nvidia Geforce GT 540M, for Windows 7 x64. Since my Laptop was getting slower and slower the last weeks, I will format it now and re-install the newest Drivers. I will then report if the Problem was solved.

One interesting fact about the bug: When there were more then one tree visible in the upper screens, only the one selected did not show the nodes. For all unselected trees, nodes were visible.

[tmbo]

[author="daniel", created="Wed, 22 May 2013 20:27:14 +0200"]

Thats exactly the same environment I'm running in, so that's strange.
Looking forward to hear whether this changed anything.

Thanks for this piece of information, I'll try to find any connections..

[tmbo]

[author="", created="Wed, 22 May 2013 21:19:43 +0200"]

I now formated my system, and the only installed components are the basic drivers (including the newest Nvidia Driver again) and Google Chrome. Unfortunately still the same problem. Im pretty sure now, that it's not my software! I also forgot to mention, that this bug just appeared a few weeks ago, before it was fine.

[tmbo]

[author="daniel", created="Wed, 22 May 2013 21:26:39 +0200"]

Unfortunately this isn't reproducible for any of us, so it's really hard to debug.

When you are moving the plane, do the nodes appear/disappear?

[tmbo]

[author="", created="Wed, 22 May 2013 21:34:37 +0200"]

Yes, I just realized that the nodes appear in the XY window (upper left) when I move the "cross-hair" away from the tree. The nodes appear/disappear only at a certain distance to the middle of the window. In the YZ window on the other hand, no nodes are visible at any time. If it helps, I can take some pictures and send/upload them.

[tmbo]

[author="daniel", created="Wed, 22 May 2013 21:39:35 +0200"]

Maybe you could create an explorative tracing and set lots of nodes in the xy-view without changing the z-coordinate, so one can see which nodes are displayed and which aren't.
Same for the yz-view, I think this would be helpful.

Just send them to [email protected] , thanks for your help!

[tmbo]

[author="", created="Wed, 22 May 2013 21:50:23 +0200"]

Alright, they should be incoming right now. After some trying, it feels like both windows behave the same, and only show nodes in the bottom right.

[tmbo]

[author="daniel", created="Wed, 22 May 2013 21:56:59 +0200"]

Thanks, I've received them and will hopefully come up with a solution for this problem soon!

[tmbo]

[author="daniel", created="Sun, 26 May 2013 23:26:40 +0200"]

Hey Helge,

I've prepared a development branch which should also be working in Firefox, could you test whether you're having the same problem in this browser?
Tested with Firefox 21.0.

http://OX-604.oxalis.at

Only for testing purposes, don't do any productive work on it yet.

Do you know the username and password for those development branches or should I send those to you via mail?

[tmbo]

[author="tmbo", created="Sun, 26 May 2013 23:55:49 +0200"]

Ther still is some kind of problem with the data reloading/ positioning as you can see at the crosshair position.

[tmbo]

[author="", created="Mon, 27 May 2013 00:59:56 +0200"]

Looks very good to me! I'm not sure I'm seeing what you are seeing, Tom..

Best,
Kevin

[tmbo]

[author="", created="Mon, 27 May 2013 15:24:30 +0200"]

Alright, I tested the development branch in Firefox, but the nodes behave exactly the same as in chrome: They appear and disappear depending on the crosshair position. Seems as if the problem is not browser dependent for me. Maybe I could test an alternative graphics driver?

[tmbo]

[author="daniel", created="Tue, 28 May 2013 23:28:43 +0200"]

Norman Rzepka Any idea on what we could do/test here?

Would it be an option to install OpenGL and switch to --use-gl=desktop ?
I can't really narrow down the source of the problem, as firefox and chrome are afaik using different implementations of webGL this most likely won't be the problem here.
Also the exact same graphic drivers Helge is using are working for me (Windows 7 x64 NVIDIA GT540M with 314.22 WHQL).

So what else could be the problem?!

[tmbo]

[author="normanrz", created="Wed, 29 May 2013 23:07:11 +0200"]

In Mr.Doob's wiki entry it says that both Chrome and Firefox use the ANGLE renderer. Have you tried turning that off in Firefox aswell? https://github.com/mrdoob/three.js/wiki/How-to-use-OpenGL-or-ANGLE-rendering-on-Windows#firefox

OpenGL is installed by your graphics driver, so you should have it. I guess Chrome blacklists you drivers OpenGL-implementation or something.

[tmbo]

[author="daniel", created="Fri, 31 May 2013 20:36:15 +0200"]

Could you test that, Helge?

Set "webgl.prefer-native-gl" to "true" in about:config in Firefox.

[tmbo]

[author="", created="Sat, 1 Jun 2013 15:00:52 +0200"]

I tried it, and I dont get the message that WebGL is not installed as in Chrome. Unfortunately, the loading screen seems to be in a loop, since it does not finish loading when starting any kind of trace. I gave it now 10 minutes time, but it's still in the loading screen. Therefore I cannot say if this would solve the problem. Maybe this is also a hint to a problem with my native GL drivers?

[tmbo]

[author="daniel", created="Sat, 1 Jun 2013 17:27:10 +0200"]

Could you also check about:config for

webgl.force-enabled: true
webgl.enabled_for_all_sites: true
webgl.disabled: false

and of course webgl.prefer-native-gl: true

But I assume those are all set as it worked for you before you set prefer-native-gl to true.

What you then could do would be to go to about:support and check whether there is some message saying your graphic drivers are blocked or anything comparable.
Mine e.g. says in Graphics - WebGL renderer: Intel – Intel(R) HD Graphics Family
and it's working for me..

[tmbo]

[author="", created="Sat, 1 Jun 2013 19:44:06 +0200"]

webgl.force-enabled was not on true, but didnt make a difference when switched (since "disabled" was on false anyway)
webgl.enabled_for_all_sites is not an option I can choose, but again, if it was disabled, Oxalis would have told me as it did in Chrome I guess?

The about:support also tells me the same as in your environment:

WebGL-RendererIntel – Intel(R) HD Graphics

Maybe there is a possiblity to avoid Chrome blacklisting my WebGL if this is the case?

[tmbo]

[author="daniel", created="Sat, 1 Jun 2013 20:01:28 +0200"]

According to this page your drivers shouldn't be blacklisted:

https://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists#Chrome_on_Windows

and as I'm using the same graphics card and driver version this is unlikely to be the problem here.

That's a tough one here, I'm running out of ideas...

[tmbo]

[author="daniel", created="Wed, 5 Jun 2013 23:31:29 +0200"]

Last thing to try would be to use another version of your graphics drivers.

Can you remember what changed when oxalis stopped working correctly for you, maybe you updated your drivers?

[tmbo]

[author="daniel", created="Tue, 25 Jun 2013 19:38:22 +0200"]

Did you try anything else Helge?
Is it still not working for you?

[tmbo]

[author="", created="Wed, 26 Jun 2013 20:32:39 +0200"]

Hey,
It is still not working. The last things I tried were old versions of my nvidia driver. This time the V. 306.02 from August 2012. Still not working, sorry.