-
Notifications
You must be signed in to change notification settings - Fork 123
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 VK_EXT_frame_boundary
fake support
#1902
base: dev
Are you sure you want to change the base?
Fix VK_EXT_frame_boundary
fake support
#1902
Conversation
CI gfxreconstruct build queued with queue ID 315625. |
CI gfxreconstruct build # 5488 running. |
be6e06e
to
cb66143
Compare
CI gfxreconstruct build queued with queue ID 315640. |
CI gfxreconstruct build # 5489 running. |
CI gfxreconstruct build # 5489 failed. |
cb66143
to
f903da4
Compare
CI gfxreconstruct build queued with queue ID 316623. |
CI gfxreconstruct build # 5508 running. |
CI gfxreconstruct build # 5508 failed. |
Fix `VK_EXT_frame_boundary` fake support at device creation at capture and replay time when `VkPhysicalDeviceFrameBoundaryFeaturesEXT` is present by removing it before the actual call to the driver (and adding it again at capture time to not have a visible difference from user's perspective) Change-Id: I52e3fbf6e413703582a38be6a098c98089edca7d
f903da4
to
33ae469
Compare
CI gfxreconstruct build queued with queue ID 316700. |
CI gfxreconstruct build # 5509 running. |
CI gfxreconstruct build # 5509 failed. |
Fix
VK_EXT_frame_boundary
fake support at device creation at capture and replay time whenVkPhysicalDeviceFrameBoundaryFeaturesEXT
is present by removing it before the actual call to the driver (and adding it again at capture time to not have a visible difference from user's perspective)