-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong AMD driver info detected #10109
Comments
On Windows, this comes from -[Unknown] |
Can you paste what this logs? master...unknownbrackets:driver-ver Maybe there are multiple "video controllers" (this is my suspicion) and the first one happens to be OpenCL.... -[Unknown] |
Here:
|
Hmm, maybe at least the driver date is correct? Mine looks correct. I guess we need to see a system with old drivers, though... I wonder if it's the release date or simply the file modification time, which would be worthless. -[Unknown] |
For Vulkan at least I think this https://www.khronos.org/registry/vulkan/specs/1.0/man/html/vkGetPhysicalDeviceProperties.html could maybe be used instead? Edit: And yeah driver date seems fine. 2017.11.02 was latest driver. |
Yeah - we call it in VulkanContext - what type of
I imagine on a multi-GPU system we're listing the wrong version entirely, heh... -[Unknown] |
Realized we're already showing the version, d'oh. Looks like the broken one was 00404001 from December 2016, before the bug was fixed. Maybe we can just take 00407000 as the minimum version (probably even 00406000 works, though.) -[Unknown] |
Nice:). BTW Vulkan Hardware Capability Viewer software uses a simple:
to get a nice text number from that version id which matches what AMD software shows up: "1.7.0" so yeah to me that part just looked like a random number, but is in fact driver version. They also have some special code for Nvidia apparently more complex versioning ~ here |
Basically all backends reports same driver version:
Which from what I can see is my OpenCL driver version:
Wouldn't really care about the info itself much, but I was hoping the "fix" for #10065 could get limited to older Vulkan drivers as this problematic feature works fine for me and probably would for all other people with gpu's that still get driver updates in 2017.
The text was updated successfully, but these errors were encountered: