Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WebGLRenderer.autoClear = false doesn't work.

See original GitHub issue

Not sure when this got broken, but it doesn’t seem to work either on the master nor dev branches…

Issue Analytics

State:
Created 12 years ago
Comments:23 (19 by maintainers)

Top GitHub Comments

1reaction

mrdoobcommented, Sep 28, 2011

Oh! So for doing such trail effects you need to do

renderer = new THREE.WebGLRenderer( { preserveDrawingBuffer: true } );

I see I see! I guess something changed from some months ago.

0reactions

mrdoobcommented, Oct 13, 2011

@koblin there is also this new example to have this use case under control http://mrdoob.github.com/three.js/examples/webgl_trails.html

Top Results From Across the Web

three.js - Use both autoclear and preserveDrawingBuffer in ...

If you are instantiating WebGLRenderer and preserving the drawing buffer like so: var renderer = new THREE. ... autoClear = false;.

WebGLRenderer#autoClear – three.js docs

First, set autoReset to false . renderer.info.autoReset = false; Call reset() whenever you have finished to render a single frame. renderer.info.reset(); ...

Solved: How to make material opacity and transparent in Ex...

... webgl renderer this.renderer = new WebGLRenderer({ context: context.gl, alpha: true, antialias: true }); this.renderer.autoClear = false ...

Working with the Camera - Three.js - page 142

WebGLRenderer , we set the autoclear property to false . ... This makes sure the 2D overlay is rendered completely on top and...

Viewport and low level operations - CGwith3JS - Google Sites

Multi-Viewport Rendering. The default settings in WebGLRenderer simplify many things: ... autoClear = false; ... Otherwise, it wont work properly.