WebGL: INVALID_ENUM: getInternalformatParameter: invalid internalformat

Unity Engine
, , , , ,
1

On my WebGL build on Unity 6000.0.14f1, I’m getting the following error message in my Mac Chrome console - the scene isn’t loading. Any idea where I can start debugging this?

bud-unity-web.framework.js:12341 WebGL: INVALID_ENUM: getInternalformatParameter: invalid internalformat
_glGetInternalformativ @ bud-unity-web.framework.js:12341
$gles::InitRenderTextureAACaps(ApiGLES*, GraphicsCaps*) @ bud-unity-web.wasm:0xf45409
$ApiGLES::Init(GfxContextGLES const&, GfxDeviceLevelGL&) @ bud-unity-web.wasm:0xf40de5
$GfxDeviceGLES::Init(GfxDeviceLevelGL) @ bud-unity-web.wasm:0xf28551
$CreateGLESGfxDevice(GfxDeviceRenderer) @ bud-unity-web.wasm:0xf27815
$CreateRealGfxDevice(GfxDeviceRenderer) @ bud-unity-web.wasm:0x11b48fb
$CreateClientGfxDevice(GfxDeviceRenderer, GfxCreateDeviceFlags) @ bud-unity-web.wasm:0xfbaa10
$InitializeGfxDevice() @ bud-unity-web.wasm:0x11b5242
$InitializeEngineGraphics(bool) @ bud-unity-web.wasm:0x139f7d6
$PlayerInitEngineGraphics(bool) @ bud-unity-web.wasm:0x3ab5f9
$RunWebGLPlayer() @ bud-unity-web.wasm:0x127a04e
$ObtainedWebGpuDevice(int, void*) @ bud-unity-web.wasm:0x127a9ec
cb @ bud-unity-web.framework.js:14107
(anonymous) @ bud-unity-web.framework.js:13725
Promise.then
_wgpu_adapter_request_device_async @ bud-unity-web.framework.js:14116
$ObtainedWebGpuAdapter(int, void*) @ bud-unity-web.wasm:0x127a9b7
cb @ bud-unity-web.framework.js:13743
(anonymous) @ bud-unity-web.framework.js:13725
Promise.then
_navigator_gpu_request_adapter_async @ bud-unity-web.framework.js:13745
$InitWebGLPlayer(int, char**) @ bud-unity-web.wasm:0x127a74c
$main @ bud-unity-web.wasm:0x127aa1a
(anonymous) @ bud-unity-web.framework.js:834
callMain @ bud-unity-web.framework.js:15982
doRun @ bud-unity-web.framework.js:16020
run @ bud-unity-web.framework.js:16032
runCaller @ bud-unity-web.framework.js:15965
removeRunDependency @ bud-unity-web.framework.js:792
(anonymous) @ bud-unity-web.framework.js:194
doCallback @ bud-unity-web.framework.js:2653
done @ bud-unity-web.framework.js:2664
reconcile @ bud-unity-web.framework.js:2097
(anonymous) @ bud-unity-web.framework.js:1878
index.openKeyCursor.onsuccess @ bud-unity-web.framework.js:1971
IndexedDB
(anonymous) @ bud-unity-web.framework.js:1968
req.onsuccess @ bud-unity-web.framework.js:1918
IndexedDB
getDB @ bud-unity-web.framework.js:1893
getRemoteSet @ bud-unity-web.framework.js:1958
(anonymous) @ bud-unity-web.framework.js:1874
getLocalSet @ bud-unity-web.framework.js:1951
syncfs @ bud-unity-web.framework.js:1872
(anonymous) @ bud-unity-web.framework.js:2671
syncfs @ bud-unity-web.framework.js:2667
unityFileSystemInit @ bud-unity-web.framework.js:192
(anonymous) @ bud-unity-web.framework.js:197
callRuntimeCallbacks @ bud-unity-web.framework.js:4076
preRun @ bud-unity-web.framework.js:664
run @ bud-unity-web.framework.js:16007
runCaller @ bud-unity-web.framework.js:15965
removeRunDependency @ bud-unity-web.framework.js:792
(anonymous) @ bud-unity-web.framework.js:920
Promise.then
loadWasmModuleToAllWorkers @ bud-unity-web.framework.js:4054
receiveInstance @ bud-unity-web.framework.js:920
receiveInstantiationResult @ bud-unity-web.framework.js:928
Promise.then
(anonymous) @ bud-unity-web.framework.js:896
Promise.then
instantiateAsync @ bud-unity-web.framework.js:894
createWasm @ bud-unity-web.framework.js:938
(anonymous) @ bud-unity-web.framework.js:15824
(anonymous) @ bud-unity-web.loader.js:1357
Promise.then
loadBuild @ bud-unity-web.loader.js:1355
(anonymous) @ bud-unity-web.loader.js:1435
Promise.then
(anonymous) @ bud-unity-web.loader.js:1434
createUnityInstance @ bud-unity-web.loader.js:1405
2

Encountering same issue. Did you manage to resolve this?

3

Hi @jameswedailabs.

Could you please provide more information about this issue?

The behaviour that you are observing might potentially be a bug in Unity. Could you please submit a bug report with the project?
Here’s the info on how to submit a bug report bug-reporting.

Thank you

4

Been encountering this also. if we upload a uncompressed file to the web server it has this error and it does not load the scene. btw we are using ngix.config. gpt says there are some lines that should be included in the ngix config
types {
application/wasm wasm; # Defines .wasm files as WebAssembly (WebGL needs this)
application/javascript js; # Ensures .js files are served as JavaScript
application/json json; # Ensures .json files are served as JSON
application/octet-stream data; # Serves .data files correctly (binary files)
}

5

For what it’s worth, I am experiencing this as well. Started a couple of days ago when I was experimenting with lighting quality & global illumination. Can’t seem to find the setting that’s causing it, and even building from a backup produces crashing builds. (browser locks up & I have to force quit)

6

Just wanted to say, that for some situations this is a false lead:

I spent a bunch of time trying to “fix” this message thinking it was the issue blocking my scene from loading correctly…but it turned out that a file-access step which worked on Windows (using EasySave asset) was silently failing in the browser, and once I removed that, the scene loads and the INVALID_ENUM msg continues to appear in the browser but doesn’t seem to do anything bad now.

7

also getting this error for a default scene with a cube and default build settings for webgl. background is rendering but nothing else, whatever I try. Tested in Unity versions 6000.0.40f1 and 6000.2.0b7

8

Hello,

I think we’ll need to get more information and take a look at one of these projects to be able to assist here. Could you please log a bug for this and attach a project that reproduces the issue? Here’s a link on how you can log a bug: How-do-I-submit-a-bug-report

Thanks!