mop Posted December 23, 2014 Share Posted December 23, 2014 I am compositing my final result from several renderbuffers. Some of them render some additional effects. Simply rendering a scene to a texture and then displaying it works like a charm. But as soon as i add another effect on top of it strange things happen The result varies from 1.14 to 2.0 but both are broken. For 1.14 i made a bit of debugging and have a local hackfix which works for now: In Mesh.prototype.render var hardwareInstancedRendering = (engine.getCaps().instancedArrays !== null) && (batch.visibleInstances[subMesh._id] !== null);if (scene.hihi) {hardwareInstancedRendering = false;} No idea why it is related to instancing but this fix above works :S when i set hihi = true on my effectScene i get the desired rendering Any insights or even a non hacky fix? Here is a demo: http://www.babylonjs-playground.com/#WNIK9 Quote Link to comment Share on other sites More sharing options...
mop Posted December 23, 2014 Author Share Posted December 23, 2014 btw. for 1.4 a quick fix whgen using chrome (and that's how i found my hackfix) is to turn on the webglinspector extension. The extension seems to disable instancing support and then the result is as expected (red dot on greenish background). A version switcher for the playground would be great Quote Link to comment Share on other sites More sharing options...
julien-moreau Posted December 24, 2014 Share Posted December 24, 2014 Hello mop, To "properly" use render target textures, you should add your RTTs to your scenes just after creating them (http://www.babylonjs-playground.com/#WNIK9#1 line 17 & 55). Then, BabylonJS will do everything you need =D Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.