-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Fix vulkan fence synchronization #17969
Merged
akioCL
merged 4 commits into
o3de:development
from
msat-huawei:fix_vulkan_fence_synchronization
May 28, 2024
Merged
Fix vulkan fence synchronization #17969
akioCL
merged 4 commits into
o3de:development
from
msat-huawei:fix_vulkan_fence_synchronization
May 28, 2024
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
Signed-off-by: Martin Sattlecker <martin.sattlecker@huawei.com>
Signed-off-by: Martin Sattlecker <martin.sattlecker@huawei.com>
Signed-off-by: Martin Sattlecker <martin.sattlecker@huawei.com>
I'm testing this PR now on a Quest Pro. |
I got this compilation error:
|
Tested with OpenXRTest and it's working. Thanks a lot for taking care of this issue. |
galibzon
approved these changes
May 22, 2024
akioCL
approved these changes
May 22, 2024
jjs-home
pushed a commit
to jjs-home/o3de
that referenced
this pull request
May 29, 2024
* Add fence synchronization back to async upload queue fences * Fix user awaited fence synchronization * Move AttachmentReadback wait to Execute Signed-off-by: Martin Sattlecker <martin.sattlecker@huawei.com> Signed-off-by: Martin Winter <martin.winter@huawei.com> Co-authored-by: Martin Winter <martin.winter@huawei.com>
@msat-huawei Can we cherry pick this PR into stabilization branch. Thanks. |
msat-huawei
added a commit
to msat-huawei/o3de
that referenced
this pull request
Jun 3, 2024
* Add fence synchronization back to async upload queue fences * Fix user awaited fence synchronization * Move AttachmentReadback wait to Execute Signed-off-by: Martin Sattlecker <martin.sattlecker@huawei.com> Signed-off-by: Martin Winter <martin.winter@huawei.com> Co-authored-by: Martin Winter <martin.winter@huawei.com>
jhmueller-huawei
pushed a commit
that referenced
this pull request
Jun 4, 2024
* Add fence synchronization back to async upload queue fences * Fix user awaited fence synchronization * Move AttachmentReadback wait to Execute Signed-off-by: Martin Sattlecker <martin.sattlecker@huawei.com> Signed-off-by: Martin Winter <martin.winter@huawei.com> Co-authored-by: Martin Winter <martin.winter@huawei.com>
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.
What does this PR do?
This fixes issues related to synchronization of VkFence and binary semaphores introduced by #17761 , when a device without timeline semaphore support is used:
This PR should fix #17890. I cannot test this directly as I don't have access to a Quest. We however managed to fix multiple Vulkan validation warnings related to VkFence and multi threading.
How was this PR tested?
Tested with various atom sample viewer samples, and some custom levels.
I couldn't get the OpenXRTest project to run, as mentioned in #17890. There are many passes/shaders that won't compile in the AssetProcessor. We managed to create Vulkan validation errors in some of the atom sample viewer samples however.