matchachoco010 / egui_winit_ash_vk_mem Goto Github PK

Reference gwihlidal/vk-mem-rs#54

When I was working on upgrading egui, I tried to remove Cargo.lock and rebuild it cleanly.
However, I found out that the latest version of vk-mem-rs does not support the latest version of ash.
This broke the existing build of lib.rs and examples.

The options I can take are :

1. set an upper limit on supported ash versions.
2. wait for vk-mem-rs to update to support the latest ash.

I think I'll take the second option.
But unfortunately, vk-mem-rs is not updated frequently these days.
Instead of vk-mem-rs, some projects seem to adopt gpu-allocator, which is an actively maintained allocator built entirely in Rust language.

I will be investigating the gpu-allocator soon.
If I migrate my personal project from vk-mem-rs to gpu-allocator, I will stop updating this egui_winit_ash_vk_mem after setting the upper limit for the corresponding ash version.
If anyone wants to continue to use vk_mem, please folk this repository and continue to maintain it.

I may create a crate called egui-winit-ash-gpu-allocator soon.
However, I don't have time to do that right away.
I would be happy if someone could make that crate for everyone.

Hi,
I'm trying to use this in my project, but the Khronos Validation layer keeps spitting out this error:

[Debug][error][validation] "Validation Error: [ UNASSIGNED-CoreValidation-DrawState-InvalidRenderpass ] Object 0: handle = 0x5555571d3858, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa1662b9 | You cannot start a render pass using attachment 0 where the render pass initial layout is VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL and the previous known layout of the attachment is VK_IMAGE_LAYOUT_PRESENT_SRC_KHR. The layouts must match, or the render pass initial layout for the attachment must be VK_IMAGE_LAYOUT_UNDEFINED"

It still renders, but clearly something is wrong with the renderpass here. Is this user error on my part or a general problem with the crate?