From e9e09497179bbff03ed93739a6ff84715cf24478 Mon Sep 17 00:00:00 2001
From: Blisto91 <47954800+Blisto91@users.noreply.github.com>
Date: Mon, 29 May 2023 22:56:04 +0200
Subject: [PATCH] [meta] Clarify readme setup instructions

---
 README.md | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 8e3f4a43..3f50ccbc 100644
--- a/README.md
+++ b/README.md
@@ -9,20 +9,29 @@ The most recent development builds can be found [here](https://github.com/doitsu
 Release builds can be found [here](https://github.com/doitsujin/dxvk/releases).
 
 ## How to use
-In order to install a DXVK package obtained from the [release](https://github.com/doitsujin/dxvk/releases) page into a given wine prefix, copy or symlink the DLLs into the following directories as follows, then open `winecfg` and manually add DLL overrides for `d3d11`, `d3d10core`, `dxgi`, and `d3d9`:
+In order to install a DXVK package obtained from the [release](https://github.com/doitsujin/dxvk/releases) page into a given wine prefix, copy or symlink the DLLs into the following directories as follows, then open `winecfg` and manually add DLL overrides for `d3d11`, `d3d10core`, `dxgi`, and `d3d9`.
+
+In a default Wine prefix that would be as follows:
 ```
-WINEPREFIX=/path/to/wineprefix
+export WINEPREFIX=/path/to/wineprefix
 cp x64/*.dll $WINEPREFIX/drive_c/windows/system32
 cp x32/*.dll $WINEPREFIX/drive_c/windows/syswow64
 winecfg
 ```
 
-Note that this is **not** an error, 64-bit DLLs are indeed supposed to go to the `system32` directory. Please refrain from opening issues or pull requests to change that, the instructions are correct as they are.
+For a pure 32-bit Wine prefix (non default) the 32-bit DLLs instead go to the `system32` directory:
+```
+export WINEPREFIX=/path/to/wineprefix
+cp x32/*.dll $WINEPREFIX/drive_c/windows/system32
+winecfg
+```
 
 Verify that your application uses DXVK instead of wined3d by by enabling the HUD (see notes below).
 
 In order to remove DXVK from a prefix, remove the DLLs and DLL overrides, and run `wineboot -u` to restore the original DLL files.
 
+Tools such as Steam Play, Lutris, Bottles, Heroic Launcher, etc will automatically handle setup of dxvk on their own when enabled.
+
 ## Build instructions
 
 In order to pull in all submodules that are needed for building, clone the repository using the following command: