Skip to content
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.

Sign up for GitHub

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

Jump to bottom

x64 and x86 not giving same DirectX result #311

Closed
IvanAclu opened this issue Jul 1, 2021 · 8 comments
Closed

x64 and x86 not giving same DirectX result #311

IvanAclu opened this issue Jul 1, 2021 · 8 comments
Labels
checks Check improvement or new check. duplicate This issue or pull request already exists external cause A program other than WhyNotWin11 causes the issue help wanted Extra attention is needed question Further information is requested

Comments

@IvanAclu
Copy link

IvanAclu commented Jul 1, 2021

Issue (#270) was closed because the interim build that I tested gave the same result for both executables.
Version 2.3.0.3 reverts to the same behaviour as 2.3.0.1

x64 displays, "DirectX 12 & WDDM 2".
x86 displays, "No DirectX 12, but WDDM 2".

I wonder if there may be an issue when the PC has more than 1 graphics card?
@micwoj92 micwoj92 added bug Something isn't working help wanted Extra attention is needed labels Jul 1, 2021
@micwoj92
Copy link
Collaborator

micwoj92 commented Jul 1, 2021

I wonder if there may be an issue when the PC has more than 1 graphics card?

As Robert said in closing comment "I'm not sure if there's some sort of display switching enabled causing the card to not report currently, but as soon as that card reports it's versioning you'll get a pass on WhyNotWin11"

@rcmaehl rcmaehl added the question Further information is requested label Jul 2, 2021
@micwoj92
Copy link
Collaborator

micwoj92 commented Jul 2, 2021 •
edited
Loading

@rcmaehl
image

64 bit on left, 32 on right.

@micwoj92
Copy link
Collaborator

micwoj92 commented Jul 2, 2021

intel igpu reports same on both versions

@rcmaehl
Copy link
Owner

rcmaehl commented Jul 2, 2021

I'm going to assume this is an issue with running a non-native version of dxdiag. I'll add in a warning about this issue but I don't think I can fix this

@micwoj92
Copy link
Collaborator

micwoj92 commented Jul 2, 2021

Also I've read a bit and it seems like WDDM2+ requires DX12, so couldn't it be hardcoced to pass both then? If you have wddm 2 then you also should have dx 12.

@rcmaehl
Copy link
Owner

rcmaehl commented Jul 2, 2021

If you can provide a link so I could verify that it'd be appreciated. Would make things simpler

@micwoj92
Copy link
Collaborator

micwoj92 commented Jul 2, 2021

Actually it seems other way around?
https://github.com/MicrosoftDocs/windows-driver-docs/blob/119a8f0435127a41cd215063200f67cd6eb51ed1/windows-driver-docs-pr/display/what-s-new-for-prior-wddm-2-x-versions.md#wddm-21

I fucking hate tech news sites man....

@rcmaehl rcmaehl added external cause A program other than WhyNotWin11 causes the issue checks Check improvement or new check. and removed bug Something isn't working labels Jul 5, 2021
@micwoj92
Copy link
Collaborator

micwoj92 commented Oct 5, 2021

Closing this as a duplicate of #58. Because once it is resolved then this issue is also fixed.

@micwoj92 micwoj92 closed this as completed Oct 5, 2021
@micwoj92 micwoj92 added the duplicate This issue or pull request already exists label Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
checks Check improvement or new check. duplicate This issue or pull request already exists external cause A program other than WhyNotWin11 causes the issue help wanted Extra attention is needed question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rcmaehl @micwoj92 @IvanAclu