Create a list of DX12 supported cards to supplement detection about whynotwin11 HOT 20 OPEN

@rcmaehl could the solution to this be same as in #223 ?

from whynotwin11.

This issue needs to be opened again. I launched the latest dev build, and it still shows in red that I don't have DX12 and WDDM2.0, even though I'm using Nvidia Pascal GPU, which is fully compatible with these features.

from whynotwin11.

@nbmrjuhneibkr Could you post your dxdiag?

from whynotwin11.

Dxdiag shows DX11.1 and WDDM1.3, since I'm on Windows 8.1. Dxdiag is not an accurate source for this information, since it shows only features supported by the currently installed OS, and not by hardware.

from whynotwin11.

By not posting your dxdiag you are making it harder for us to check this issue. You should know that wnw11 already checks for DirectX hardware compatibility.

from whynotwin11.

Here it is, but I don't know what are you expecting to find there. I removed some parts that are not related to this problem - storage, audio etc.
DxDiag.txt

from whynotwin11.

Here it is, but I don't know what are you expecting to find there. I removed some parts that are not related to this problem - storage, audio etc.
DxDiag.txt

You are running Windows 8.1 which does not support DirectX 12. Oddly enough, Feature Level is reported as 11.1 as well. I'm unsure if dxdiag is unable to recognize that it's a DirectX 12 card because DX12 isn't installed or what's happening here. Can you send a screenshot of GPU-Z?

from whynotwin11.

Dxdiag in 8.1 predates DX12, so it probably just doesn't know how to recognize it.
Here is GPU-Z:

from whynotwin11.

I may just need to create a database of DX12 cards for "enhanced" detection.

from whynotwin11.

I think that the only way to make this app accurate is to rely on the OS as little as possible - not just for DirectX, but also for TPM, UEFI, SecureBoot. Just because some feature is disabled at the moment doesn't mean that it's not present in hardware.

If it can't be accurate, then the user would be better off posting detailed specs on some forum and asking if Windows 11 can run on that PC.

from whynotwin11.

Ok @nbmrjuhneibkr since you say that "I think that the only way to make this app accurate is to rely on the OS as little as possible - not just for DirectX, but also for TPM, UEFI, SecureBoot." Please help us with creating following lists:

• Every motherboard with UEFI
• Every motherboard with TPM (support)
• Every GPU supporting Directx 12
• Every x thing that is in the following document by Microsoft

Don't you see how much of (mostly pointless) data it would be? That's why the application should try to detect these features instead of relying on some hardcoded data sheets.

from whynotwin11.

Ok @nbmrjuhneibkr since you say that "I think that the only way to make this app accurate is to rely on the OS as little as possible - not just for DirectX, but also for TPM, UEFI, SecureBoot." Please help us with creating following lists:

• Every motherboard with UEFI
• Every motherboard with TPM (support)
• Every GPU supporting Directx 12
• Every x thing that is in the following document by Microsoft

Don't you see how much of (mostly pointless) data it would be? That's why the application should try to detect these features instead of relying on some hardcoded data sheets.

No need to be mean

CPU TPM support
and
GPU DirectX support

can be done, and will continue to keep WhyNotWin11 as one of the most accurate tools outside of Microsoft's, currently unavailable, own, but they're not a priority

from whynotwin11.

I'm not mean. Microsoft's official tool only supports Windows 10 and these problems could easily be resolved if WNW11 also supported only Win10. For Windows 7 there is unsupported warning, so why not add the same for Windows 8.1 for DirectX +WDDM2 detection?

from whynotwin11.

Every motherboard with UEFI

Can be determined by the chipset or by CPU model.

Every motherboard with TPM (support)

Not counting headers for dedicated TPM modules, this can be determined by CPU generations.

Every GPU supporting Directx 12

Needs to be checked against a full list when OS is not DX12-capable, there's no way around this, it seems.

Every x thing that is in the following document by Microsoft

Most of these are requirements set by MS for OEMs to ship their devices with Windows 11, and not actual requirements for the OS.

That's why the application should try to detect these features instead of relying on some hardcoded data sheets.

MS tried that with the official tool, and failed miserably. What's the point in doing pretty much the same thing again with this app?

Microsoft's official tool only supports Windows 10 and these problems could easily be resolved if WNW11 also supported only Win10. For Windows 7 there is unsupported warning, so why not add the same for Windows 8.1 for DirectX +WDDM2 detection?

So you're saying that an app which verifies whether or not a PC meets system requirements for Windows 11, should have its own strict system requirements? Do you see the irony here? "Make sure that your PC meets system requirements before you can check if it meets system requirements."

Support should be expanded, not dropped. Actually, I'm pretty sure that there are more people who would want to run this app on Windows 7 than on 8.1.

from whynotwin11.

I may just need to create a database of DX12 cards for "enhanced" detection.

Or somehow use GPU-Z. I don't know if this program is open source and/or if they have API's to use. I wouldn't recommend reinventing the wheel. Clearly they found a workaround and/or already have a database/list of GPU's who support what and whatnot. My advice is to email them and maybe work together on this particular thing. See: https://www.techpowerup.com/contact/

from whynotwin11.

I do see that GPU-Z has a command line parameter to dump the results to an XML file. Obviously that can be parsed to get the DirectX version. What is the feasibility of incorporating something like that vs figuring out how that info is obtained using autoit?

from whynotwin11.

This appears to be a problem for me, too ... on a Lenovo Thinkpad P53 with Xeon running Windows 10. DXDiag claims I have DX12, and the display tabs claim WDDM 2.7 for both the Intel HD Graphics P630 and NVIDIA Quadro M2200 GPUs.

Yet, whynotwin11 shows a big red X for "DirectX + WDDM2".

I'm attaching my dxdiag and CPU-Z dumps.

Is the Windows 11 incompatibility real??

Thanks for taking this on!

DxDiag.txt

MKYLE.txt

from whynotwin11.

This appears to be a problem for me, too ... on a Lenovo Thinkpad P53 with Xeon running Windows 10. DXDiag claims I have DX12, and the display tabs claim WDDM 2.7 for both the Intel HD Graphics P630 and NVIDIA Quadro M2200 GPUs.

Yet, whynotwin11 shows a big red X for "DirectX + WDDM2".

I'm attaching my dxdiag and CPU-Z dumps.

Is the Windows 11 incompatibility real??

Thanks for taking this on!

DxDiag.txt

MKYLE.txt

I see this happen a lot with devices with multiple graphics, generally laptops.

I do see that your DXDIAG is reporting that there is a Displaylink USB device. Maybe a USB to Display adapter or a docking station that states WDDM 1.3. This may be throwing off the reporting. If you disconnect that device and re-run the application, does the issue resolve?

from whynotwin11.

from whynotwin11.

Or somehow use GPU-Z. I don't know if this program is open source and/or if they have API's to use. I wouldn't recommend reinventing the wheel. Clearly they found a workaround and/or already have a database/list of GPU's who support what and whatnot. My advice is to email them and maybe work together on this particular thing. See: https://www.techpowerup.com/contact/

This may be possible. From: https://www.techpowerup.com/gpuz/

GPU-Z is free to use for personal and commercial usage. However, you may not redistribute GPU-Z as part of a commercial package.
We also offer a GPU-Z SDK, which is provided as simple-to-use DLL with full feature set. Commercial support and customization options are available, please contact us for details.

from whynotwin11.