Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loader.createMaterial: Unsupported colorAmbient and mapAmbient errors #8034

Closed
BrodaNoel opened this issue Jan 29, 2016 · 3 comments
Closed

Comments

@BrodaNoel
Copy link

Version: THREE.WebGLRenderer 73
Windows 7, Firefox 44.0

I'm getting those errors in console log:

THREE.WebGLRenderer 73
scripts.js (línea 1047)
GET http://local.xxx.com/files/escena.json
Loader.createMaterial: Unsupported colorAmbient [0.7, 0.7, 0.7]
Loader.createMaterial: Unsupported mapAmbient da01f132.dds
Loader.createMaterial: Unsupported colorAmbient [0.7, 0.7, 0.7]
Loader.createMaterial: Unsupported mapAmbient 3fc5e191.dds
Loader.createMaterial: Unsupported colorAmbient [0.7, 0.7, 0.7]
Loader.createMaterial: Unsupported mapAmbient e71c68d2.dds
Loader.createMaterial: Unsupported colorAmbient [0.7, 0.7, 0.7]
Loader.createMaterial: Unsupported mapAmbient f71d20d6.dds
Loader.createMaterial: Unsupported colorAmbient [0.7, 0.7, 0.7]
Loader.createMaterial: Unsupported mapAmbient 0e3bf8b2.dds

The zip file (http://warriots.com/allinfo.zip) contain:
folder Chamber Of Secrets (file to be transformed to .json file)
obj2json.py: transformer downloaded from this repo a few hours ago
index.html: file with the html and js content
escena.json: JSON file to be rendered. Output of the chamber of secret.obj file.

Why Chamber of secret? Well... I just downloaded an example from the web...
Probably that is the issue... Some old 3dMax version. I really don't know.
Here the file: http://tf3dm.com/3d-model/chamber-of-secrets-scene-45247.html

If you don't feel confident opening that .zip file, let me know and I could send you all files with no .zip file

Error:
sin titulo

@Wilt
Copy link
Contributor

Wilt commented Jan 29, 2016

It might happen because ambient was removed from material from r71.
You can read that in the release notes here.

@Mugen87
Copy link
Collaborator

Mugen87 commented Feb 2, 2016

@mrdoob I've seen in dev, that THREE.Loader.createMaterial produces a warning for colorAmbient(see below), but not for mapAmbient. Do you think, we should add mapAmbient in the same way like colorAmbient (so users get a warning and not an error)?

case 'colorAmbient':
    console.warn( 'THREE.Loader.createMaterial: colorAmbient is no longer supported' );
    break;

@mrdoob
Copy link
Owner

mrdoob commented Feb 9, 2016

@Mugen87 nice catch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants