Basic ShaderToy shader support#271
Merged
Merged
Conversation
smj-edison
approved these changes
Jun 9, 2026
Closed
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.
IMG_5703.MOV
Basic example (same as https://www.shadertoy.com/new):
ShaderToy code should run verbatim as long as it only uses iResolution and iTime (no channels, iFrame, iMouse, or iFrameRate support yet).
Tested and working:
This is not very flexible right now -- you can't add additional uniforms -- but I like the idea of maintaining verbatim compatibility so we can use the existing library of ShaderToy. Can try to make it extensible later while maintaining compatibility (maybe use reflection to find declared uniforms)
Fixes #106 / May supersede #270