[ANNOUNCEMENTS] About the latest version of ash and the vk_mem problem.

[MatchaChoco010]

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.

[thargy]

Just been running up against this myself all day 😢 really frustrating and seems endemic in the Rust ecosystem. All I wanted was to get a working ash+GUI, but the 'abandonment' of vk-mem seems to have scuppered a lot of examples.

[MatchaChoco010]

I've published a crate called egui-winit-ash-integration that uses gpu-allocator as the default GPU allocator.

From now on, egui_winit_ash_vk_mem will no longer be maintained.
Please use egui-winit-ash-integration.

[Jasper-Bekkers]

@MatchaChoco010 Please let us know if you run into any issues with gpu-allocator we're actively maintaining and improving it.