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

Move the pending scene data structure to the SceneBuilder thread #2998

Merged
merged 7 commits into from Sep 4, 2018

Commits on Aug 31, 2018

  1. Move the pending scene data structure to the scene builder thread.

    With this change the render backend only sees the state of the scene
    that it can use for frame building and the scene builder thread manages
    its own scene.
    This will allow us to perform low priority scene building and rasterization
    asynchronously without having to involve the render backend thread.
    nical committed Aug 31, 2018
  2. Remove the per-document FrameBuilderConfig.

    All documents currently always have the same config.
    nical committed Aug 31, 2018
  3. Move scene loading code behind the "replay" feature flag.

    nical committed Aug 31, 2018
  4. Fix confusion with generate frame/render/composite terminology.

    From now on, generate frame means having the frame builder generate a frame (but not necessarily render it), and render means asking the renderer to render a frame.
    nical committed Aug 31, 2018

Commits on Sep 4, 2018

  1. Rename generate_frame into build_frame.

    nical committed Sep 4, 2018
  2. Rename Transaction's render into render_frame.

    This is to avoid confusion with the previous meaning of render which was about building the frame rather than rendering it.
    nical committed Sep 4, 2018
  3. Rename Document::render into Document::build_frame.

    nical committed Sep 4, 2018
You can’t perform that action at this time.