[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Latest Chrome Render to Cubemap bug?

I found the same thing recently. Both Chrome and Firefox were having issues for me. On Firefox an error was being displayed as:

"Error: WebGL: A texture is going to be rendered as if it were black, as per the OpenGL ES 2.0.24 spec section 3.8.2, because it is a cube map texture, with a minification filter requiring a mipmap, and is not mipmap cube complete (as defined in section 3.7.10)."

So I changed the cube texture to use mip maps and it worked again. Not sure if this is related to your problem but the symtoms, and timing, are the same for me. The spec mentioned above seemed to suggest it should break if the min filter requires mipmaps and there are none setup (which makes sense - but seems incorrect as my previous setup was linear filtering without mipmap generation)

On Mon, Jan 26, 2015 at 6:30 PM, Geoff Lang <geofflang@google.com> wrote:

No conformance test yet, it's on my to-do list.

I wrote a small test in ANGLE when I fixed the bug and it's running on the chrome waterfall for now.

On Mon, Jan 26, 2015, 5:50 PM Florian Bösch <pyalot@gmail.com> wrote:
Is there a conformance test for that kind of bug? There wasn't one on the ticket...

Mathew Henson

tel: 00 44 (0)7907582537