Seems horse model was wrong, it had one extra frame at the end (almost identical to the first frame), which caused our animation playback code to be incorrect in order to accommodate for this.

Side-effect was that two frame animations were completely broken.

Bah.

As per discussion in #1256

Also improved error reporting in JSONLoader (getting DEPRECATED errors for incorrect URLs was really confusing).

Default computation of morph normals for all models with morphs was taking unnecessary time and memory.

Also made it less resource intensive to recompute morph normals.

It seems to work, though not sure yet how to handle some things. Also for the moment it's implemented just for Lambert material.

As per discussion in #1207

As per discussion in #1201

Shadow cascades should be now a bit more under control.

Cascades can't be active together with multiple separate shadows, it's either one or the other. For this there is `renderer.shadowMapCascade` parameter.

Made colored shadow frustum debug visibility toggleable via `renderer.shadowMapDebug` parameter.

Fixed runaway globals in ShadowMapPlugin.

Fixed missing Gyroscope dependency in WebGL lib build.

This should make it work with cameras having parents other than scene root.

Added a silly check on Object3D.add(). It's a quick check and it avoids enless recursivity making the browser silently hang.

Not sure about this hardcoded epsilon thing for "isZero", also related strict equality check. Maybe these should be configurable somehow.

Now we can just do console.log(THREE.VERSION). Thanks for the suggestiong @chandlerprall!

Keeping the old IcosahadrenGeometry and OctahedronGeometry to double check results later.

It's Object3D subclass that takes a position from the scene graph hierarchy but uses its local rotation as world rotation.

It works like real-world gyroscope - you can move it around using hierarchy while its orientation stays fixed with respect to the world.

After shadow mapping fixes orthographic shadow projection finally started to work.

Work in progress. Still need to figure out some way to set up shadow camera automagically with respect to the actual camera (so that whole scene is shadowed when the camera moves). For the moment shadow camera needs to be handled manually (like for SpotLight).

As per discussion here: https://github.com/alteredq/three.js/commit/835b57addaf328412b61a2b644ff5efd7fe6d25e

Thanks GUI-DAT ;)

This should allow to have spotlights as a parts of hierarchy.

Sidenote: these extra verbose Closure warnings are starting to pay off - I keep catching subtle bugs (like missing dependencies in rarely used code corners).

This allows to have different shadow map parameters for different lights, also it's easier to access parameters for tweaking / debugging.

Changes:

renderer.shadowMapWidth    => spotLight.shadowMapWidth
renderer.shadowMapHeight   => spotLight.shadowMapHeight

renderer.shadowMapBias     => spotLight.shadowBias
renderer.shadowMapDarkness => spotLight.shadowDarkness

renderer.shadowCameraNear  => spotLight.shadowCameraNear
renderer.shadowCameraFar   => spotLight.shadowCameraFar
renderer.shadowCameraFov   => spotLight.shadowCameraFov

Also added new uniform type "v2v" for array of Vector2 (to support per-light sizes of shadow maps).