Hi there, I can’t seem to get the 3D view at all. I get the grey scale plane ok and can rotate it, scroll in etc. but cannot see the neuron on it. What am I doing wrong? I’m using the Chrome browser.
Thanks
hey meeshcoates,
Did you select some stuff in the 2d on ther right? When you select things on the right they should show up in 3d on the left. There might be a short delay before they do.
Matt
Yep tried that. If I repeatedly click just outside of the cube I can see the black outline like a shadow but then it disappears. I also don’t see the spinning neuron when I log in, could that be something to do with it? I checked whether my WebGL was disabled in Chrome Flags and it is…
Hey messhcoates,
Try clicking this link, do you see a spinning cube? If not your WebGL is not working.
On the Chrome:flags page WebGl should be enabled, it’s a bit tricky because it’s a double negative. If below WebGL it says “Disable” it means that WebGL is enabled. If below WebGL it says enable, that means it’s disabled. Annoying isn’t it?
Hi Rachel, clicked the link and…can see the spinning cube so the WebGL is working. Nuts. Now what?
Nuts indeed. Here’s a screenshot of what you should be seeing.
If what I understand is correct, you’re seeing everything except the blue? And you’re still not seeing a big rotating neuron when you’re on the home page?
Have a look...
I see the segment in that 3d view. It’s just black. Probably a coloring issue? How old is your machine?
Not old. No it’s only black occasionally when i double click outside of the cube and then disappears as soon as I click somewhere else on the screen. Could it be something do to with shaders?
Here’s my Webgl performance info:
userAgent = Mozilla/5.0 (Windows NT 6.2) 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 | 10268091 |
| uniqtex/l4.dim32.strip.dps | 5342 |
| uniqtex/l4.dim64.strip.tps | 11702211 |
| uniqtex/l4.dim64.strip.dps | 1474 |
| 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 |
±-----------------------------------------±-------------+
Unfortunately, it’s an issue with your graphics card. See this thread over here. The issue is with the number of supported varying vectors. We may be able to support this machine in the future, but not at the moment.
Hi Matt, I’ve come to that conclusion myself. So annoying as it’s the only laptop in the house at the moment. I might have to ‘appropriate’ one from the office.
Thanks for your help.
Michelle