I’ve just upgraded my desktop and now the 3d view doesn’t work properly. Most of the time it’s just a blank grey window. Sometimes it flashes up the model briefly but then it goes blank again. Anyone else seeing a problem?
I don’t know if it’s just me on linux fedora 17 / 64 bit / firefox 12.
Yeah those examples are all fine. I can reproduce this issue on our site, I have a hunch it has to do with the depth buffer stuff I added to the 3d view. I’ll see if I can narrow down the issue today, and if not I’ll revert this feature.
Sorry for the issues @richardk & thanks for telling us
Thanks for the replies, what cool demos.
Just to confirm that all of them work, except the Vertex Buffer Object Example. I only get a black rectangle.
I’ve got a blank 3D view as well - just a grey box, no neuron.
I’m using Chrome on a Mac, so totally different setup…
@richardk As far as I can tell, this issue is only on Firefox on GNU Linux, and I haven’t yet been able to diagnose what’s causing it. It doesn’t seem to be related to what I thought, so unfortunately this means there’s nothing simple I can do to fix this, and will just have to dig deeper tonight/tomorrow.
Do you have some idea when the 3d view last worked for you in Firefox? Was it just a day or two ago, or closer to a week+?
@frabcus This issue shouldn’t affect Chrome, it’s possible you caught the site when I was tinkering with stuff so the 3d view was ephemerally broken. If you have a moment could you try refreshing the play page and tell me if your issue persists?
@richardk
Sorry for the inconvenience
Hi, this is happening for me too (Mac, Firefox 12). It stopped for me yesterday afternoon (NZ time)…maybe just over 24 hours ago. I just tried in Chrome (Version 20.0.1132.21 beta) and it didn’t work there either.
I also observed the same problem the last two days (Win7, FF12.0). However, sometimes the bits I added were displayed correctly and sometimes the whole 3D structure showed up when I submitted. Hope that helps.
Update: I just realized something odd. The 3D view is blank. However sometimes added pieces show up and are rendered properly. This only happens for neurons which do not belong to the original neuron. (E.g. if I click on a neighboring neuron deliberately). Bits which I add to the starting neurons or missing bits however do not show up. It seems as if somehow the software would be able to differentiate between correct additions and erroneous ones.
This is actually a different issue. The issue @richardk is describing requires that you can’t even see the cube in 3d, but I think you are both only missing the neuron segments.
Anyways, I think I’ve fixed the issue you’re both experiencing now.
It had to do with a cache pointing to stale files that had been swept up by the server. These stale files were any segments someone had selected in the task you were working on before you had done it. That’s why the system appeared to know the difference between correct and incorrect segments.
This one is still affecting me, FF (iceweasel 10.0.4) on 32bit Debian.
I’m not familiar with how Iceweasel version numbers map onto FF version numbers, but as far as I can tell this issue affects FF 12 only.
FF 11 and FF 13+ (beta, nightly, etc) do not seem have this issue, nor do any webkit browsers. I have not yet been able to figure out why FF 12 fails in this way.
I’ve just upgraded to fedora 13.0 and it’s still not working properly. Sometimes it will display, but it quickly goes blank again, and it goes blank if I try to do anything to it. At other times I seen just the empty cube but that disappears too. I think the scaling and orientation is a bit odd, but it doesn’t stay on screen long enough to tell.
What version of firefox is it? If you use chrome does it work?
Sorry, I meant to say firefox 13.0, the latest update from the fedora 17 repo.
I haven’t tried chrome.
Ditto, 3D image is missing (shows up for a fraction of a second then goes away)
Firefox 13, Fedora 17 i686, Radeon X1400M (open source driver)
Out of curiosity, can you try visiting
There should be a spinning cube, does the cube exhibit the same behavior? (shows up for a split second then disappears, or doesn’t show up at all)
I just realized there’s a preference FF’s about:config which is “prefer-native-gl”. When I enabled that FF displayed 3d correctly for me. Let me know if this resolves anyone else’s issue as well?