Affinity

https://github.com/seapear/AffinityOnLinux/blob/main/Guides/Lutris/Guide.md for more information.
Official Runner Found here: https://github.com/seapear/AffinityOnLinux/releases/tag/v10.18-staged.

Overview =================================================================
This YAML automates the installation of Affinity Suite on Linux using a portable, custom Wine runner (GameDirectionWine-x86_64, based on Wine 10.18). It sets up all required dependencies, prepares helper folders, and installs the Affinity applications inside a managed Lutris prefix.
=================

1. Runner Requirements
The YAML expects a local Wine runner located at:
~/.local/share/lutris/runners/wine/GameDirectionWine-x86_64/
This should contain the portable Wine 10.18 (Staged) build from:
https://github.com/seapear/AffinityOnLinux/releases/tag/v10.18-staged

Verify that running:
bin/wine64 --version
outputs wine-10.18

If you rename or update the folder, adjust the YAML line:
wine:
version: GameDirectionWine-x86_64
to match your folder name exactly.

2. File Inputs
During installation, Lutris will prompt for or download these files:
setup: Local Affinity Suite installer (select manually)
WinMetadata.zip: https://archive.org/download/win-metadata/WinMetadata.zip
Windows.winmd: https://github.com/microsoft/windows-rs/raw/master/crates/libs/bindgen/default/Windows.winmd
Wintypes_Shim.dll.so: https://github.com/ElementalWarrior/wine-wintypes.dll-for-affinity/raw/refs/heads/master/wintypes_shim.dll.so

You can pre-download these to speed up installation or run offline by placing them beside the YAML file before installing.

3. Directory Structure
The installer will automatically ensure these directories exist:
$GAMEDIR/
└── drive_c/
├── Program Files/
│ └── Affinity/Affinity/
│ ├── Affinity.exe
│ └── Wintypes_Shim.dll.so
└── windows/system32/winmetadata/
├── Windows.winmd
└── (other metadata files)

4. Post-Install Behavior
After the setup completes, Lutris is configured to launch:
/home/$USER/Games/affinity-suite/drive_c/Program Files/Affinity/Affinity/Affinity.exe

If the executable name differs (for example, Designer, Photo, or Publisher), edit the path in the YAML or inside Lutris → Configure → Game Options → Executable.

5. Artwork and Metadata
This YAML includes metadata for icon, banner, and cover art, but Lutris only auto-loads this when installed from lutris.net. For local installs, manually set these once the game appears in your library:
Icon: https://github.com/seapear/AffinityOnLinux/blob/main/Assets/Icons/Affinity-Canva.svg?raw=true
Cover: https://github.com/seapear/AffinityOnLinux/blob/main/Assets/Covers/Affinity-Canva-Cover.png?raw=true
Banner: https://github.com/seapear/AffinityOnLinux/blob/main/Assets/Covers/Affinity-Canva-Banner.png?raw=true

6. Common Adjustments
Different Wine or Proton builds: set wine.version to any installed runner name (for example, lutris-GE-Proton8-26-x86_64).
Offline operation: remove URLs in files: and use “N/A:” prompts so users select local copies.
Testing new builds: replace GameDirectionWine-x86_64 with newer Wine versions or your own portable build.

7. Troubleshooting
Runner not found: ensure folder name matches the version: value exactly.
Missing icons: add ?raw=true to all GitHub image URLs or re-link in Lutris manually.
Affinity fails to launch: re-run the installer, confirm helper files are in the proper directories, and verify your prefix architecture matches win64.