Why VulkanCore is in pre-release state?

[haruby511]

I just wonder that why VulkanCore is not stable release?

I moved from VulkanSharp and I think, VulkanCore is better than that.
API design and native memory handling seems more stable.
And I cannot see any critical issue, milestone or commit in over than 6 months.

[discosultan]

Hi @haruby511, great question!

The initial vision was to keep it in pre-release state until VulkanCore has been successfully used in some bigger project. Mainly to indicate that there may still be bugs present and to allow breaking API from version to version. Unfortunately, I never really got to employ it myself but others might have done so.

Also, I don't think the approach I chose to manually create the bindings was the right decision. While it was convenient in the beginning due to a lot of quirks in the Vulkan spec, it turned out to be too cumbersome to keep up-to-date with the spec. Especially between bigger versions such as 1.0.x to 1.1.x. This means VulkanCore currently targets the latest 1.0.x version of the spec which is by now quite old.

I'm still open to merging PRs and fixing critical bugs but have since left to develop on other projects.

[haruby511]

Thanks for honest answer.

I also felt that the Vulkan API is hard to porting to C# because of many dynamic arrays.