Regarding "fake" database entries for Fermi based GPUs

[saschawillems]

Regarding "fake" database entries for Fermi based GPUs

[SaschaWillems]

Thank you very much for this detailled information. This is a bug in the current version and will be fixed in a future version.

As a temporary workaround I have disabled upload of reports without formats on the server side and will remove the invalid reports.

[timjp87]

Why does it manage to execute this part, though:

VulkanCapsViewer/vulkanDeviceInfo.hpp

Lines 199 to 206 in d5c5f3f

	vkGetPhysicalDeviceProperties(device, &props);
	properties.clear();
	properties["devicename"] = props.deviceName;
	properties["driverversion"] = vulkanResources::versionToString(props.driverVersion);
	properties["apiversion"] = vulkanResources::versionToString(props.apiVersion);
	properties["vendorid"] = to_string(props.vendorID);
	properties["deviceid"] = to_string(props.deviceID);

For me that looks like it actually entered the driver and fetched all the information to populate the pointer to props so that the deviceid can be printed out as a member of it. I am using a GTX 580 and if it doesn't have a Vulkan driver, why does it return a deviceid that must be somehow in the Vulkan driver and is associated with the 580 model?

[SaschaWillems]

This is a beta driver and may be an unintentional left over. There is (currently) no Vulkan support for Fermi (NV confirmed this).

And since not a single format is supported, it's no usable Vulkan implementation.

[SaschaWillems]

Closing this as recent drivers won't expose Vulkan on non-supported GPUs anymore. I also deleted the fermi reports from the database.