You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this issue when trying to load textures from Amazon S3 onto my Serve on EC2.
Inside examples/js/loaders/MTLLoader.js there's a static call at line 356, from MaterialCreature.createMaterial_
params[ 'map' ] = THREE.MTLLoader.loadTexture( this.baseUrl + value );
Inside of loadTexture() there's a reference to this.crossOrigin. Since "this" is a function and not an object, it returns null instead of whatever crossOrigin is set inside the created MTLLoader. This causes an issue where objects that successfully download from CORS aren't redrawn (because the canvas is dirty and the images crossOrigin attribute never gets set properly) and instead spew out "Uncaught Error: SecurityError: DOM Exception 18 " errors in the console.
To work around this locally, I just changed the line 436,
I noticed this issue when trying to load textures from Amazon S3 onto my Serve on EC2.
Inside examples/js/loaders/MTLLoader.js there's a static call at line 356, from MaterialCreature.createMaterial_
Inside of loadTexture() there's a reference to this.crossOrigin. Since "this" is a function and not an object, it returns null instead of whatever crossOrigin is set inside the created MTLLoader. This causes an issue where objects that successfully download from CORS aren't redrawn (because the canvas is dirty and the images crossOrigin attribute never gets set properly) and instead spew out "Uncaught Error: SecurityError: DOM Exception 18 " errors in the console.
To work around this locally, I just changed the line 436,
but I know that's not a permanent fix for the project.
Anyway, thought you guys should know.
The text was updated successfully, but these errors were encountered: