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

[d3d10] Stalker Clear Sky dx10 mode msaa bugged #4480

Closed
Blisto91 opened this issue Nov 20, 2024 · 2 comments
Closed

[d3d10] Stalker Clear Sky dx10 mode msaa bugged #4480

Blisto91 opened this issue Nov 20, 2024 · 2 comments

Comments

@Blisto91
Copy link
Contributor

Blisto91 commented Nov 20, 2024 •
edited
Loading

In Stalker Clear Sky using the dx10 mode if you turn on Anti Aliasing (msaa) the main menu, and ingame i gather, can become fully garbled up.

Screenshot

image

Software information

S.T.A.L.K.E.R.: Clear Sky
dx10 mode with AA turned on

System information

  • GPU: RTX 4080
  • Driver: 565.57.01
  • Wine version: Proton Bleeding Edge
  • DXVK version: Tested 1.0 to master

Apitrace file(s)

https://drive.proton.me/urls/V0S952F3R8#JqRQnM7x2dpA
Reproduces the issue

Log files

xrEngine_d3d11.log
xrEngine_dxgi.log
@Blisto91 Blisto91 changed the title [d3d11] Stalker Clear Sky dx10 mode msaa bugged [d3d10] Stalker Clear Sky dx10 mode msaa bugged Nov 20, 2024
@Blisto91
Copy link
Contributor Author

I gather from @doitsujin that this is actually a game bug that doesn't have quite as drastic outcome on AMD. Disabling msaa entirely for the game is likely not wanted because it might sorta kinda work on AMD. Maybe kinda perhaps.

@doitsujin
Copy link
Owner

doitsujin commented Nov 20, 2024 •
edited
Loading 

VUID-RuntimeSpirv-samples-08725(ERROR / SPEC): msgNum: -1917995058 - Validation Error: [ VUID-RuntimeSpirv-samples-08725 ] Object 0: handle = 0xfe711100000001df, type = VK_OBJECT_TYPE_DESCRIPTOR_SET; | MessageID = 0x8dadb7ce | vkCmdDrawIndexed():  the descriptor VkDescriptorSet 0xfe711100000001df[] [Set 0, Binding 2, Index 0, variable "t1"] has image created with VK_SAMPLE_COUNT_4_BIT. The Vulkan spec states: If an OpTypeImage has an MS operand 0, its bound image must have been created with VkImageCreateInfo::samples as VK_SAMPLE_COUNT_1_BIT (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-RuntimeSpirv-samples-08725)

Yeah, the usual game bug where a multisampled texture is bound for sampling, which is UB in d3d10/11 and highly annoying to work around.

@Blisto91 Blisto91 mentioned this issue Mar 4, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@doitsujin @Blisto91