This repository was archived by the owner on Oct 31, 2025. It is now read-only.
Closed
Conversation
Closed
Contributor
|
#423 does the same thing as this and isn't a draft, so closing this! |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
This is the the test a did 1-2 weeks ago on hot-reloading of shaders, haven't had time to continue on it but do think we should clean it up and get it in to the all the example runners
It does have a problem with spirv-builder where that somehow causes every iteration in cargo-watch to rebuild
coreand everything, it seems like. I did test before to not have the spriv-builder build path at all and just load .spv directly from the target folder and that worked flawlessly when iterating, could potentially disable the spriv-builder path when one has thehot-reloadfeature enabled as it is not needed then