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

Rendering System #9

Open
alaingalvan opened this issue Jun 5, 2017 · 0 comments
Open

Rendering System #9

alaingalvan opened this issue Jun 5, 2017 · 0 comments
Assignees

Comments

@alaingalvan
Copy link
Collaborator

alaingalvan commented Jun 5, 2017

CodeVR's Vulkan Renderer

The following is the start of some discussion on the Rendering System Pull Request #5.

CodeVR's renderer is modeled after a centralized graphics state store, which is laid out similarly to the GLTF specification.

The renderer is an API specific class that follows the AbstractRenderer trait, that takes a GraphicsState object, and creates API specific data structures from that state from its own handles, and renders the state using the graphics API of choice.

Multiple Actors, 1 Graphics State

There's a large number of actors in a scene, each writing to the engine's state. Each could queue a request to the scene graph to add or remove an actor, each could add a construct to the graphics state, or a physics construct to the physics world, etc.

@alaingalvan alaingalvan self-assigned this Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant