Device Setup & Pipeline cont. - Vulkan Game Engine Tutorial 03 

It is pretty nice, i'm more of a fan of mostly single files myself tho :)

​@@abarry6002 programmers must enjoy collaborating with you ;)

@@Crimspn lmao

@@abarry6002 Programmers after finding your file: "Cast into the fire! Destroy it!" You: "No."

@@Crimspn and all the dudes in the thread: It doesn't make sense to create an architecture with an API you have no idea how it works in the first place. in this scenario learning in a single file is optimal. Later, after you understand what's going on, is when splitting into different files becomes a necessity, and guess what? you will be in a better position to create an architecture that really fits your needs ;)

+1 on this request :D

+1 on this request

vscode is an ide but a slim down version of your typical IDE.

@@EmperorKagato Not really. Its a beefed up text editor.

Nice!! That will definitely be useful information going forward and will provide some context for what we’re doing.

Thanks for catching this!

@@BrendanGalea No problem :). THank YOU for this amazing content!

thanks! I thought I was going crazy and redid everything a few times.

Ya I still need to get around to creating the device appendix video, but every time i start on it it just feels like im reiterating vulkan-tutorial.com :/ I highly recommend giving the device creation secion a 15 minute read, which gives a step by step appraoch as to how that code was constructure.

Ya my main focus is getting out more tutorials. Once I cover the basics, which should be around tutorial 25, then I think I'll do the appendix just to have a complete series.

+1

thanks for the feedback! I'd highly recommend checking out vulkan-tutorial.com for step by step instructions. I'm trying to structure this as how to build out an engine so its hard for the series not to jump around a bit. It's a bit of a balancing act between a bunch of different constraints for me when trying to design these tutorials, and I don't always get it right. So defintely don't use me as your only source. But I'll keep trying to do my best to make the series as easy to follow as possible

Thank you!!

Yes will do!

Thank you, That is a good point. I should make rust files available as well.

@@BrendanGalea I'm going through your code now trying to convert it using the Vulkano crate rather than an unsafe wrapper like Erupt.

@@BrendanGalea BTW, I am really excited about this series. Not just from a Vulkan point of view, but graphics programming in general.

Let me know if you run into issues and I’ll do my best to help. (Ive never used rust though so the capacity I can help in is limited)

Thanks! Unfortunately can’t correct them as they’re coming from the vulkan c headers. Alternative would be to use the cpp headers or find a way to silence them. But I’ll take a look into the uninitialized member variables, that’s probably my mistake somewhere.

Ya that’s a really good point. What language are you using. I’ll ask on our discord if anyone has done it in a different language and if they are alright letting me share links to it.

Thanks for mentioning! I wasn't aware of this issue.

@theRPGmaster Dude tysm, you're thee year old comment saved me a BUNCH of time probably :D.

Hmm that’s pretty strange. I’ve tested the code on most compilers now. What compiler were you using? And do you have the error message?

I'm sorry, it was a typo on my code. I found it today, just a missing pointer operator. Thanks

No worries! Hope you’ve been finding the tutorials helpful ☺️

I'm not sure what you're referring to, could you please elaborate?

Great question! You are absolutely right in that this is an unnecessary restriction, but for now it really simplifies a lot. Currently I'm taking the approach of 1:1:1 for our window, device and swapchain. But it should be possible to have 1 device, with multiple window/swapchain pairs. I'm not 100% about this, but I believe there could be situations though that you can't share your device (or have to re-create it). For example, if you have a full screen window on a 10 bit HDR monitor, and then a window on another second monitor. It might be possible that the required extensions are incompatible? So until I've looked into this more I figured it would be best to keep things as straightforward as possible. Multiple windows is a really good idea for a future tutorial.

@@BrendanGalea Yeah right, a number of good points! That's very useful info to keep in mind when I do eventually break the 1:1:1 in my own engine

this can be a bit tricky. My first recommendation is try re-installing vulkan, make sure you're downloading the vulkanSDK and not just the vulkan runtime. Next if that doesn't fix the issue, in the vulkanSDK/Applications directory there should be an application called vulkaninfo. Try running that and in the output nearish the top you should see something like Layers: count = 8 ================= Where validation layer count should be some number greater than 0. Then another thing you could try is in the same directory try opening vkconfig, have selected the validation layers option, and then run your program and see if the validation layers can be found in that case.

It's not causing any issues (currently) but you are absolutely right in that this does shadow the variable and isn't clean code. I should've used differentiated names. Thanks for bringing this to my attention!

@@BrendanGalea also noticed same shadowing warnings for "swapChainExtent" when I added the swap chain class is video 5.

that's good to know, thanks for sharing this!

He's using VS Code, not XCode. Hope it helps.

The device code is pretty dumb, and just picks the first device that is suitable for the requested features. In your case the ordering happens to present the intel first. i still haven't gotten around to the device code walk through yet unfortunately, I'm still propritzing adding new tutorials currently. But the device code very closely follows the setup section vulkan-tutorial.com/Drawing_a_triangle/Setup/Base_code so thats a good place to start

Sounds like you’re trying to pass an int to something that takes and int pointer. You might be missing an &. What’s the line of code?

Are you running any processes in the background. Things like screen capture and over clocking software hook in pretty low level into the system and validation layers can pick these messages up from other programs. Perhaps the epic launcher uses some vulkan processes in some way and you’re getting cross talk. If it is just cross talk, it won’t affect how your vulkan program runs, just may clog up your logs a bit

ive had this same problem, seems like our gpus dont support anisotropic filtering. luckily this can be turned off. you can remove the check for supportedFeatures.samplerAnisotrpy and change deviceFeatures.samplerAnisotropy = VK_TRUE; to VK_FALSE in line 153 of your_enging_device.cpp im not 100% sure this works yet, ill reply to this comment after further testing

yikes, thanks for catching this! I go on to make this mistake in multiple spots. I'll mention this in the next tutorial I make.

Maybe try translating with chatgpt? But I think others have done this in python. You could check the discord and ask there (link is on the later video descriptions) Sorry I can’t be more help. Dumb of me to not think of this scenario when I was making these originally. I regret not covering this content

Ahh 🤦‍♂️ I’ll add that to my list of known issues. Mistakes like this become a lot harder to fix in an ongoing video tutorial series. Thanks for letting me know, I appreciate it!

I’m not sure what you mean by the glfw header files? The struct declared at 6:20 is to specify configuration info. It’s purpose is to make it so that we can eventually create multiple pipeline objects but with slightly different behaviour as specified by the configuration info. For example one pipeline could be used to draw solid objects, when a second pipeline would be used to draw just the wireframes of an object.

Another way to think of this struct is as a replacement for the arguments to the LvePipeline constructor. Since there are so many configuration options it would be a bit impractical to create a constructor for the class with every argument. So this just cleans up the code a bit.

@@BrendanGalea I see, thx for the explanation.

Just the default clear color. In the subsequent tutorials we set the background color each frame so you will be able to set it to black or whatever you wish then!

Try this: 1. On device.cpp VkInstanceCreateInfo struct, after getRequiredExtensions() function call add following: extensions.emplace_back(VK_KHR_PORTABILITY_ENUMERATION_EXTENSION_NAME); extensions.emplace_back("VK_KHR_get_physical_device_properties2"); createInfo.flags |= VK_INSTANCE_CREATE_ENUMERATE_PORTABILITY_BIT_KHR; 2. On device.hpp modify deviceExtensions vector as following: const std::vector deviceExtensions = {VK_KHR_SWAPCHAIN_EXTENSION_NAME, "VK_KHR_portability_subset"};

If just like me you are using a Mac with M1 chip, you can define a precompilation variable for this condition that we will use later : In lve_device.hpp #if __APPLE__ #include #if TARGET_OS_MAC #if TARGET_CPU_ARM64 #define __ADD_MOLTEN_VK_CAPABILITY_MAC_ARM64__ #endif #endif #endif And later in the same file change the device extensions vector to const std::vector deviceExtensions = { VK_KHR_SWAPCHAIN_EXTENSION_NAME #ifdef __ADD_MOLTEN_VK_CAPABILITY_MAC_ARM64__ , "VK_KHR_portability_subset" #endif }; In the lve_device.cpp before creating the vk instance (vkCreateInstance), we can change the lines auto extensions = getRequiredExtensions(); createInfo.enabledExtensionCount = static_cast(extensions.size()); createInfo.ppEnabledExtensionNames = extensions.data(); to auto extensions = getRequiredExtensions(); #ifdef __ADD_MOLTEN_VK_CAPABILITY_MAC_ARM64__ extensions.emplace_back(VK_KHR_PORTABILITY_ENUMERATION_EXTENSION_NAME); extensions.emplace_back(VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2_EXTENSION_NAME); createInfo.flags |= VK_INSTANCE_CREATE_ENUMERATE_PORTABILITY_BIT_KHR; #endif createInfo.enabledExtensionCount = static_cast(extensions.size()); createInfo.ppEnabledExtensionNames = extensions.data(); I'm not sure if this is the right condition so that it will only affect m1 macs, but it works for me and I do not have the hardware to test on multiple setup, let me know if it works!

I am sorry but I am using intel

@@homemadetech3776 Ok, it is probably just an issue with macs, you could remove the if TARGET_CPU_ARM64 and change the defined variable name to something more significative. Should probably work.

I'm not sure which parameters you're referring to?

The parameters of createGraphicsPipeline(...). I'm talking about the code style formatting of a bunch of parameters (= new line for each argument)

Oh it’s still just the order of the arguments. It’s just multiline for formatting to make it more readable

@@BrendanGalea Yes I like that. Is there a keybinding or something for this or was it a jump cut in your video? Because you didnt do this manually in the video.

ya that was just my editor. It applies auto-formatting when I save.

No unfortunately not. I’d still recommend reading the chapters on vulkan tutorial at some point as you go. You can do the tutorial series up to where I’ve left off without needing to touch anything there. But if you want to continue on after that yourself it’s definitely worth reading

When I run the exe file I have abort() error but when I run it on vs it works fine

Yup that’s expected at this point!

@@BrendanGalea my bad!

hmm thats strange, is the program crashing?

Not quite, vulkan is an API to communicate with a computer's graphics card. So an engine like unity or unreal could use the vulkan API for things such as rendering. But an engine also handles a lot of other systems beyond just rendering such as audio, physics, ai, animation, input, networking, etc. In this tutorial series we're using vulkan and creating our own basic engine. The initial focus of the series is mostly on rendering.

Something like this: tory vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_8bit_storage (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_bind_memory2 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_buffer_device_address (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_copy_commands2 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_create_renderpass2 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_dedicated_allocation (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.3 validation layer: Device Extension: VK_KHR_deferred_host_operations (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.3 validation layer: Device Extension: VK_KHR_depth_stencil_resolve (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_descriptor_update_template (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_device_group (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.4 validation layer: Device Extension: VK_KHR_draw_indirect_count (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_driver_properties (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_external_fence (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_external_fence_win32 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_external_memory (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_external_memory_win32 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_external_semaphore (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_external_semaphore_win32 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_get_memory_requirements2 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_image_format_list (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_imageless_framebuffer (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_maintenance1 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.2 validation layer: Device Extension: VK_KHR_maintenance2 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_maintenance3 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_multiview (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_pipeline_executable_properties (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_pipeline_library (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_push_descriptor (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.2 validation layer: Device Extension: VK_KHR_relaxed_block_layout (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_sampler_mirror_clamp_to_edge (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.3 validation layer: Device Extension: VK_KHR_sampler_ycbcr_conversion (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.14 validation layer: Device Extension: VK_KHR_separate_depth_stencil_layouts (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_shader_atomic_int64 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_shader_clock (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_shader_draw_parameters (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_shader_float16_int8 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_shader_float_controls (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.4 validation layer: Device Extension: VK_KHR_shader_non_semantic_info (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_shader_subgroup_extended_types (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_shader_terminate_invocation (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_spirv_1_4 (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_storage_buffer_storage_class (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_swapchain (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.70 validation layer: Device Extension: VK_KHR_swapchain_mutable_format (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_timeline_semaphore (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.2 validation layer: Device Extension: VK_KHR_uniform_buffer_standard_layout (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_variable_pointers (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_KHR_vulkan_memory_model (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.3 validation layer: Device Extension: VK_KHR_win32_keyed_mutex (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_EXT_4444_formats (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_EXT_blend_operation_advanced (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.2 validation layer: Device Extension: VK_EXT_buffer_device_address (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.2 validation layer: Device Extension: VK_EXT_calibrated_timestamps (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_EXT_conditional_rendering (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.2 validation layer: Device Extension: VK_EXT_conservative_rasterization (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.1 validation layer: Device Extension: VK_EXT_custom_border_color (C:\Windows\System32\DriverStore\FileRepository vmii.inf_amd64_ea7416dfc07162e7\. voglv64.dll) version 0.0.12

haha I didn't know yt comments could be that long! You're using windows right? In the LveDevice.cpp file at around line ~219 you can remove VK_DEBUG_UTILS_MESSAGE_SEVERITY_VERBOSE_BIT_EXT The verbose level messages don't mean you're doing anything wrong and can clutter up the console.

@@BrendanGalea Ya that would make things easier i realized that when i read it. Thank you. Also Didn't know youtube messages could be that long either lmao

@@multikillgames Keep in mind this is only printed when building in Debug mode. The device class checks NDEBUG and enables some more stuff to be printed.

Correct!

i might have been relying on it being declared in some other file that was being included, glad you found the solution. That is a good way to do it and typically it's good practice to include anything you are using directly, rather than relying on it being included indirectly as I may have done.

@@BrendanGalea I also needed to add #include "vulkan/vulkan.h" to both device files for it to work

This applies to newly added files. The code from the previous tutorials works fine.

The IDE claims that these types are not defined

I fix it, with including: #include #include but i don't understand why i should include it manualy.

I find another error in my project linked with includes. And apparently it's the structure of the include folder in the vulkan SDK, because after I manually added vulkan.h I no longer need the previous fixes.

This is the final part of my diary. I was so stupid. I must define #define GLFW_INCLUDE_VULKAN, but define this: #define GLFW_VULKAN_INCLUDE

No need to reply it was simply a typo in my " #define GLFW_INCLUDE_VULKAN #include " I had #define GLFE_INCLUDE_VULKAN simple typo, thanks for the videos they've been great so far! :D

I'm not really sure but there are a couple things we could try. It is possible that vulkan was installed correctly but for some reason the validation layers extension was not. Maybe try re-installing vulkan and see if that works. Make sure to install the SDK rather than just the runtime. It could also be a driver issue, you could try updating you graphics card drivers if you haven't recently and that could fix the issue. If those don't work let me know and we can keep looking for a solution, because debugging without validation layers would be a bit of a nightmare.

@@BrendanGalea Hey, I got the same issue with the throw std::runtime_error("validation layers requested, but not available!"); My Vulkan version is 1.2.162.1 and I am on MacOS. I have already clean all the project file, reinstall SDK and headers but it didn't change anything. Any thought ? PS: Huge thanks for this tutorial it rocks ;)

@@etiennep.1593 in your vulkansdk/Applications folder try running the vulkaninfo application. It should open a terminal and output a bunch of information. Do you see something like Layers: count = 9 ================= You should have a non-zero number of layers.

@@BrendanGalea Hey. I have checked that and it doesn't return me a count but an error... Here it is: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file /usr/local/Caskroom/vulkan-sdk/1.2.162.1/macOS/etc/vulkan/icd.d/MoltenVK_icd.json ERROR at /Users/lunarg/Dev/macos-sdk-build/Vulkan-Tools/vulkaninfo/vulkaninfo.h:668:vkCreateInstance failed with ERROR_INITIALIZATION_FAILED Saving session...completed. I have tried to reinstall MoltenVK with brew but it doesn't changed anything. It looks that the "/usr/local/Caskroom/vulkan-sdk/1.2.162.1/macOS/etc/" directory didn't exist... Even if I reinstall all SDK. EDIT: OK, I greped the JSON file and found it. The /etc/ dir was called "share" IDK why... I rename it and it looks better now. But I got an other problem... When I try to execute the programme, it can't create window surface. Here are logs: ./executable validation layer: ReadDataFilesInSearchPaths: Searching the following paths for manifest files: /Users/etienne/Documents/Vulkan/vulkan/implicit_layer.d:/etc/xdg/vulkan/implicit_layer.d:/Users/lunarg/Dev/macos-sdk-build/Vulkan-Loader/build/install/etc/vulkan/implicit_layer.d:/etc/vulkan/implicit_layer.d:/usr/local/share/vulkan/implicit_layer.d:/usr/share/vulkan/implicit_layer.d:/Users/etienne/.local/share/vulkan/implicit_layer.d validation layer: ReadDataFilesInSearchPaths: Searching the following paths for manifest files: /usr/local/Caskroom/vulkan-sdk/1.2.162.1/macOS/etc/vulkan/explicit_layer.d validation layer: ReadDataFilesInSearchPaths: Searching the following paths for manifest files: /usr/local/Caskroom/vulkan-sdk/1.2.162.1/macOS/etc/vulkan/icd.d/MoltenVK_icd.json validation layer: Searching for ICD drivers named /usr/local/lib/libMoltenVK.dylib validation layer: Build ICD instance extension list validation layer: Instance Extension: VK_KHR_device_group_creation (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_external_fence_capabilities (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_external_memory_capabilities (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_external_semaphore_capabilities (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_get_physical_device_properties2 (/usr/local/lib/libMoltenVK.dylib) version 0.0.2 validation layer: Instance Extension: VK_KHR_get_surface_capabilities2 (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_surface (/usr/local/lib/libMoltenVK.dylib) version 0.0.25 validation layer: Instance Extension: VK_EXT_debug_report (/usr/local/lib/libMoltenVK.dylib) version 0.0.9 validation layer: Instance Extension: VK_EXT_debug_utils (/usr/local/lib/libMoltenVK.dylib) version 0.0.2 validation layer: Instance Extension: VK_EXT_metal_surface (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_EXT_swapchain_colorspace (/usr/local/lib/libMoltenVK.dylib) version 0.0.4 validation layer: Instance Extension: VK_MVK_macos_surface (/usr/local/lib/libMoltenVK.dylib) version 0.0.3 validation layer: Instance Extension: VK_MVK_moltenvk (/usr/local/lib/libMoltenVK.dylib) version 0.0.29 validation layer: Loading layer library /usr/local/lib/libVkLayer_khronos_validation.dylib validation layer: Build ICD instance extension list validation layer: Instance Extension: VK_KHR_device_group_creation (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_external_fence_capabilities (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_external_memory_capabilities (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_external_semaphore_capabilities (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_get_physical_device_properties2 (/usr/local/lib/libMoltenVK.dylib) version 0.0.2 validation layer: Instance Extension: VK_KHR_get_surface_capabilities2 (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_KHR_surface (/usr/local/lib/libMoltenVK.dylib) version 0.0.25 validation layer: Instance Extension: VK_EXT_debug_report (/usr/local/lib/libMoltenVK.dylib) version 0.0.9 validation layer: Instance Extension: VK_EXT_debug_utils (/usr/local/lib/libMoltenVK.dylib) version 0.0.2 validation layer: Instance Extension: VK_EXT_metal_surface (/usr/local/lib/libMoltenVK.dylib) version 0.0.1 validation layer: Instance Extension: VK_EXT_swapchain_colorspace (/usr/local/lib/libMoltenVK.dylib) version 0.0.4 validation layer: Instance Extension: VK_MVK_macos_surface (/usr/local/lib/libMoltenVK.dylib) version 0.0.3 validation layer: Instance Extension: VK_MVK_moltenvk (/usr/local/lib/libMoltenVK.dylib) version 0.0.29 available extensions: VK_KHR_device_group_creation VK_KHR_external_fence_capabilities VK_KHR_external_memory_capabilities VK_KHR_external_semaphore_capabilities VK_KHR_get_physical_device_properties2 VK_KHR_get_surface_capabilities2 VK_KHR_surface VK_EXT_debug_report VK_EXT_debug_utils VK_EXT_metal_surface VK_EXT_swapchain_colorspace VK_MVK_macos_surface required extensions: VK_KHR_surface VK_EXT_metal_surface VK_EXT_debug_utils libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: failed to create window surface [1] 16229 abort ./executable If i comment the throw instruction, that tell me that: vkGetPhysicalDeviceSurfaceSupportKHR(physicalDevice, queueFamilyIndex, surface, pSupported) returns VkResultvalidation layer: Validation Error: [ UNASSIGNED-GeneralParameterError-RequiredParameter ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x99fb7dfd | vkGetPhysicalDeviceSurfaceSupportKHR: required parameter surface specified as VK_NULL_HANDLE validation layer: Validation Error: [ VUID-vkGetPhysicalDeviceSurfaceSupportKHR-surface-parameter ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_INSTANCE; | MessageID = 0x801f247e | Invalid VkSurfaceKHR Object 0x0. The Vulkan spec states: surface must be a valid VkSurfaceKHR handle. Seems that i got a problem with the surface...

Sorry!! I didn't see this reply. Is this still not working? Can you check the output of glfwCreateWindowSurface in the window implementation? Make sure in the initWindow function you have the line glfwWindowHint(GLFW_CLIENT_API, GLFW_NO_API);

What was the purpose of using SDL? Why try and use it over GLFW?

@@tweetyguy7347 sdl is not only the standard for engines but more powerful than glfw in terms of its features. Im also more familiar with it since ive been using sdl for around 4+ years

Ya unfortunately that is not all to uncommon. In the vulkanSDK/x86_64/bin folder you could try using the vkconfig program. Running that in the background has worked for some viewers if you really can't get the validation layers working.

@@BrendanGalea thank you for the suggestion I'll try that.

I do not know if I missed this is one of your previous videos, but you need to add #define GLFW_INCLUDE_VULKAN in the lve_window.h

sorry for the slow reply, any luck figuring this out? For debugging-help you can try posting in that group on the discord discord.gg/CUQkuKsszr, Myself or somebody else is usually pretty quick to respond

I am using GitHub? Or do you mean for the pastebin… lol that’s a good point, mainly because I record the videos before committing to git but I could make it work. Thanks for the feedback!

Thanks for the honest critical feedback. I agree with what you’re saying. However if I was to do this again I would do it in the same way. I want to build up more of the surrounding context around renderpasses, framebuffers, etc where the tutorials covering each of these topics can really go into the proper depth, before going back and then going over the swap chain and device code. When I was first writing the tutorials for the device and swap chain code it was just information overload so I scrapped them and went the other direction. So hopefully in about 4ish months when I have a chance to start making videos again there will be just a few more topics covered before we finally go back to rewrite the swap chain and device code

Thank you, I appreaciate the honest feedback! The main reasoning I avoided spending much time on the device setup code was I wanted to avoid just re-treading material on vulkan-tutorial.com, and also felt like its a lot of information to take in, and without some more context the later tutorials provide, is difficult to understand. But ya... honestly I'd really like to completely re-do the first 5 tutorials if I could, especially now that Vulkan 1.3 has been released which would drastically simplify the swap chain code to the point where I could have covered it from the start. As for all the other points you brought up, noted and I agree. I'll keep that in my when making future tutorials. Thanks again!