Conversation
…er Ported from wgpu_sort (BSD 2-Clause License)
…orage buffers. todo: more selective impl for future mb
Owner
Author
|
note: With WGPU 28, we can also try this with mesh shaders. However, this is just an idea for now... |
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.
cargo run --release --example gaussian3dI tried it with Apple's mlsharp ply export.
30fps: MacBook M3 16GB.
gpu radix sort ported from: wgpu_sort (Copyright (c) 2024, Simon Niedermayr, Josef Stumpfegger: BSD 2-Clause License). I must admit that I spent some time researching whether there are more modern sorting approaches for 3dgs. However, I think this is still the best approach for now.
ply reader: a new dep but very very tiny: https://github.com/bourumir-wyngs/ply-rs so
note that for now, its compute + frag approach. When I have time, I want to try to convert this entirely into a compute pipeline. However, I realized that I need to work harder on this because I had some performance issues.
As I did previously in gaussian.wgsl, I tried a purely tiled approach for creating entire compute pipeline. However, given the immense size of the 3D gaussians, this approach proved to be too naive and ineffective result: 8-10 fps and lower quality. but I'll still push for it. I'll take that as a “starting point” for now.
NOTE: I was able to get my ply file in minutes using the following simple script via Google Colab:
An even crazier idea would be to export this model to ONNX, make the necessary adjustments, and serve it in real time :-P
but considering the complexity, this would be a huge work.