forked from cocos/cocos-engine
-
Notifications
You must be signed in to change notification settings - Fork 0
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
subresource move #157
Merged
Merged
subresource move #157
Conversation
This file contains 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
test case: cocos/cocos-example-custom-pipeline#1 |
@hana-alice ❗ There was an error during the execution of the tasks. Please check the logs for more details. |
star-e
pushed a commit
that referenced
this pull request
Aug 14, 2023
* subresource move (#157) # Conflicts: # native/cocos/renderer/pipeline/custom/FrameGraphDispatcher.cpp
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.
Re: #
Changelog
A0
view on slice 0 of 3-layer texture viewB0
, whileB0
is a 3-layer texture view on 6-layer textureC0
at first 3 slices, they are expect to be appear in resource graph in the following form(except cube and depthstencil):C0
-> "C0"B0
-> "C0/B0"A0
-> "C0/B0/A0"Continuous Integration
This pull request:
Compatibility Check
This pull request: