Hi all,
since a few days I’m experiencing a corrupt overview of the cell I’m tracing:
I’m running Eyewire on the latest version of Chrome.
Cheers,
eluchinat
Ooh, that’s new…
Can you give me some more details about your system? Windows/Mac/Linux? What browser & version? Do you happen to know what kind of graphics card you have?
Thanks
using “return to overview” I see the same image seen by Eluchinat
Ciao
Mario
Chrome - latest version, Windows XP
Here is what I am experiencing, with some more detail:
when I first login to eyewire, I don’t see the 3D neuron in the overview. It’s empty. No matter if I change cell.
If I start tracing some neuron (which works perfectly BTW), and then return to overview, I get the above result.
I have a notebook running Windows 7 64bit sp1, Chrome 23.0.1271.95 m (up to date), Nvidia GeForce GT240M.
I hope this helps.
Bye!
eluchinat
Cool, I’ll see if I can reproduce it on one of my machines. I’ll get back to you in a day or two.
Thanks for reporting this!
Hm I wonder if some webgl stats could help debug this…
If either of you can spare a minute, can you run the benchmark on:
http://webgl-bench.appspot.com/
http://webgl-bench.appspot.com/
Then copy+paste the results in this thread.
(Just to clarify, neither of you see the whole-cell when you first come to the site?)
Thanks in advance
Sure! Here you go:
userAgent = Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.95 Safari/537.11
GL_VERSION = WebGL 1.0 (OpenGL ES 2.0 Chromium)
GL_VENDOR = WebKit
GL_RENDERER = WebKit WebGL
GL_SHADING_LANGUAGE_VERSION = WebGL GLSL ES 1.0 (OpenGL ES GLSL ES 1.0 Chromium)
±-----------------------------------------±-------------+
| metric | value |
±-----------------------------------------±-------------+
| vtf/l1.dim128.strip.tps | 317831671 |
| vtf/l1.dim128.strip.dps | 9853 |
| uniqtex/l4.dim32.strip.tps | 56614079 |
| uniqtex/l4.dim32.strip.dps | 29456 |
| uniqtex/l4.dim64.strip.tps | 180498270 |
| uniqtex/l4.dim64.strip.dps | 22739 |
| caps/ALIASED_LINE_WIDTH_RANGE0 | 1 |
| caps/ALIASED_LINE_WIDTH_RANGE1 | 1 |
| caps/ALIASED_POINT_SIZE_RANGE0 | 1 |
| caps/ALIASED_POINT_SIZE_RANGE1 | 8192 |
| caps/ALPHA_BITS | 8 |
| caps/BLUE_BITS | 8 |
| caps/GREEN_BITS | 8 |
| caps/MAX_COMBINED_TEXTURE_IMAGE_UNITS | 20 |
| caps/MAX_CUBE_MAP_TEXTURE_SIZE | 8192 |
| caps/MAX_FRAGMENT_UNIFORM_VECTORS | 221 |
| caps/MAX_RENDERBUFFER_SIZE | 8192 |
| caps/MAX_TEXTURE_IMAGE_UNITS | 16 |
| caps/MAX_TEXTURE_SIZE | 8192 |
| caps/MAX_VARYING_VECTORS | 10 |
| caps/MAX_VERTEX_ATTRIBS | 16 |
| caps/MAX_VERTEX_TEXTURE_IMAGE_UNITS | 4 |
| caps/MAX_VERTEX_UNIFORM_VECTORS | 254 |
| caps/MAX_VIEWPORT_DIMS0 | 8192 |
| caps/MAX_VIEWPORT_DIMS1 | 8192 |
| caps/RED_BITS | 8 |
| caps/SAMPLE_BUFFERS | 1 |
| caps/SAMPLES | 4 |
| caps/STENCIL_BITS | 0 |
| caps/SUBPIXEL_BITS | 4 |
±-----------------------------------------±-------------+
I confirm that I don’t see the whole cell when I first come to the site.
Bye,
eluchinat
This will be fixed momentarily, doing some final testing on the fix.
userAgent = Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.95 Safari/537.11
GL_VERSION = WebGL 1.0 (OpenGL ES 2.0 Chromium)
GL_VENDOR = WebKit
GL_RENDERER = WebKit WebGL
GL_SHADING_LANGUAGE_VERSION = WebGL GLSL ES 1.0 (OpenGL ES GLSL ES 1.0 Chromium)
+------------------------------------------+--------------+
| metric | value |
+------------------------------------------+--------------+
| vtf/load_program_failed | 1 |
| uniqtex/l4.dim32.strip.tps | 9121974 |
| uniqtex/l4.dim32.strip.dps | 4746 |
| uniqtex/l4.dim64.strip.tps | 10903846 |
| uniqtex/l4.dim64.strip.dps | 1374 |
| caps/ALIASED_LINE_WIDTH_RANGE0 | 1 |
| caps/ALIASED_LINE_WIDTH_RANGE1 | 1 |
| caps/ALIASED_POINT_SIZE_RANGE0 | 1 |
| caps/ALIASED_POINT_SIZE_RANGE1 | 1 |
| caps/ALPHA_BITS | 8 |
| caps/BLUE_BITS | 8 |
| caps/GREEN_BITS | 8 |
| caps/MAX_COMBINED_TEXTURE_IMAGE_UNITS | 16 |
| caps/MAX_CUBE_MAP_TEXTURE_SIZE | 2048 |
| caps/MAX_FRAGMENT_UNIFORM_VECTORS | 29 |
| caps/MAX_RENDERBUFFER_SIZE | 2048 |
| caps/MAX_TEXTURE_IMAGE_UNITS | 16 |
| caps/MAX_TEXTURE_SIZE | 2048 |
| caps/MAX_VARYING_VECTORS | 8 |
| caps/MAX_VERTEX_ATTRIBS | 16 |
| caps/MAX_VERTEX_TEXTURE_IMAGE_UNITS | 0 |
| caps/MAX_VERTEX_UNIFORM_VECTORS | 254 |
| caps/MAX_VIEWPORT_DIMS0 | 2048 |
| caps/MAX_VIEWPORT_DIMS1 | 2048 |
| caps/RED_BITS | 8 |
| caps/SAMPLE_BUFFERS | 1 |
| caps/SAMPLES | 4 |
| caps/STENCIL_BITS | 0 |
| caps/SUBPIXEL_BITS | 4 |
+------------------------------------------+--------------+
It is fixed for me!
Thanks,
eluchinat
I am having the same problem.
I have tried Firefox 17 and Chromium 20.0.1132.47 Ubuntu 12.04 (144678)
GL version 1.4
GL_VENDOR Tungsten Graphics, Inc
GL_RENDERER Mesa DRI Intel® G33 x86/MMX/SSE2
GL_VERSION 1.4 Mesa 8.0.4
chrome://gpu-internals also gives me some recent error messages:
[10573:10573:122585994060:ERROR:gles2_cmd_decoder.cc(4867)] : glDrawXXX: attempt to access out of range vertices
[10573:10573:122586001895:ERROR:gles2_cmd_decoder.cc(4867)] : glDrawXXX: attempt to access out of range vertices
Currently this issue occurs when your graphics card supports fewer than 10 varying vectors. I’ll work on fixing this in the next few weeks.
Hello,
This is what I get
I do not see a constant colored 3D on the left side,
and i get a curropt neuron on the main page, it's all jagged and spikey
userAgent = Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17
GL_VERSION = WebGL 1.0 (OpenGL ES 2.0 Chromium)
GL_VENDOR = WebKit
GL_RENDERER = WebKit WebGL
GL_SHADING_LANGUAGE_VERSION = WebGL GLSL ES 1.0 (OpenGL ES GLSL ES 1.0 Chromium)
+------------------------------------------+--------------+
| metric | value |
+------------------------------------------+--------------+
| vtf/load_program_failed | 1 |
| uniqtex/l4.dim32.strip.tps | 10802810 |
| uniqtex/l4.dim32.strip.dps | 5621 |
| uniqtex/l4.dim64.strip.tps | 17174383 |
| uniqtex/l4.dim64.strip.dps | 2164 |
| caps/ALIASED_LINE_WIDTH_RANGE0 | 1 |
| caps/ALIASED_LINE_WIDTH_RANGE1 | 1 |
| caps/ALIASED_POINT_SIZE_RANGE0 | 1 |
| caps/ALIASED_POINT_SIZE_RANGE1 | 1 |
| caps/ALPHA_BITS | 8 |
| caps/BLUE_BITS | 8 |
| caps/GREEN_BITS | 8 |
| caps/MAX_COMBINED_TEXTURE_IMAGE_UNITS | 16 |
| caps/MAX_CUBE_MAP_TEXTURE_SIZE | 2048 |
| caps/MAX_FRAGMENT_UNIFORM_VECTORS | 29 |
| caps/MAX_RENDERBUFFER_SIZE | 2048 |
| caps/MAX_TEXTURE_IMAGE_UNITS | 16 |
| caps/MAX_TEXTURE_SIZE | 2048 |
| caps/MAX_VARYING_VECTORS | 8 |
| caps/MAX_VERTEX_ATTRIBS | 16 |
| caps/MAX_VERTEX_TEXTURE_IMAGE_UNITS | 0 |
| caps/MAX_VERTEX_UNIFORM_VECTORS | 254 |
| caps/MAX_VIEWPORT_DIMS0 | 2048 |
| caps/MAX_VIEWPORT_DIMS1 | 2048 |
| caps/RED_BITS | 8 |
| caps/SAMPLE_BUFFERS | 0 |
| caps/SAMPLES | 0 |
| caps/STENCIL_BITS | 0 |
| caps/SUBPIXEL_BITS | 4 |
+------------------------------------------+--------------+
any advice?
caps/MAX_VARYING_VECTORS | 8 |
Quoting echo:
Currently this issue occurs when your graphics card supports fewer than 10 varying vectors.