chore: Updated Vortice.Vulkan package to the latest version 2.1.2 -> 3.0.3

[Feralnex]

PR Details

Updated Vortice.Vulkan package to the latest version (2.1.2 -> 3.0.3)

Related Issue

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[xen2]

Quick question, will there be any changes in the C# code (due to binding changes)?
If yes, let me know, and depending how big the changes are, it might be better to do the changes in https://github.com/xen2/stride/tree/vulkan_wip

[Feralnex]

Quick question, will there be any changes in the C# code (due to binding changes)? If yes, let me know, and depending how big the changes are, it might be better to do the changes in https://github.com/xen2/stride/tree/vulkan_wip

Yes, there will be some changes to the code, but as far as I noticed it's all about extracting InstanceApi and DeviceApi instead of invoking functions directly from the library. Also there were some changes to the way the core functions work (instead of single call we always get VkResult as a return type and extracting the specific result is done by another call). Let me know if I should branch off from Your fork then.

[amerkoleci]

Hey,
As always, ping me if you need any information or doubts :)

Thanks

[Kryptos-FR]

I think the branch should be rebased on top of master while keeping only the commit(s) that updates the package version, and any related modified code.

Currently there seems to be a lot of unrelated changes because of some incorrect merging, possibly cause by the merge issue we had a few days ago, where the master branch was on the wrong "side" of the merge for PR #1715.

Alternatively, reset the branch to before the last merge, fetch the latest master and redo the merge.

Edit: seems fixed now.

[Eideren]

Thanks !