Tracking issue for Silk.NET Vulkan Memory Allocator

[Perksey]

Development

• [x] [Complete] Add legacy VMASharp sources to the repo while we work - #599 - @sunkin351
• [ ] [Started] Review the VMASharp API/propose changes as needed - #595 - @HurricanKai
  • [ ] Markdown document in #595 is updated with action items and comments
• [ ] [Not Started] Create the Silk.NET.Vulkan.MemoryAllocator project and start implementing the new public API - unclaimed
• [ ] [Not Started] Delete the original code once the new API is implemented - unclaimed
• [ ] [Not Started] OPTIONAL/BONUS: Profile the new implementation before release - unclaimed

Milestones

• [ ] Release with Silk.NET Vulkan Memory Allocator

[Perksey]

@Beyley did you want to take on any of the VMASharp merger tasks? This work package has been forgotten about mostly since Kai's time was chipped away at.

[Beyley]

@Beyley did you want to take on any of the VMASharp merger tasks? This work package has been forgotten about mostly since Kai's time was chipped away at.

I'll bring the branches back up to date and we can move forward from there

[jcyuan]

hi, so now which is the recommended way to use VMA? because from official it seems stopped, and from https://github.com/sunkin351/VMASharp, the last commit was 3years ago...

[Perksey]

We are still accepting community contributions towards the efforts of bringing VMASharp into the main library. For now VMASharp remains the most up to date, though it may require some updating to work on new builds, not sure. TIAS.

[jcyuan]

We are still accepting community contributions towards the efforts of bringing VMASharp into the main library. For now VMASharp remains the most up to date, though it may require some updating to work on new builds, not sure. TIAS.

got it, thanks~