Difference between revisions of "Vkd3d known issues"

From WineHQ Wiki
Jump to: navigation, search
Line 4: Line 4:
 
|+Known issues
 
|+Known issues
 
|-
 
|-
|Issue
+
!Issue
|Description
+
!Description
|Current implementation
+
!Current implementation
|Possible solutions  
+
!Possible solutions  
 
|-
 
|-
 
|Device memory over-allocation
 
|Device memory over-allocation

Revision as of 14:56, 5 June 2019

Vkd3d is considered as work-in-progress, there are known issues that have to be resolved. Moreover, there are some incompatibilities between Vulkan and Direct3D 12 which are another source of issues.

Known issues
Issue Description Current implementation Possible solutions
Device memory over-allocation Some apps doesn't seem to care much about memory budget and always allocates the same amount of memory. On Windows, it seem that drivers allows allocating more memory than available. In Vulkan, device memory allocations fails quite quickly. This is issue is especially problematic for GPUs with low amount of memory.
NULL descriptors Vulkan doesn't support NULL descriptors. NULL descriptors are currently emulated using dummy resources. Sparse resources are used when residencyNonResidentStrict is supported. The current solution doesn't handle resinfo and bufinfo instructions correctly.