The 3D cube view just shows an empty grey box with the white cut through. The 2D view seems to be working as it should though. I used to be able to see the 3D view fine a while ago.
If you let it sit for a minute does the 3D eventually appear? Some people have been experiencing a lag this morning.
Nope, it doesn’t show up however long I wait
Hmmm, if you’re not getting these all the time I’d just skip it when it happens.
I have this problem too, and have never seen the 3d on my cubes. Not on the tutorials or the ones I’ve done. I joined a few days ago, but it’d be quite helpful to see the 3d. I’ve updated my browsers, and have tried in firefox and chrome with the same result.
i have something kind of similar right now - it only partially showed up. very strange. i’m going to keep working on the cube, even though not having the 3d model (fully) makes it harder 
…trying to upload the screenshot, but doesn’t seem to be working. basically, it’s just random shards of color disbursed in the 3d model, though 2d looks fine.
My 3d cubes are all empty, too. I’ve tried skipping a few, but none show up, no matter how long I wait.
I’m on Win7, FF 17
Could one or two of you open up the javascript console and see if there are any errors?
Lots of errors and warnings in my javascript console…
- Could not initialise shader VALIDATE_STATUS: false, gl error [0] Three.js:18239
WebGL: INVALID_OPERATION: getUniformLocation: program not linked / (1):1
WebGL: INVALID_OPERATION: getAttribLocation: program not linked / (1):1
WebGL: INVALID_OPERATION: useProgram: program not valid / (1):1
.WebGLRenderingContext: GL ERROR :GL_INVALID_OPERATION : glDrawArrays: attempt to access out of range vertices in attribute 1 / (1):1
WebGL: INVALID_OPERATION: useProgram: program not valid
The last one is repeated 200+ times, then it says it's getting tired of errors and won't report any more.
Thanks! We’ll take a look at it!
This looks like a case of hardware not supporting some functionality we are using. Could any of you try running the tests here: http://webgl-bench.appspot.com/ and copy&pasting the results in this thread? Thanks.
I do have a somewhat older computer, I guess. Please let me know if there’s any tweak I can do so I can participate.
This is what I got from the test.
userAgent = Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 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 | 10248182 |
| uniqtex/l4.dim32.strip.dps | 5332 |
| uniqtex/l4.dim64.strip.tps | 11243626 |
| uniqtex/l4.dim64.strip.dps | 1416 |
| 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 |
±-----------------------------------------±-------------+
When I first did the tutorial and early on afterward, the 3D image showed up fine. Now I can see the cube, can see the plane in the cube, but see no 3D image.
Ran tests. Results:
userAgent = Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 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 | 4362233 |
| uniqtex/l4.dim32.strip.dps | 2270 |
| uniqtex/l4.dim64.strip.tps | 7367053 |
| uniqtex/l4.dim64.strip.dps | 928 |
| 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 |
±-----------------------------------------±-------------+
Does this help or do you need something else?
Here’s my results from this:
userAgent = Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 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 |
| 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 |
±-----------------------------------------±-------------+
Hey All,
So it appears that this issue stems from the fact that you guys only support 8 varying vectors. With graphics programming, it’s always a trade off between neat effects and broad support. In the future, we will try to do better at detecting these situations where things are not supported, and either let the user know that they are not supported or downgrade the effects. Unfortunately, it currently looks like it might be a while before we can make such a change. Hope the experience isn’t too bad in the mean time.
sadface
Oh, how disappointing. I find it’s not playable without the 3D cube there as a guide.
Sorry, but all that code is a little frightening - what does this mean? That I won’t be able to see the 3d anymore? Because nothing I’ve tried helps, and apparently I should be able to see it. I used to be able to.