Jetson AGX Orin unreal engin vulkan problem

We are building a game for Agx orin 64gb on jetson linux 36.2 and when try to run it we have error about vulkan so we looked at the vulkan and unreal logs about it here what we can found

Observed the following with vulkan validation layers enabled:

[1970.01.01-00.47.13:431][  0]LogVulkanRHI: Warning: *** [Error:Validation(VUID-VkDeviceCreateInfo-pNext-pNext)] Validation Error: [ VUID-VkDeviceCreateInfo-pNext-pNext ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x901f59ec | vkCreateDevice: pCreateInfo->pNext chain includes a structure with unknown VkStructureType (1000348013); Allowed structures are

the unknown VkStructureType(10003480013) is described at Vulkan® 1.3.274 - A Specification (with all registered extensions)

// Provided by VK_KHR_ray_query
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_RAY_QUERY_FEATURES_KHR = 1000348013

But the VK_KHR_ray_query is listed as an available extension that Unreal picks up.

[1970.01.01-00.47.13:428][  0]LogRHI: FValidationRHI on, intercepting Vulkan RHI!
[1970.01.01-00.47.13:428][  0]LogRHI: RHI Adapter Info:
[1970.01.01-00.47.13:428][  0]LogRHI:             Name: NVIDIA Tegra Orin (nvgpu)
[1970.01.01-00.47.13:428][  0]LogRHI:   Driver Version: 540.02 (internal:540.02, unified:)
[1970.01.01-00.47.13:428][  0]LogRHI:      Driver Date: 01-01-01
[1970.01.01-00.47.13:429][  0]LogVulkanRHI: Display: Found 182 available device extensions :
.
.
.
[1970.01.01-00.47.13:430][  0]LogVulkanRHI: Display:   + VK_KHR_ray_query
.
.
.

It seems that either the extension shouldn’t be reported as available or it shouldn’t cause further problems down the line. Can we get an update to the provided vulkan library and/or driver?’

This is a fresh install of Jetpack 5.1.2 on AGX Orin 64GB dev kit. I am unable to follow Vulkan SC Samples — Jetson Linux Developer Guide documentation. See Jetson orin (devkit 64GB) cannot run the cross compiled program of ue5.1.1 - #36 by sag.ibrahim for error details.I would try to produce a minimal modification that reproduce the error if the samples were working.

And you are not responding to the clues from validation layer. Please advise.

Hi @kamilutkumavi0,

can you share the code in question which triggers the validation error?

There are still quite a number of open issues with Vulkan validation layers, so it is hard to say whether this is triggered by that or rather by our driver misbehaving. So a code snippet would be most welcome.

@sag.ibrahim thanks for chiming in, although I am not sure if your comment was to give some advice or to add another question to this?

I am inheriting the project and problems, apologies for assuming that it was clear.

I tried to find the relevance of the other thread linked above. But I was a bit frustrated to be referred to samples, which can have completely different behavior than an engine. And the samples are for Vulkan SC whereas we don’t really need anything safety critical.

In any case, the vulkan-sc-sample is building now, after the CMakeLists.txt file is provided separately. And it may be possible to produce a minimal project that exhibits the same error as the unreal engine.

But the problem now is as follows, the vulkanscinfo binary that comes after building the samples shows the following extensions

evice Extensions: count = 11
        VK_EXT_blend_operation_advanced : extension revision 2
        VK_EXT_depth_clip_enable        : extension revision 1
        VK_EXT_depth_range_unrestricted : extension revision 1
        VK_EXT_index_type_uint8         : extension revision 1
        VK_EXT_line_rasterization       : extension revision 1
        VK_EXT_robustness2              : extension revision 1
        VK_KHR_synchronization2         : extension revision 1
        VK_NV_external_memory_sci_buf   : extension revision 1
        VK_NV_external_sci_sync         : extension revision 2
        VK_NV_external_sci_sync2        : extension revision 1
        VK_NV_private_vendor_info       : extension revision 2

But the /usr/bin/vulkaninfo shows the following:


Device Extensions: count = 159
	VK_EXT_4444_formats                         : extension revision 1
	VK_EXT_blend_operation_advanced             : extension revision 2
	VK_EXT_border_color_swizzle                 : extension revision 1
	VK_EXT_buffer_device_address                : extension revision 2
	VK_EXT_calibrated_timestamps                : extension revision 2
	VK_EXT_color_write_enable                   : extension revision 1
	VK_EXT_conditional_rendering                : extension revision 2
	VK_EXT_conservative_rasterization           : extension revision 1
	VK_EXT_custom_border_color                  : extension revision 12
	VK_EXT_depth_clip_control                   : extension revision 1
	VK_EXT_depth_clip_enable                    : extension revision 1
	VK_EXT_depth_range_unrestricted             : extension revision 1
	VK_EXT_descriptor_indexing                  : extension revision 2
	VK_EXT_discard_rectangles                   : extension revision 1
	VK_EXT_display_control                      : extension revision 1
	VK_EXT_extended_dynamic_state               : extension revision 1
	VK_EXT_extended_dynamic_state2              : extension revision 1
	VK_EXT_external_memory_dma_buf              : extension revision 1
	VK_EXT_external_memory_host                 : extension revision 1
	VK_EXT_fragment_shader_interlock            : extension revision 1
	VK_EXT_global_priority                      : extension revision 2
	VK_EXT_global_priority_query                : extension revision 1
	VK_EXT_graphics_pipeline_library            : extension revision 1
	VK_EXT_host_query_reset                     : extension revision 1
	VK_EXT_image_2d_view_of_3d                  : extension revision 1
	VK_EXT_image_drm_format_modifier            : extension revision 2
	VK_EXT_image_robustness                     : extension revision 1
	VK_EXT_image_view_min_lod                   : extension revision 1
	VK_EXT_index_type_uint8                     : extension revision 1
	VK_EXT_inline_uniform_block                 : extension revision 1
	VK_EXT_line_rasterization                   : extension revision 1
	VK_EXT_load_store_op_none                   : extension revision 1
	VK_EXT_memory_budget                        : extension revision 1
	VK_EXT_multi_draw                           : extension revision 1
	VK_EXT_physical_device_drm                  : extension revision 1
	VK_EXT_pipeline_creation_cache_control      : extension revision 3
	VK_EXT_pipeline_creation_feedback           : extension revision 1
	VK_EXT_post_depth_coverage                  : extension revision 1
	VK_EXT_primitive_topology_list_restart      : extension revision 1
	VK_EXT_primitives_generated_query           : extension revision 1
	VK_EXT_private_data                         : extension revision 1
	VK_EXT_provoking_vertex                     : extension revision 1
	VK_EXT_queue_family_foreign                 : extension revision 1
	VK_EXT_robustness2                          : extension revision 1
	VK_EXT_sample_locations                     : extension revision 1
	VK_EXT_sampler_filter_minmax                : extension revision 2
	VK_EXT_scalar_block_layout                  : extension revision 1
	VK_EXT_separate_stencil_usage               : extension revision 1
	VK_EXT_shader_atomic_float                  : extension revision 1
	VK_EXT_shader_demote_to_helper_invocation   : extension revision 1
	VK_EXT_shader_image_atomic_int64            : extension revision 1
	VK_EXT_shader_subgroup_ballot               : extension revision 1
	VK_EXT_shader_subgroup_vote                 : extension revision 1
	VK_EXT_shader_viewport_index_layer          : extension revision 1
	VK_EXT_subgroup_size_control                : extension revision 2
	VK_EXT_texel_buffer_alignment               : extension revision 1
	VK_EXT_tooling_info                         : extension revision 1
	VK_EXT_transform_feedback                   : extension revision 1
	VK_EXT_vertex_attribute_divisor             : extension revision 3
	VK_EXT_vertex_input_dynamic_state           : extension revision 2
	VK_EXT_ycbcr_2plane_444_formats             : extension revision 1
	VK_EXT_ycbcr_image_arrays                   : extension revision 1
	VK_KHR_16bit_storage                        : extension revision 1
	VK_KHR_8bit_storage                         : extension revision 1
	VK_KHR_acceleration_structure               : extension revision 13
	VK_KHR_bind_memory2                         : extension revision 1
	VK_KHR_buffer_device_address                : extension revision 1
	VK_KHR_copy_commands2                       : extension revision 1
	VK_KHR_create_renderpass2                   : extension revision 1
	VK_KHR_dedicated_allocation                 : extension revision 3
	VK_KHR_deferred_host_operations             : extension revision 4
	VK_KHR_depth_stencil_resolve                : extension revision 1
	VK_KHR_descriptor_update_template           : extension revision 1
	VK_KHR_device_group                         : extension revision 4
	VK_KHR_draw_indirect_count                  : extension revision 1
	VK_KHR_driver_properties                    : extension revision 1
	VK_KHR_dynamic_rendering                    : extension revision 1
	VK_KHR_external_fence                       : extension revision 1
	VK_KHR_external_fence_fd                    : extension revision 1
	VK_KHR_external_memory                      : extension revision 1
	VK_KHR_external_memory_fd                   : extension revision 1
	VK_KHR_external_semaphore                   : extension revision 1
	VK_KHR_external_semaphore_fd                : extension revision 1
	VK_KHR_format_feature_flags2                : extension revision 1
	VK_KHR_fragment_shading_rate                : extension revision 2
	VK_KHR_get_memory_requirements2             : extension revision 1
	VK_KHR_global_priority                      : extension revision 1
	VK_KHR_image_format_list                    : extension revision 1
	VK_KHR_imageless_framebuffer                : extension revision 1
	VK_KHR_maintenance1                         : extension revision 2
	VK_KHR_maintenance2                         : extension revision 1
	VK_KHR_maintenance3                         : extension revision 1
	VK_KHR_maintenance4                         : extension revision 2
	VK_KHR_multiview                            : extension revision 1
	VK_KHR_pipeline_executable_properties       : extension revision 1
	VK_KHR_pipeline_library                     : extension revision 1
	VK_KHR_push_descriptor                      : extension revision 2
	VK_KHR_ray_query                            : extension revision 1
	VK_KHR_ray_tracing_pipeline                 : extension revision 1
	VK_KHR_relaxed_block_layout                 : extension revision 1
	VK_KHR_sampler_mirror_clamp_to_edge         : extension revision 3
	VK_KHR_sampler_ycbcr_conversion             : extension revision 14
	VK_KHR_separate_depth_stencil_layouts       : extension revision 1
	VK_KHR_shader_atomic_int64                  : extension revision 1
	VK_KHR_shader_clock                         : extension revision 1
	VK_KHR_shader_draw_parameters               : extension revision 1
	VK_KHR_shader_float16_int8                  : extension revision 1
	VK_KHR_shader_float_controls                : extension revision 4
	VK_KHR_shader_integer_dot_product           : extension revision 1
	VK_KHR_shader_non_semantic_info             : extension revision 1
	VK_KHR_shader_subgroup_extended_types       : extension revision 1
	VK_KHR_shader_subgroup_uniform_control_flow : extension revision 1
	VK_KHR_shader_terminate_invocation          : extension revision 1
	VK_KHR_shared_presentable_image             : extension revision 1
	VK_KHR_spirv_1_4                            : extension revision 1
	VK_KHR_storage_buffer_storage_class         : extension revision 1
	VK_KHR_swapchain                            : extension revision 70
	VK_KHR_swapchain_mutable_format             : extension revision 1
	VK_KHR_synchronization2                     : extension revision 1
	VK_KHR_timeline_semaphore                   : extension revision 2
	VK_KHR_uniform_buffer_standard_layout       : extension revision 1
	VK_KHR_variable_pointers                    : extension revision 1
	VK_KHR_vulkan_memory_model                  : extension revision 3
	VK_KHR_workgroup_memory_explicit_layout     : extension revision 1
	VK_KHR_zero_initialize_workgroup_memory     : extension revision 1
	VK_NVX_binary_import                        : extension revision 1
	VK_NVX_image_view_handle                    : extension revision 2
	VK_NVX_multiview_per_view_attributes        : extension revision 1
	VK_NV_clip_space_w_scaling                  : extension revision 1
	VK_NV_compute_shader_derivatives            : extension revision 1
	VK_NV_cooperative_matrix                    : extension revision 1
	VK_NV_corner_sampled_image                  : extension revision 2
	VK_NV_coverage_reduction_mode               : extension revision 1
	VK_NV_cuda_kernel_launch                    : extension revision 2
	VK_NV_dedicated_allocation                  : extension revision 1
	VK_NV_dedicated_allocation_image_aliasing   : extension revision 1
	VK_NV_device_diagnostic_checkpoints         : extension revision 2
	VK_NV_device_diagnostics_config             : extension revision 1
	VK_NV_device_generated_commands             : extension revision 3
	VK_NV_fill_rectangle                        : extension revision 1
	VK_NV_fragment_coverage_to_color            : extension revision 1
	VK_NV_fragment_shader_barycentric           : extension revision 1
	VK_NV_fragment_shading_rate_enums           : extension revision 1
	VK_NV_framebuffer_mixed_samples             : extension revision 1
	VK_NV_geometry_shader_passthrough           : extension revision 1
	VK_NV_inherited_viewport_scissor            : extension revision 1
	VK_NV_linear_color_attachment               : extension revision 1
	VK_NV_mesh_shader                           : extension revision 1
	VK_NV_ray_tracing                           : extension revision 3
	VK_NV_ray_tracing_motion_blur               : extension revision 1
	VK_NV_representative_fragment_test          : extension revision 2
	VK_NV_sample_mask_override_coverage         : extension revision 1
	VK_NV_scissor_exclusive                     : extension revision 1
	VK_NV_shader_image_footprint                : extension revision 2
	VK_NV_shader_sm_builtins                    : extension revision 1
	VK_NV_shader_subgroup_partitioned           : extension revision 1
	VK_NV_shading_rate_image                    : extension revision 3
	VK_NV_viewport_array2                       : extension revision 1
	VK_NV_viewport_swizzle                      : extension revision 1

The latter agrees with the extensions reported by unreal.

So, I would like to start with some samples that share the environment with unreal executable. That way we can verify if the error caught by the validation layers is the actual error. Does that make sense?

following from this repository seems like an option: GitHub - KhronosGroup/Vulkan-Samples: One stop solution for all Vulkan samples

I executed the following commands specifed in root README.adoc and Vulkan-Samples/docs/build.adoc at main · KhronosGroup/Vulkan-Samples · GitHub . I had already updated cmake to 3.28.1 before, in case that is relevant.

sudo apt install git-lfs

git clone --recurse-submodules https://github.com/KhronosGroup/Vulkan-Samples.git
cd Vulkan-Samples
sudo apt-get install cmake g++ xorg-dev libglu1-mesa-dev
cmake -G "Unix Makefiles" -Bbuild/linux -DCMAKE_BUILD_TYPE=Release
cmake --build build/linux --config Release --target vulkan_samples -j$(nproc)
./build/linux/app/bin/Release/aarch64/vulkan_samples --help

which works quite well.

swapchain_images sample works quite well.

./build/linux/app/bin/Release/aarch64/vulkan_samples sample swapchain_images

but the ray_queries sample fails miserably, after reporting the VK_KHR_ray_query extension as supported, in confirmation with the previous error pointed at by validation layers.

~/Vulkan-Samples$ ./build/linux/app/bin/Release/aarch64/vulkan_samples sample ray_queries
[info] Logger initialized
[info] Initializing Vulkan sample
[info] Vulkan debug utils enabled (VK_EXT_debug_utils)
[info] Extension VK_KHR_get_physical_device_properties2 found, enabling it
[info] Extension VK_EXT_debug_utils found, enabling it
[info] Extension VK_KHR_xcb_surface found, enabling it
[info] Enabled Validation Layers:
[info] Found GPU: NVIDIA Tegra Orin (nvgpu)
[warning] Couldn't find a discrete physical device, picking default GPU
[info] Selected GPU: NVIDIA Tegra Orin (nvgpu)
[info] Dedicated Allocation enabled
[info] Device supports the following requested extensions:
[info]   	VK_KHR_get_memory_requirements2
[info]   	VK_KHR_dedicated_allocation
[info]   	VK_KHR_swapchain
[info]   	VK_KHR_shader_float_controls
[info]   	VK_KHR_spirv_1_4
[info]   	VK_KHR_deferred_host_operations
[info]   	VK_KHR_buffer_device_address
[info]   	VK_EXT_descriptor_indexing
[info]   	VK_KHR_acceleration_structure
[info]   	VK_KHR_ray_query
[error] [framework/platform/platform.cpp:169] Error Message: Cannot create device : ERROR_INITIALIZATION_FAILED
[error] [framework/platform/platform.cpp:170] Failed when running application ray_queries
Press return to continue

So, I repeat:

“It seems that either the extension shouldn’t be reported as available or it shouldn’t cause further problems down the line. Can we get an update to the provided vulkan library and/or driver?”

Thank you for the clarification!

And thank you for trying the samples, that should help nail this down.

I wonder if it has to do with the fact that the Orin GPU is not actually a separate physical device…

I will reach out to Daniel and see if he has some suggestion.

Thank you as well! We are eagerly waiting for a resolution.

Hi @sag.ibrahim

You definitely don’t want the Vulkan SC samples, etc for what you are doing, so the Vulkan-Samples that you found on github are the right place to start.

However @kamilutkumavi0 seemed to be using Jetpack 6 (36.2), and you are using Jetpack 5.2.1.
Can you make sure you are using the latest Jetpack 6 build?

-Daniel

Hi,

6.0 has the same problem. and more even. I have had to start fresh from 5.1.2. Please try it on your end.

Please don’t ask me to switch to a developer preview (6.0 DP) again. Did you have an update related to this issue since yesterday? Otherwise, you are just going to bury me with different problems.

Are you talking about this thread: Jetson orin (devkit 64GB) cannot run the cross compiled program of ue5.1.1 - #36 by sag.ibrahim ?

Because there you are using the Vulkan SC samples and validation layers.
Anything with “vksc” or “vulkansc” in the name is for Vulkan SC.

If you are trying to do ray tracing/query - you want Vulkan NOT Vulkan SC. Vulkan SC (SC=Safety Critical) is a more minimal driver intended for environments that need safety certification (such as automotive).

Yes, I have had to start fresh with 5.1.2 per Daniel’s suggestion. I think it is fair to say that you can try out the Vulkan-Samples on 6.0 and ask me to switch if that works properly.

We don’t particularly need ray tracing, but the engine can’t be blamed when the application crashes for passing a VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_RAY_QUERY_FEATURES_KHR struct when the VK_KHR_ray_query extension is reported as available or whatever the problem is with ray_queries sample on Vulkan-Samples repo.

I will start the download of 6.0, it might take a while.

Hi sag.ibrahim, not everyone here is set up to run Vulkan on a Jetson device, meaning we are not able to simply “try out” something on that platform.

We do have QA systems that regularly run also Vulkan conformance testing on all kind of NVIDIA devices, including Jetson and from what I can find there are no reported issues. Of course that does not mean that everything is 100% bug free.

I can open an internal issue for this, but what would help me greatly would be if you had some more verbose output or a stack trace of a debug build of the ray_queries sample app where the latest error occurred. I need a bit more context than

[error] [framework/platform/platform.cpp:169] Error Message: Cannot create device : ERROR_INITIALIZATION_FAILED

If you could provide that, I would appreciate it.

Thanks!

That is quite absurd. I am somehow more capable than a billion dollar company for debugging some public code? What you are saying is essentially a rephrasing of ‘works on my machine’. And you take no responsibility for dragging us through Vulkan SC as a standard response? And now the only responder that resembles a human is pulling back because I am hesitant to switch to a ‘developer preview’ for a very standard code to be run? Please have mercy!

I am sorry if we seem unhelpful, at the same time I kindly ask for you to keep it civil. I can assure you we are all still human here.

It is not a question of capability, just a question of time. You are already set up with all the necessary tools, we are not. All I am asking for is a bit more consistent information that I can add to an internal bug report. Because the current information quite simply is too confusing to get started.

  • Different Jetpack versions
  • Different Vulkan releases
  • Different issue descriptions
  • The Vulkan error is non-descriptive based on a public, non-NVIDIA sample app

I know the “works for me” answer is unsatisfactory, that is why I asked for more information to be able to help instead of shrugging it off.

I apologize if I crossed any boundaries of civility. It is just that the possibility of being deflected by an llm is quite bewildering and I couldn’t focus on the requirement of a physical device.

I will run a debug build and try to provide more details. But I am not sure how to get information from vulkan api boundary. Vulkan-Samples seem to have an option for validation layers Vulkan-Samples/docs/build.adoc at main · KhronosGroup/Vulkan-Samples · GitHub. Would that be a separate, more helpful system or all validation layers are considered unreliable for reporting purposes?

I apologize again for freaking out. I hope you don’t find it so unreasonable that I got knocked off balance on the news of the complete irrelevance of Vulkan SC.

I am now on a fresh install with jetpack 6 and jetson linux 36.2. Following from the Vulkan-Samples repo, the ray_queries sample fails with the
same error as before. I have tried to comment out the lines 82, 84 and 115-119 in the file ray_queries.cpp. link: Vulkan-Samples/samples/extensions/ray_queries/ray_queries.cpp at main · KhronosGroup/Vulkan-Samples · GitHub

081.	set_api_version(VK_API_VERSION_1_1);
082.	add_device_extension(VK_KHR_RAY_QUERY_EXTENSION_NAME);
083.
084.	// Ray tracing related extensions required by this sample
085.	add_device_extension(VK_KHR_ACCELERATION_STRUCTURE_EXTENSION_NAME);
   .
   .
   .
115.	 RequestFeature(gpu)
116.	    .request(VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_BUFFER_DEVICE_ADDRESS_FEATURES, &VkPhysicalDeviceBufferDeviceAddressFeatures::bufferDeviceAddress)
117.	    .request(VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_ACCELERATION_STRUCTURE_FEATURES_KHR, &VkPhysicalDeviceAccelerationStructureFeaturesKHR::accelerationStructure)
118.	    .request(VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_RAY_QUERY_FEATURES_KHR, &VkPhysicalDeviceRayQueryFeaturesKHR::rayQuery)
119.	    .request(VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_RAY_TRACING_PIPELINE_FEATURES_KHR, &VkPhysicalDeviceRayTracingPipelineFeaturesKHR::rayTracingPipeline);

This way we are able to pass the device creation phase:

~/Vulkan-Samples$ ./build/linux/app/bin/Release/aarch64/vulkan_samples sample ray_queries
[info] Logger initialized
[info] Initializing Vulkan sample
[info] Vulkan debug utils enabled (VK_EXT_debug_utils)
[info] Extension VK_EXT_debug_utils found, enabling it
[info] Extension VK_KHR_get_physical_device_properties2 found, enabling it
[info] Extension VK_KHR_xcb_surface found, enabling it
[error] [framework/core/instance.cpp:96] Validation Layer VK_LAYER_KHRONOS_validation not found
[warning] Couldn't enable validation layers (see log for error) - falling back
[error] [framework/core/instance.cpp:96] Validation Layer VK_LAYER_LUNARG_standard_validation not found
[warning] Couldn't enable validation layers (see log for error) - falling back
[error] [framework/core/instance.cpp:96] Validation Layer VK_LAYER_GOOGLE_threading not found
[warning] Couldn't enable validation layers (see log for error) - falling back
[error] [framework/core/instance.cpp:96] Validation Layer VK_LAYER_LUNARG_core_validation not found
[warning] Couldn't enable validation layers (see log for error) - falling back
[info] Enabled Validation Layers:
[info] Found GPU: NVIDIA Tegra Orin (nvgpu)
[warning] Couldn't find a discrete physical device, picking default GPU
[info] Selected GPU: NVIDIA Tegra Orin (nvgpu)
[info] Dedicated Allocation enabled
[info] Device supports the following requested extensions:
[info]   	VK_KHR_get_memory_requirements2
[info]   	VK_KHR_dedicated_allocation
[info]   	VK_KHR_swapchain
[info]   	VK_KHR_shader_float_controls
[info]   	VK_KHR_spirv_1_4
[info]   	VK_KHR_deferred_host_operations
[info]   	VK_EXT_descriptor_indexing
[info]   	VK_KHR_buffer_device_address
[info] Surface supports the following surface formats:
[info]   	VK_FORMAT_B8G8R8A8_UNORM, VK_COLORSPACE_SRGB_NONLINEAR_KHR
[info]   	VK_FORMAT_B8G8R8A8_SRGB, VK_COLORSPACE_SRGB_NONLINEAR_KHR
[info] Surface supports the following present modes:
[info]   	VK_PRESENT_MODE_FIFO_KHR
[info]   	VK_PRESENT_MODE_FIFO_RELAXED_KHR
[info]   	VK_PRESENT_MODE_IMMEDIATE_KHR
[warning] (Swapchain) Image extent (0, 0) not supported. Selecting (1280, 720).
[warning] (Swapchain) Surface format (VK_FORMAT_UNDEFINED, VK_COLORSPACE_SRGB_NONLINEAR_KHR) not supported. Selecting (VK_FORMAT_B8G8R8A8_SRGB, VK_COLORSPACE_SRGB_NONLINEAR_KHR).
[info] (Swapchain) Image usage flags: VK_IMAGE_USAGE_TRANSFER_SRC_BIT VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT 
[warning] (Swapchain) Composite alpha 'VK_COMPOSITE_ALPHA_INHERIT_BIT_KHR' not supported. Selecting 'VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR.
[warning] (Swapchain) Present mode 'VK_PRESENT_MODE_MAILBOX_KHR' not supported. Selecting 'VK_PRESENT_MODE_FIFO_KHR'.
[info] (Swapchain) Surface format selected: VK_FORMAT_B8G8R8A8_SRGB, VK_COLORSPACE_SRGB_NONLINEAR_KHR
[info] Depth format selected: VK_FORMAT_D32_SFLOAT
[info] Depth format selected: VK_FORMAT_D32_SFLOAT
[info] Depth format selected: VK_FORMAT_D32_SFLOAT
[info] Depth format selected: VK_FORMAT_D32_SFLOAT
[info] glTF file contains extension: KHR_lights_punctual
[info] Loaded gltf image #3 (sponza_thorn_diff.ktx)
[info] Loaded gltf image #11 (sponza_floor_a_diff.ktx)
[info] Loaded gltf image #9 (sponza_column_c_diff.ktx)
[info] Loaded gltf image #4 (vase_plant.ktx)
[info] Loaded gltf image #2 (background.ktx)
[info] Loaded gltf image #10 (sponza_details_diff.ktx)
[info] Loaded gltf image #0 (sponza_flagpole_diff.ktx)
[info] Loaded gltf image #1 (lion.ktx)
[info] Loaded gltf image #13 (vase_dif.ktx)
[info] Loaded gltf image #17 (chain_texture.ktx)
[info] Loaded gltf image #5 (spnza_bricks_a_diff.ktx)
[info] Loaded gltf image #12 (sponza_column_b_diff.ktx)
[info] Loaded gltf image #8 (sponza_arch_diff.ktx)
[info] Loaded gltf image #7 (sponza_column_a_diff.ktx)
[info] Loaded gltf image #16 (vase_round.ktx)
[info] Loaded gltf image #15 (vase_hanging.ktx)
[info] Loaded gltf image #14 (spnza_bricks_a_diff.ktx)
[info] Loaded gltf image #21 (sponza_fabric_green_diff.ktx)
[info] Loaded gltf image #6 (sponza_ceiling_a_diff.ktx)
[info] Loaded gltf image #23 (sponza_fabric_diff.ktx)
[info] Loaded gltf image #24 (sponza_roof_diff.ktx)
[info] Loaded gltf image #22 (sponza_fabric_blue_diff.ktx)
[info] Loaded gltf image #19 (sponza_curtain_diff.ktx)
[info] Loaded gltf image #18 (sponza_curtain_blue_diff.ktx)
[info] Loaded gltf image #20 (sponza_curtain_green_diff.ktx)
[info] Time spent loading images: 0.019900 seconds across 12 threads.
[error] [framework/platform/platform.cpp:169] Error Message: Cannot create Buffer : ERROR_VALIDATION_FAILED_EXT
[error] [framework/platform/platform.cpp:170] Failed when running application ray_queries
[info] Total device memory leaked: 0 bytes.
Press return to continue

Now, both the VK_KHR_ray_query and VK_KHR_acceleration_structure is reported on vulkaninfo, but they cause errors when relied upon. Is this narrowing down the problem for you @MarkusHoHo @dkoch ?

@1903009055 may I ask that you try out the Vulkan-Samplesrepo, particularly the ray_queries sample on the 32GB device and see if this is the divergence? I apologize for the previous request of activating Vulkan SC validation layers, that turned out to be irrelevant.

@MarkusHoHo I know you have asked for a stack trace but Vulkan API is notoriously sparse in details and that kind of information is really not applicable in this case. I hope you will find the change in behavior by whether an extension is requested as sufficient detail to notify relevant parties.