Pros of Vulkan-Samples

• Comprehensive collection of Vulkan samples covering various aspects of the API
• Regularly updated with new features and best practices
• Well-documented and maintained by the Khronos Group

Cons of Vulkan-Samples

• Focuses on general Vulkan features, not specifically on ray tracing
• May be overwhelming for beginners due to its extensive coverage

Code Comparison

vk_raytracing_tutorial_KHR:

void createBottomLevelAS()
{
  // Create the bottom-level acceleration structure
  nvvk::RaytracingBuilderKHR::BottomLevelInput bottomLevelInput;
  bottomLevelInput.flags = VK_BUILD_ACCELERATION_STRUCTURE_PREFER_FAST_TRACE_BIT_KHR;
  // ... (specific ray tracing setup)
}

Vulkan-Samples:

void create_acceleration_structure()
{
  VkAccelerationStructureCreateInfoKHR create_info{};
  create_info.sType = VK_STRUCTURE_TYPE_ACCELERATION_STRUCTURE_CREATE_INFO_KHR;
  create_info.type = VK_ACCELERATION_STRUCTURE_TYPE_BOTTOM_LEVEL_KHR;
  // ... (general Vulkan acceleration structure setup)
}

The vk_raytracing_tutorial_KHR code is more focused on ray tracing specifics, while Vulkan-Samples provides a more general Vulkan implementation. The former uses NVIDIA's nvvk helper library, while the latter uses standard Vulkan calls.

Pros of Vulkan

• Comprehensive collection of Vulkan examples covering a wide range of features and techniques
• Well-documented and organized codebase with clear explanations for each example
• Regularly updated to include new Vulkan features and best practices

Cons of Vulkan

• Focuses on general Vulkan usage rather than specializing in ray tracing
• May be overwhelming for beginners due to the large number of examples and advanced topics

Code Comparison

vk_raytracing_tutorial_KHR:

void HelloVulkan::createBottomLevelAS()
{
  // ... (ray tracing specific code)
}

Vulkan:

void VulkanExample::prepareUniformBuffers()
{
  // ... (general Vulkan setup code)
}

Summary

Vulkan provides a broader overview of Vulkan capabilities, making it suitable for developers looking to explore various aspects of the API. vk_raytracing_tutorial_KHR, on the other hand, offers a more focused approach to ray tracing in Vulkan, making it ideal for those specifically interested in implementing ray tracing techniques.

While Vulkan covers a wide range of topics, vk_raytracing_tutorial_KHR delves deeper into ray tracing specifics, providing more detailed examples and explanations for this particular use case. Developers should choose based on their specific needs and level of expertise in Vulkan programming.

Pros of vk_mini_path_tracer

• More compact and focused implementation, easier for beginners to grasp
• Includes a complete path tracing algorithm, demonstrating advanced rendering techniques
• Utilizes modern C++ features and coding practices

Cons of vk_mini_path_tracer

• Less comprehensive in covering Vulkan ray tracing features compared to vk_raytracing_tutorial_KHR
• May not be as suitable for learning the full range of Vulkan ray tracing capabilities
• Limited to a specific rendering technique (path tracing) rather than exploring various ray tracing applications

Code Comparison

vk_mini_path_tracer:

void createRayTracingPipeline()
{
  vk::RayTracingPipelineCreateInfoKHR rayPipelineInfo;
  rayPipelineInfo.setStages(stages);
  rayPipelineInfo.setGroups(groups);
  rayPipelineInfo.setMaxPipelineRayRecursionDepth(10);
  rayPipelineInfo.setLayout(pipelineLayout);
  m_rtPipeline = m_device.createRayTracingPipelineKHR({}, {}, rayPipelineInfo);
}

vk_raytracing_tutorial_KHR:

void createRayTracingPipeline()
{
  VkRayTracingPipelineCreateInfoKHR rayPipelineInfo{VK_STRUCTURE_TYPE_RAY_TRACING_PIPELINE_CREATE_INFO_KHR};
  rayPipelineInfo.stageCount = static_cast<uint32_t>(stages.size());
  rayPipelineInfo.pStages = stages.data();
  rayPipelineInfo.groupCount = static_cast<uint32_t>(groups.size());
  rayPipelineInfo.pGroups = groups.data();
  rayPipelineInfo.maxPipelineRayRecursionDepth = 1;
  rayPipelineInfo.layout = pipelineLayout;
  vkCreateRayTracingPipelinesKHR(device, VK_NULL_HANDLE, VK_NULL_HANDLE, 1, &rayPipelineInfo, nullptr, &pipeline);
}

Pros of Filament

• Comprehensive real-time rendering engine with support for multiple platforms
• Extensive documentation and examples for easier adoption
• Active development and maintenance by Google

Cons of Filament

• Steeper learning curve due to its broader scope and feature set
• May be overkill for simple ray tracing projects
• Less focused on Vulkan-specific ray tracing techniques

Code Comparison

vk_raytracing_tutorial_KHR:

void createRayTracingPipeline()
{
  vk::ShaderModule rayGenShader = createShaderModule(loadFile("shaders/raygen.rgen.spv"));
  vk::ShaderModule missShader = createShaderModule(loadFile("shaders/miss.rmiss.spv"));
  vk::ShaderModule chitShader = createShaderModule(loadFile("shaders/chit.rchit.spv"));
  // ... (pipeline creation code)
}

Filament:

FilamentApp& app = FilamentApp::get();
auto& engine = app.getEngine();
auto scene = engine.createScene();
auto& view = app.getGuiView();
view.setScene(scene);
// ... (scene setup and rendering code)

The vk_raytracing_tutorial_KHR focuses on low-level Vulkan ray tracing setup, while Filament provides a higher-level abstraction for scene management and rendering across multiple platforms.