Skip to content

[Frame Looping] Handle vkBindBufferMemory and vkBindImageMemory - #3273

Merged
nickdriscoll-lunarg merged 2 commits into
LunarG:devfrom
nickdriscoll-lunarg:frame_loop_memory_binding
Sep 21, 2026
Merged

nickdriscoll-lunarg merged 2 commits into
LunarG:devfrom
nickdriscoll-lunarg:frame_loop_memory_binding

Conversation

@nickdriscoll-lunarg

Copy link
Copy Markdown
Contributor

This PR adds generated code for handling the original memory biding entry points.

A future PR will handle the modern entry points that can bind multiple objects to memory at once.

@nickdriscoll-lunarg nickdriscoll-lunarg added the approved-to-run-ci Can run CI check on internal LunarG machines label Sep 16, 2026
Comment thread framework/generated/generated_vulkan_replay_frame_loop_consumer_base.cpp Outdated
@nickdriscoll-lunarg
nickdriscoll-lunarg force-pushed the frame_loop_memory_binding branch 2 times, most recently from c7f7158 to 8efc1f3 Compare September 17, 2026 14:27
Comment thread framework/decode/vulkan_replay_frame_loop_consumer.cpp
@nickdriscoll-lunarg
nickdriscoll-lunarg added this pull request to the merge queue Sep 21, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 21, 2026
@nickdriscoll-lunarg
nickdriscoll-lunarg added this pull request to the merge queue Sep 21, 2026
Merged via the queue into LunarG:dev with commit 3ec6080 Sep 21, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved-to-run-ci Can run CI check on internal LunarG machines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants