next »

[Marvin Fröhlich]

I have noticed, that disabling the Clipper gives a little performance boost for the whole RenderPass, for which it is disabled.

I would like to disable it by default, so that you need to manually enable it, if you want to use it.

Is this a problem for anybody. Well, I guess, no. But see this as a warning, that it might be necessary to enable it in the future .

Marvin

[horati]

You made reference to this post from the performance thread.  This message is more specific so I will post here.

Another tweak, that I have enabled manually just for the Q3 test is, that I have disabled the user-defined clipping planes for the main RenderPass. Handling the Clipper or ScissorRects is expensive for the whole RenderPass with the current implementation. So, if you don't need it, disable it through:

Code:

renderPass.setClipperEnabled( false );

I do not think anyone responded because we didn't understand exactly what you meant.  Is this still relevant?  Do we need to do something?  Could you elaborate as to exactly what is missing with false?  I cannot understand how we could use a scene graph API without some form of clipping.  Presumably, you do not mean this disables all clipping.

[Marvin Fröhlich]

No. this just disables user defined clipping. You can attach scissor rects (2D) and user defined clip planes (3D) to groups. But they are ignored as long as you don't enable clipping for the render pass. Of course regular frustum culling keeps being enabled as long as you don't explicitly disable it.

Marvin

[horati]

Since I would rarely add my own clipping beyond setting the field of view through the regular API, should I expect a performance boost if I add the code you quoted?

[Marvin Fröhlich]

tbh I don't remember, if this means a big performance boost. But it should at least do a little one. Just try it out .

Marvin