Fix incorrect MTLRenderStages constants #227
Merged
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 potentially fixes synchronization as these constants are passed to APIs like
waitForFence(_ fence: MTLFence, before stages: MTLRenderStages)
https://developer.apple.com/documentation/metal/mtlrendercommandencoder/1648378-waitforfence
Would appreciate if someone could properly double-check this. I can see from the metal frame capture that this fixed incorrect values for me, and these docs show the constants being used in other bindings. https://docs.microsoft.com/en-us/dotnet/api/metal.mtlrenderstages?view=xamarin-ios-sdk-12 I was not able to find the correct values published by apple. (Maybe their C++ bindings would have them)