[BUG]: Vulkan crash on startup

[all500234765]

Is there an existing issue for this?

• [X] I have searched the existing issues

Affected Build(s)

v0.2.0 3577-afce7a8d

Description of Issue

Crash on startup

Expected Behavior

Not crash

Reproduction Steps

Open Vita3K See the crash

Log File

[02:55:47.722] |I| [config::init_config]: backend-renderer: Vulkan [02:55:47.723] |I| [config::init_config]: log-level: 0 [02:55:47.724] |I| [config::init_config]: log-active-shaders: enabled [02:55:47.724] |I| [config::init_config]: log-uniforms: enabled [02:55:48.072] |I| [SDL_main]: Vita3K v0.2.0 3577-afce7a8d [02:55:48.072] |I| [SDL_main]: OS: Microsoft Windows 10 Professional (build 19045) [02:55:48.073] |I| [SDL_main]: CPU: 11th Gen Intel(R) Core(TM) i5-11600KF @ 3.90GHz | 12 Threads | 3.912 GHz [02:55:48.073] |I| [SDL_main]: Available ram memory: 65449 MiB [02:55:48.077] |I| [app::init]: Base path: H:\SDK_Consoles\PSVita\windows-latest\ [02:55:48.077] |I| [app::init]: User pref path: H:\SDK_Consoles\PSVita\windows-latest_DATA/ [02:55:48.489] |I| [renderer::vulkan::VKState::create]: Enabling vulkan validation layers (has a performance impact but allows better error messages) [02:55:48.732] |I| [renderer::vulkan::VKState::create]: Vulkan device: NVIDIA GeForce RTX 3070 [02:55:48.732] |I| [renderer::vulkan::VKState::create]: Driver version: 551.23.0.0 [02:55:48.732] |I| [renderer::vulkan::VKState::create]: Memory mapping is enabled [02:55:49.497] |C| [logging::init::::operator ()]: Unhandled C++ exception. vma::Allocator::createImage: ErrorFeatureNotPresent

System Configuration

CPU: 11th Gen Intel(R) Core(TM) i5-11600KF @ 3.90GHz | 12 Threads | 3.912 GHz GPU/Driver: NVIDIA GeForce RTX 3070 / 551.23.0.0 RAM: Available ram memory: 65449 MiB OS: Microsoft Windows 10 Professional (build 19045)

[all500234765]

previous build worked fine. I've just feed up with constant restarts that proceed with skipping an update everytime, so i just went with it.

[Zangetsu38]

yes, last pr merged broken vulkan

[scribam]

@all500234765 does it work now with the latest build?

[all500234765]

Sorry, this was fixed a while ago. I don't usually check for github specifically, so sorry for the wait.