Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve culling data reuse #946

Open
paroj opened this issue Nov 14, 2018 · 0 comments
Open

Improve culling data reuse #946

paroj opened this issue Nov 14, 2018 · 0 comments

Comments

@paroj
Copy link
Member

paroj commented Nov 14, 2018

similar to what is suggested in the 2.0 slides p. 45 and following.

The given example is:

    target_output
    {
        pass render_scene
        {
            first_render_queue 10
            last_render_queue 90
        }

        pass render_quad { }

        pass render_scene
        {
            first_render_queue 91
            last_render_queue 95
        }
    }

however, this was never an issue. The RenderTarget is only updated once and both render_scene passes affect the per-target render-queue mask. The render_quad pass is sorted-in accordingly.

On the other hand:

        target scene
        {
            pass clear { }
            pass render_scene
            {
                first_render_queue 0
                last_render_queue 10
            }
        }

        target scene
        {
            pass render_scene
            {
                first_render_queue 10
                last_render_queue 20
            }
        }

will update the RenderTarget twice and hence do the culling again.

If neither viewport nor camera changed between target calls, we can skip _findVisibleObjects.

Possible gains:
ogre1-12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant