GeraldKimmersdorfer / meshlet_playground

1 stars 1 forks source link

Compile Issue #5

Closed matthiasfostel closed 11 months ago

matthiasfostel commented 1 year ago

Hello!

Sorry to bother, but I am trying to compile to checkout your work and receiving the following error:

2>C:\dev\compressed_meshlet_skinning\source\pipelines\MeshPipeline.cpp(77,77): error C2664: 'std::vector<avk::descriptor_set,std::allocator<avk::descriptor_set>> avk::descriptor_cache_t::get_or_create_descriptor_sets(std::initializer_list<_Ty>)': cannot convert argument 1 from 'std::vector<avk::binding_data,std::allocator<avk::binding_data>>' to 'std::initializer_list<_Ty>'

2>C:\dev\compressed_meshlet_skinning\source\pipelines\VertexIndirectPipeline.cpp(115,77): error C2664: 'std::vector<avk::descriptor_set,std::allocator<avk::descriptor_set>> avk::descriptor_cache_t::get_or_create_descriptor_sets(std::initializer_list<_Ty>)': cannot convert argument 1 from 'std::vector<avk::binding_data,std::allocator<avk::binding_data>>' to 'std::initializer_list<_Ty>'

I installed the Vulkan SDK from LunarG with Vulkan Memory Allocator option checked, so the Auto-VK-Toolkit builds fine but I am not sure what you mean in your Setup Notes by "Make sure that auto_vk_toolkit is set on development branch". I assumed this ment go into the Auto-VK-Toolkit folder and git checkout development, but that did not fix the errors above.

I also double checked the Properties -> Configuration Properties -> Debugging -> Working Directory is set to "$(OutputPath)", but again that did not fix the error.

Thank you for sharing your work and I wish you well in your studies!

GeraldKimmersdorfer commented 1 year ago

Hi, sry for the late response. I work locally with a different fork of avk where i added the function that you might miss. Since avk is a submodule of auto-vk-toolkit I didnt find a good way of including this in the repo yet.

You can try to pull avk from here and overwrite it locally: https://github.com/GeraldKimmersdorfer/Auto-Vk

Also, be aware that this whole project is currently under development and in a very chaotic state. Right now I'm writing my bachelor-thesis with it and I already have an idea for a paper where I'll use it too. If there are specific questions feel free to contact me.

matthiasfostel commented 1 year ago

Thank you! I appreciate the quick reply.

That seems to have done the trick. I went into the auto_vk_toolkit folder, renamed the original auto_vk folder then git cloned your new repository in there and renamed it to auto_vk. Looks like it found what it needed.

I appreciate the help and the warning. I am only a hobbyist and was curious of how the methods you are exploring will help rigged mesh animation calculations since I know it can be a big hindrance in 3D graphics. I was going to add collada import and try to make a benchmark as my own learning experience.

You do whatever you need to do and do not worry about me. Wish you well in your studies!

GeraldKimmersdorfer commented 11 months ago

I now linked the repo to custom forks of avk-toolkit and avk. Building the project should now not be an issue anymore.