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

docs: linked the rules to follow while writing GLSL code #33

Merged
merged 5 commits into from Jun 2, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/shader-specifications/1-shaders.md
Expand Up @@ -14,6 +14,7 @@ parameters the shader need, in which order the data of those parameters should b
to do anything related to assets. This makes it easier for users of the shader as they now have a strongly typed API that has parameters with
which they are more familiar and it can be used immediately without any other configuration.

❗ Note: As mentioned above there are certain constraints from the [SPIR-V library](https://github.com/flutter/engine/blob/master/lib/spirv/README.md) that you have to adhere to while writing your GLSL code. Some of these rules are handled by Umbra while generating the raw GLSL code but it is still recommended to read up on the rules because Umbra is not able to cover them all.

## Umbra Shader Abstraction

Expand Down