webgl_shaders_ocean triggers warnings

Description of the problem

In the current dev commit of webgl_shaders_ocean @ 1715e623ecf7b451bfef7f460cd7b2cb0828d9e6 I’m getting

[.WebGL-0x3830e6afbc00]RENDER WARNING: texture bound to texture unit 0 is not renderable.
It maybe non-power-of-2 and have incompatible texture filtering.

while in the current master webgl_shaders_ocean @ 5360a81b8c557ed255e97b87c49e7d00b546b795 changing the azimuth or the inclination slider causes

[.WebGL-0x3830e6ba8100]GL ERROR :GL_INVALID_OPERATION : glDrawArrays:
Source and destination textures of the draw are the same.

Both of them > 255 times, i.e. WebGL: too many errors, no more errors will be reported to the console for this context. follows.

Three.js version

• Dev (1715e623ecf7b451bfef7f460cd7b2cb0828d9e6)
• r98 (5360a81b8c557ed255e97b87c49e7d00b546b795)

Browser

• Chrome

OS

• Linux

Hardware Requirements (graphics card, VR Device, …)

Intel Core i7 integrated graphics, Intel something 4000? maybe 4500?

[Mugen87]

Oh, I see. Yeah, the ico-sphere looks slightly different. Here are the links:

https://threejs.org/examples/webgl_shaders_ocean.html https://raw.githack.com/mrdoob/three.js/dev/examples/webgl_shaders_ocean.html

[Mugen87]

Thanks for testing! Yes, the warnings are caused by another issue. The lighting problem was introduced with #15236, hence the simple fix.