m1 deferred rendering issue: fbf & write to same tex not fully support #4174
Conversation
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
4 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.
对于fbf： 没事了里边input参数声明[color[n]]就可以了；
对于read&write同一个texture: 需要spirv编译的时候加入一些配置触发声明为texture<read_write>,也是可行的；
对于fbf+同时读写，ios跑起来并没有问题，m1下出现了闪烁，看效果像是是某些tile读写并没有完全按照shader顺序先读后写，现阶段所有资源都没有采用MTLHeap所以不需要加资源fence。
