# Loading serialized scene containing mesh(es) with texture(s) leads to 'Failed to execute 'texImage2D' on 'WebGL2RenderingContext': Overload resolution failed.' error

**URL:** <https://forum.babylonjs.com/t/loading-serialized-scene-containing-mesh-es-with-texture-s-leads-to-failed-to-execute-teximage2d-on-webgl2renderingcontext-overload-resolution-failed-error/16764>\
**Category:** Questions\
**Created:** [December 19, 2020, 3:54am UTC](https://forum.babylonjs.com/t/loading-serialized-scene-containing-mesh-es-with-texture-s-leads-to-failed-to-execute-teximage2d-on-webgl2renderingcontext-overload-resolution-failed-error/16764 "2020-12-19T03:54:10Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![aWeirdo](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/aweirdo/32/52_2.png) [@aWeirdo](https://forum.babylonjs.com/u/aWeirdo)\
**Post date:** [December 20, 2020, 6:30pm UTC](https://forum.babylonjs.com/t/loading-serialized-scene-containing-mesh-es-with-texture-s-leads-to-failed-to-execute-teximage2d-on-webgl2renderingcontext-overload-resolution-failed-error/16764/9 "2020-12-20T18:30:18Z")

</div>

@emmbema  
Is that with webgpu enabled?  
If yes, can you try disabling it?  
if possible, can you try with 4.2.0?

It will help pin-point if the issue comes from webgpu update, your setup / if executeWhenReady runs before texture is fully loaded and ready to be read.

**Texture.ForceSerializeBuffers** wont change the URL of the serialized texture (for easy removing the base64string /reverting to load from url again)  
this is not a problem, on load, if base64string exists, url is ignored.

---

_[View the full topic](https://forum.babylonjs.com/t/loading-serialized-scene-containing-mesh-es-with-texture-s-leads-to-failed-to-execute-teximage2d-on-webgl2renderingcontext-overload-resolution-failed-error/16764)._