ColladaLoader now loads a Scene instead of an Object3D

[Baccanno]

ColladaLoader now loads a 'Scene' instead of an 'Object3D' in the '.scene' field of the callback parameter.

It's not an issue rather a fix but the info is somehow interesting.

I had a regretion due to that as I was performing a deep copy of the object in order to have instances not sharing materials indeed clone functions of Object3D and Scene are slightly different

[mrdoob]

Added to the Migration page.

[WestLangley]

Why is ColladaLoader implented to return a Scene instead of an Object3D?

[mrdoob]

Hmmm... It was for making it renderable... 17a4ae3

[WestLangley]

Sorry, I do not understand what "making it renderable" means in this case...

Also, the returned scene has scale applied by the loader. Usually we do not scale a scene.

And furthermore, in the loader callback, users end up adding the returned scene as a child of another scene.

Unless I am missing something, the loader should return an Object3D with children... No?

[mrdoob]

Sorry, I do not understand what "making it renderable" means in this case...

It means that WebGLRenderer can only do render.render( THREE.Scene, THREE.Camera ). It can't do renderer.render( THREE.Object3D, THREE.Camera ). Well, that's not true. Since r69 we can now render a single object (or group) but updateMatrix may not be being called...

Unless I am missing something, the loader should return an Object3D with children... No?

Yeah, you're making me reconsider...

[Baccanno]

I would agree with @WestLangley although you can use the collada loader for a scene it may happen quite often that you only want to load an Object3D to add anywhere, adding a scene to as scene could probably add sides effects and confusion no ?

[mrdoob]

Yesh... I agree. I'll revert! :)