Skip to content

feat: presenter#7

Open
alexcu2718 wants to merge 10 commits intoalex_stufffrom
feat/presenter
Open

feat: presenter#7
alexcu2718 wants to merge 10 commits intoalex_stufffrom
feat/presenter

Conversation

@alexcu2718
Copy link
Copy Markdown
Collaborator

Keeping the cmake changes in this as makes it easier to do testing,

Added vk12/vk13 switch, I am pretty sure I could've made it a template class with specialisations for each.
So feel free to rebuke me on that. I don't think it matters(?).

Also added the presenter abstraction.

@gituser12981u2
Copy link
Copy Markdown
Owner

Can you rebase feat/presenter with the newest version of alex_stuff? That should get rid of most of the merge conflicts.

@alexcu2718
Copy link
Copy Markdown
Collaborator Author

Can you rebase feat/presenter with the newest version of alex_stuff? That should get rid of most of the merge conflicts.

Yeah i will tonight. Probably. Maybe

@gituser12981u2 gituser12981u2 changed the title Feat/presenter feat: presenter Mar 22, 2026
Copy link
Copy Markdown
Owner

@gituser12981u2 gituser12981u2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FIX PLZ

image_count > swapchain_support.capabilities.maxImageCount) {
image_count = swapchain_support.capabilities.maxImageCount;
}
render_path_ = can_use_dynamic_rendering
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Knowing whether the physical device is vk13 or vk12 is helpful beyond just the render pass path. We should abstract this so it can be reused.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will do this. I will probably make a small shared struct that is filled in with device info that can be used.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still do this I swear

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

U SURE?

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kinda

@gituser12981u2
Copy link
Copy Markdown
Owner

About the Apple issue with VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VULKAN_1_2_FEATURES and VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VULKAN_1_3_FEATURES I talked to you about, you know the thing that was giving me a segfault, well I made a fix in the last commit and, for fun, I checked the non Apple path on my MacBook and it somehow worked.

So I guess everything the chain does work and it was some other little problem with the implementation before. I don't know any more. I will just blame MoltenVK. I am making a new commit without the Apple path.

std::move(list)), // This may not require a move
std::memory_order_release);
// lint from clang tidy does not work on msvc(it works on GCC, at least!), we
// should look into this more! TODO
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I look

QUARK_NO_COPY(Swapchain);
Swapchain(const Swapchain &) = delete;
Swapchain &operator=(const Swapchain &) = delete;
Swapchain(Swapchain &&other) noexcept;
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fie upon thee for not using macros

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants