It doesn't have effect there anyway as scene is rendered to FBO without multisampling.
Turning antialiasing off here didn't have much effect on performance though (unlike for particles).
Also updated GUI-DAT (didn't help with recent Chrome compositing bugs, though this is Chrome Windows issue), added FileAPI to Detector and fixed aspect ratio bug in WebGLRenderer.
Clearing API for rendering to RenderTarget is now flipped: before forced clearing of render target was default, now no clearing is default.
New way of doing things saves one extra duplicitous clear call when switching render targets (like when doing postprocessing).
(doing documentation is indeed turning out to be useful)
Went through all examples, all should work.
JSON files exported from Blender / converted from OBJ files still use underscored property names internally. I don't know, should these also be changed?
Now you can add keyboard + mouse camera control with a single line, just change camera type and add parameters:
camera = new THREE.QuakeCamera( { fov: 50, aspect: window.innerWidth / window.innerHeight, near: 1, far: 10000,
movement_speed: 1, look_speed: 0.002, nofly: true, look_vertical: false } );
Thanks to mrdoob for suggestions ;)
Mr.doob
alteredq
Chris Killpack
Mr.doob