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

Renderer roadmap #3001

Open
11 of 24 tasks
lilleyse opened this issue Sep 8, 2015 · 3 comments
Open
11 of 24 tasks

Renderer roadmap #3001

lilleyse opened this issue Sep 8, 2015 · 3 comments

Comments

@lilleyse
Copy link
Contributor

lilleyse commented Sep 8, 2015

For background, see the original roadmap for the Data Driven Renderer.

@pjcozzi
Copy link
Contributor

pjcozzi commented Sep 9, 2015

Refactor command execution. For example use computeEngine.execute(command) directly.

Looks OK for us to have context.executeDrawCommand, context.executeClearCommand, and ComputeEngine.execute.

@pjcozzi
Copy link
Contributor

pjcozzi commented Sep 9, 2015

  1. Separate command lists to avoid sorting based on pass type later.
  2. Pass just frameState to update functions. Place context and commandList inside frameState.

I think we need to do (2) before doing (1), right? Perhaps just hold on these for now.

@lilleyse lilleyse mentioned this issue Sep 11, 2015
3 tasks
This was referenced Sep 28, 2015
This was referenced Oct 26, 2015
@pjcozzi pjcozzi mentioned this issue Jan 6, 2016
4 tasks
@bagnell
Copy link
Contributor

bagnell commented Mar 16, 2017

Derived command shaders are cached in the ShaderCache so they will be properly released when the original shader is. The same method of caching can be used for the derived render states.

This was referenced Apr 18, 2017
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

3 participants