Limitations:
- Chrome can handle up to 5 lights in total (directional + point)
- Firefox seems to handle up to 29 lights
These number are GPU specific (mine is ATI Mobility Radeon 3650).
This turned out to be quite tricky. The number of varying vectors in shaders is limited. Additionally Chrome and Firefox have different limitations (at least on Windows, probably due to Chrome using ANGLE as rendering backend).
Hence WebGLRenderer has hardcoded limit of maximum 5 lights.
WebGLRenderer constructor now takes (optional) scene argument, so that numbers and types of lights present in the scene can be used to generate minimal possible shader.
If no scene is passed, shader allowing 1 directional + 4 point lights will be generated.
Changed OBJ -> Three.js converter to use new materials system (eventual old models need to be reconverted).
Limitations:
- one use case is now much slower
- when a mesh has each face with different color (e.g. polyfield in examples/test.html)
- before this used FaceColorFill material and in WebGLRenderer it was rendered fast with color attribute array
- now when FaceColorFill material is gone, each face gets own VBO :(
- material sorting uses Materials "toString" methods for hashing, so it's very important to keep these in a good shape
In Chrome it looks more or less ok, but it has some problem in Firefox 4 (with some camera angles there are black areas around edges).
Also updated Python builder scripts and examples to include this new material.
* Removed MeshFaceColorFillMaterial and MeshFaceColorStrokeMaterial
* Added MeshFaceMaterial ( it uses the face.material for that pass )
* CanvasRenderer and SVGRenderer per face material logic changed.
* SVGRenderer supports particles again.
* WebGLRenderer currently broken :/
* Code clean up
Old version was doing massive overdraw (whole mesh was drawn for each material).
Even current solution is still quite messy: there is a different behavior for stroke and fill materials (when used as secondary materials).
Stroke materials are applied to the complete mesh (as most common use case seems to be wireframe) while fill materials now apply only to faces within single material group (when "decalIndex" property of secondary fill material is set).
There were two problems:
- vertices were in a different coordinate system than normals
- generated JS code was not properly handling normals with 0-sized components
Changed WebGLRenderer to use 3x3 normal matrix.
Limitations of WebGL lights:
- currently handles only single one of each ambient/directional/point light
- light intensity modifier not yet taken into account
- only diffuse term (this applies also in CanvasRenderer)
alteredq
Mr.doob
Julian Walker
Mark DiMarco