Open PaulKinlan opened 5 years ago
This must have to do with the nebula.
It seems non-critical and device specific, but I’ll take a look when I get around to it.
@jakearchibald is seeing this too. Moving back into MVP. Will tackle this one at home where I have my Pixelbook.
I'm also now seeing the following when the gameboard shows.
shaderbox.ts:155 WebGL: INVALID_VALUE: vertexAttribPointer: index out of range
t @ shaderbox.ts:155
(anonymous) @ renderer.ts:53
p @ renderer.ts:69
(anonymous) @ index.tsx:181
(anonymous) @ bootstrap.ts:41
(anonymous) @ bootstrap.ts:41
(anonymous) @ bootstrap.ts:41
a @ bootstrap.ts:41
(anonymous) @ index.tsx:177
r @ index.tsx:85
B @ bootstrap.ts:41
U @ bootstrap.ts:41
u @ bootstrap.ts:41
Promise.then (async)
c @ bootstrap.ts:41
setState @ bootstrap.ts:41
(anonymous) @ bootstrap.ts:41
Promise.then (async)
r @ bootstrap.ts:41
B @ bootstrap.ts:41
(anonymous) @ bootstrap.ts:41
N @ bootstrap.ts:41
(anonymous) @ bootstrap.ts:41
N @ bootstrap.ts:41
x @ bootstrap.ts:41
U @ bootstrap.ts:41
u @ bootstrap.ts:41
Promise.then (async)
c @ bootstrap.ts:41
setState @ bootstrap.ts:41
(anonymous) @ bootstrap.ts:41
(anonymous) @ comlink.ts:120
(anonymous) @ bootstrap.ts:41
(anonymous) @ bootstrap.ts:41
(anonymous) @ bootstrap.ts:41
a @ bootstrap.ts:41
(anonymous) @ comlink.ts:96
shaderbox.ts:163 WebGL: INVALID_VALUE: enableVertexAttribArray: index out of range
Yeah, those are kind of race-y one-off errors, but they are basically fixed by the time the next frame ships.
I can’t reproduce these errors on my Pixelbook.
Can y’all check again?
On a Pixelbook it errors with 256x
[.WebGL-0x271131c86700]GL ERROR :GL_INVALID_OPERATION : glFramebufferTexture2D: <- error from previous GL command
WebGL: too many errors, no more errors will be reported to the console for this context.
On the plane this seemed to cause the game not to load on the device (but it worked on Pixel) - however now testing locally the board loads fine.