renderTarget argument has been removed in r102

Not a single issue with the current r101.
The problem started with the current 102dev.
I get hundreds of console warnings like this one:

THREE.WebGLRenderer.render(): the renderTarget argument has been removed. Use .setRenderTarget() instead. three.min.js:197:289
THREE.WebGLRenderer.render(): the forceClear argument has been removed. Use .clear() instead. three.min.js:197:434

I get those warnings with many samples.
Here is one of them:
http://necromanthus.com/Test/html5/Lara_mirror.html

Author: Fantashit

2 thoughts on “renderTarget argument has been removed in r102

  1. Folks, did you really improve anything with all these changes?

    Yes.

    1. The getCurrentViewport() saves on garbage collection (no new Vector4 created in every call).
    2. The renderTarget parameter removal simplifies how to know where is WebGLRenderer rendering to.

Comments are closed.