forked from doitsujin/dxvk
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Upstream: D3D8 fixes that should be applied to D3D9 or DXSO too #44
Labels
upstream
Related to upstream or D3D9 issues, PRs, and code.
Comments
AlpyneDreams
added
the
upstream
Related to upstream or D3D9 issues, PRs, and code.
label
Nov 6, 2022
#68 - AL16, R16, L16, AR16 |
AlpyneDreams
changed the title
D3D8 fixes that should be applied to D3D9 or DXSO too
Upstream: D3D8 fixes that should be applied to D3D9 or DXSO too
Mar 4, 2023
The trace included with doitsujin#2184 seems to suggest that is the case, albeit I expect most d3d9 games to behave properly and not rely on it. |
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's possible some of the fixes in d8vk are accounting for weird behavior in d9vk / dxso but not D3D9. There may be a couple of these as D3D9 also supports vs1.1 and ps1.4.
See #43 for one possible example. D3D9 docs state that replicate swizzle should be used but DXSO seems to allow arbitrary swizzles, which may either be fixing games or breaking them.
The text was updated successfully, but these errors were encountered: