Skip to content

Introduce Image2DBufferSpecification for Image ViewType abstractation #295

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

Closed
JeanPhilippeKernel opened this issue Dec 26, 2023 · 0 comments · Fixed by #377
Closed

Introduce Image2DBufferSpecification for Image ViewType abstractation #295

JeanPhilippeKernel opened this issue Dec 26, 2023 · 0 comments · Fixed by #377

Comments

@JeanPhilippeKernel
Copy link
Owner

JeanPhilippeKernel commented Dec 26, 2023

As today, we have the option to create flat texture 2D or a cubemap (composition of 6 texture 2D).
the implementation of creating a cubemap has been hard-coded based on a fixed image format: VK_FORMAT_R32G32B32A32_SFLOAT which is handling by the Image2DBuffer abstraction

To ease the creation of whether a flat 2D image buffer or cubemap buffer, we want to introduce Image2DBufferSpecification which will take care of the user config and drive the process of creation.

The specification should allow the caller to tell whether the buffer is for flat 2d image or cubemap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants