fix(graphics): rendering textured meshes on some machines

Some machines seem to have an issue with not passing the instance UVs.
It should default to zero, but it seems to not work as expected. Not
sure if this a difference in behaviour from the GPU/OS/something else.

.changeset/short-falcons-raise.md

@@ -0,0 +1,5 @@
+---
+'@tedengine/ted': patch
+---
+
+Fix rendering problems with textured meshes on some machines

packages/ted/src/renderer/renderable-textured-mesh.ts

@@ -50,7 +50,8 @@ export default class TRenderableTexturedMesh {
       !this.indexBuffer ||
       !this.uvBuffer ||
       !this.normalBuffer ||
-      !this.colorFilterUniformLocation
+      !this.colorFilterUniformLocation ||
+      !this.instanceUVBuffer
     ) {
       return;
     }
@@ -76,13 +77,22 @@ export default class TRenderableTexturedMesh {
       instanceUVs ? 1 : 0,
     );
 
-    if (instanceUVs && this.instanceUVBuffer) {
+    if (instanceUVs) {
       gl.bindBuffer(gl.ARRAY_BUFFER, this.instanceUVBuffer);
       gl.bufferData(
         gl.ARRAY_BUFFER,
         new Float32Array(instanceUVs),
         gl.STATIC_DRAW,
       );
+    } else {
+      // Even if instanceUVs are not provided, we need to bind the buffer
+      // Some machines seem to require this, otherwise the shader will fail.
+      gl.bindBuffer(gl.ARRAY_BUFFER, this.instanceUVBuffer);
+      gl.bufferData(
+        gl.ARRAY_BUFFER,
+        new Float32Array(this.uvs),
+        gl.STATIC_DRAW,
+      );
     }
 
     const vertexCount = this.indexes.length;