feature: Adding a WebGPU Rendering System to Vis Core [DT-9593]#265
Draft
Jarbuckle wants to merge 4 commits into
Draft
feature: Adding a WebGPU Rendering System to Vis Core [DT-9593]#265Jarbuckle wants to merge 4 commits into
Jarbuckle wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feature: Adding a WebGPU Rendering System to Vis Core DT-9593
What
This is an⚠️ EXPERIMENTAL ⚠️ branch focused on adding a rendering system into Vis Core, specifically one implemented with WebGPU.
How
Reviewed WebGPU's rendering pipelines and related features, then experimented with different ways of providing a simplification to this interface that works well for the use cases Vis is intended for.
Some initial experiments include a twin-graph approach, where resource bindings to shaders are defined in one graph, then mapped to pipeline activations in a state-execution graph. This aims to disconnect the resource-management side of rendering ("what to render") from the rest of the state ("how to render"), and also aims to make resource management itself somewhat more intuitive and efficient than might be achieved using WebGPU directly.
PR Checklist
main?