Frequently Asked Questions (FAQ)

Frequently Asked Questions (FAQ)

Q: Why LTO is not applied in LLVM and GCC builds?

A: Reasons:

1. In order to use any DXVK build with LTO on Linux/Mac, Wine must be compiled with LTO - specifcally, at least wine/libwinecrt0.a.

2. Static libraries built with clang LTO or LTO-thin are not understandable by GCC and vice versa: static libraries built by GCC with LTO are not understandable by clang.

3. State of LTO implementation in GCC leaves much to be desired.

Q: Why GPL is disabled by default?

A: Reasons:

1. This feature is replaced by Async, which does not require any specific driver/extension support and provides better performance than using DXVK with GPL or using DXVK only with state cache.

2. Use of GPL leads to prolonged periods of very high CPU utilization and decreases GPU-bound performance in some cases.

3. Use of GPL significantly increases VRAM/RAM usage and since many Vulkan Drivers on Linux do not have effective memory management mechanisims and do not implement VK_EXT_pageable_device_local_memory, using GPL decreases GPU-bound performance in VRAM-limited and VRAM/PCIe bandwidth-limited situations.

4. Use of GPL requires proper implementation of VK_EXT_graphics_pipeline_library extension which is not available on all devices/drivers.

Note: GPL is disabled by default since 2.6.1-4. GPL still can be enabled by setting dxvk.enableGraphicsPipelineLibrary = True in dxvk.conf.