For our future reference.
Yes, DXVK baseline requirements do shift upward over time as the project evolves.
Major DXVK updates periodically drop legacy hardware extensions in favor of newer Vulkan specifications. For instance, upstream DXVK development has already begun transitioning its baseline expectations toward Vulkan 1.4 features.
What This Means for Your Detection Logic:
If a future DXVK release officially bump its baseline requirement from Vulkan 1.3 to Vulkan 1.4:
Hardware with Vulkan 1.3 only: Installing that hypothetical future DXVK build on a Vulkan 1.3 system would cause it to fail or crash because the driver lacks the newer Vulkan 1.4 extensions.
Updating the script threshold: If DXVK ever updates its hard dependency to 1.4, you would simply update the threshold in your script's awk math from minor >= 3 to minor >= 4:
B4X:
# Example threshold update if DXVK moves to a Vulkan 1.4 requirement:
if [ -n "$VULKAN_VER" ] && echo "$VULKAN_VER" | awk -F. '{ major=$1+0; minor=$2+0; if (major > 1 || (major == 1 && minor >= 4)) exit 0; else exit 1 }'; then
Why your script is future-proof right now:
By structuring your script around dynamic mathematical evaluation (major and minor split) rather than hardcoded text regex, you've ensured that adjusting the target version down the road only ever requires changing
a single digit in your script!
Summary of Requirements:
DXVK 2.x series: Requires a Vulkan 1.3 capable driver.
DXVK 3.x series: Bumps the requirement up to Vulkan 1.4.
DXVK 1.x series (e.g., 1.10.3): Legacy branch, required only Vulkan 1.1.
Currently, running winetricks dxvk will not fetch DXVK 3.x.
winetricks defaults to downloading stable DXVK 2.x releases.
