Context::getCompatibleDevices(const ContextCreateInfo& info) will return the wrong compatible device, when the physical device is CPU type.

[Frederique-Hsu]

Inside the Context::getCompatibleDevices(const ContextCreateInfo& info) method,

exactly calling the getDeviceExtensions(physicalDevice) function,

when passing an argument of CPU type, Vulkan API vkEnumerateDeviceExtensionProperties(physicalDevice, nullptr, &count, extensionProperties.data() will return almost all the extensions.

If user wants to enable the ray-tracing function, add VK_KHR_acceleration_structure and VK_KHR_ray_tracing_pipeline extensions, it can pass the checking missingExtensions = checkEntryArray(extensionProperties, info.deviceExtensions), and further regards the CPU device as
compatible device.

Actually this is a wrong compatible device. It should skip the device of CPU type.

[mklefrancois]

This function gets the VK_PHYSICAL_DEVICE_TYPE_DISCRETE_GPU, which should prioritize the selection of the final device to the hardware GPU. If ray tracing is requested and both the on-board and discrete GPUs support the feature, the discrete GPU will be selected.

Note that the information of all devices is reported, with requested and missing extensions.

Isn't the result you are getting?