I understand that mipmaps don’t work on WebGL, but I want to be able to suppress the warning about it in a WebGL build. After our game has been running for a while there have been several thousand of these warnings logged to the console:
Warning: Rendering to mipmap levels other than zero is not supported on this device
It makes diagnosing actual problems really difficult when the browser log has been clogged by them.
From what I understand, it’s not possible to disable mipmaps per-platform and we want mipmaps on other platforms, so disabling mipmap generation on the relevant textures isn’t an option. I could just replace the browser’s console.warn function to detect and stop the warning, but that seems a little unnecessary to me.
Basically what I want to know: Is there an easy way to disable/supress the warning?
I narrowed it down, I get the warnings at two points:
When we load a new scene for about 20 or so times until the scene is loaded.
When the canvas element is re-sized or hidden. We allow the user to re-size the canvas window to help with frame-rate and we hide the canvas when an error occurs. This can also happen sometimes if you move the tab out of a window.
I turned off our only post-effect (Antialiasing) and it seemed to have not effect.
I’m suffering the same warning and I’ve figured out the 2 causes (in my case):
Post-effects
Render to texture (with a code pretty similar to the one in this thread)
In the case of the post-efects, it triggers every frame for the edge detection effect and just one every time I toggle the ambient occlusion effect.
Is it possible to set the mipmap count of the render textures? I guess the post-effects need to be reviewed more in-depth to see if I can fix them.
I can’t share because it’s under nda stuff at work, but It’s just a scene that loads a model and has the Edge detection effect on. That generates warning every frame.
There are other effects on the camera that toggle on/off, such as Screen Space Ambient Occlussion and Color correction curves (for HDR stuff, although HDR is currently switched off right now).
In the case of the warning being generated by rendering to a texture (basically to get a screenshot) I haven’t been able to figure out how to avoid the warning.
[Edit] Just made a quick scene to test and yes, got the warning (although not every frame). I’ll try to upload a project (in the mean time it’s just a blank scene with two objects and the edge detection effect on the camera).
I’ve also had the warning, that I tracked down to mip maps. It occurred as the webgl app was about to start. Sometimes it seemed to clear itself after 15 mins or so and the app started.
The fix was to turn off all the mip maps in the first scene. The error doesn’t seem to occur again in subsequent scenes.
Unity 5.3.7
