gaspard-- / magma Goto Github PK

Should be fairly basic. Requires some other things though.

This is necessary for #7 and could potentially be used to make CommandBufferGroupes better.

Bite me. I'm already overwhelmed...

It seems a rather common pattern in the code. Removing the code duplication would be a good step forward.

A warning would be more appropriate.

see #39
This should probably be some wrapper class around RangeId.

Looking seems like command buffers should be in groups, this means balancing RAII granularity and Memory (which implies performance too).

Code is commented as needing to be refactored.

Needed to render a triangle.

Turns out it's not useful at all, this implies a lot of simplification. This issue should come after #16

Easy to mess up, no immediate compilation warning combined with the rare need of several flags make this error quite common in the codebase.

Could be useful to reduce memory footprint.
Started on branch raven-os/magma/singleton_based_deleter

This issue mostly concerns CreateInfo.hpp.

Would be cool. Kind of hard to test in our situation.

Not to priority, but could be really useful to help debug projects.

Vulkan has explicit allocation, which allows more precise control, however this means that data with variable size is harder to handle.

Putting this on priority high because needed in other projects.

They were broken by Gaspard--/claws#36

This may cause overflows for things such as large staging buffers for textures.
This should be pretty easy to fix.

Would be cool. Making an issue to remember, but right now we aren't at that point yet.

This shall take advantage of vk::Device::destroy

Seems to be a good way to win performance from what I'm reading.

Sub-issue of #7

• This means Subpasses, Dependencies and attachements
• Maybe recycle some format selection code? ("VulkanFormats.hpp")
• Add relevent functions to magma::RenderPassCreateInfo

This seems like something that could be useful, especially for raven-os/feathers.

This would make the API more explicit and understandable.
The drawback being structured bindings are gone. After reading into it a little, structured bindings can still be implemented.

sub-issue of #7