Affinity Wine DocumentationAffinity Wine Documentation
Guide
Contributing
  • To-Do
  • License
  • Analytics
Source
Guide
Contributing
  • To-Do
  • License
  • Analytics
Source
  • Guide
    • Introduction
    • Compiling Wine
    • Wineprefix Setup
    • See also
  • Q&A
  • Troubleshooting

Q&A

This section provides background information on the guide. For bug fixes and similar issues, refer to the Troubleshooting page.

Q: Why Use rum Instead of Bottles?

I chose rum over Bottles because the Bottles installation of dotnet48 in the original guide was incomplete, specifically missing some crucial registry keys. This incomplete installation prevents Affinity from being installed and used properly, as it fails to recognize that dotnet is installed due to the missing registry keys.

Click here if you deeply prefer Bottles over rum

To use Bottles instead of rum, you need to add the compiled Wine build as a "runner" in Bottles to this directory:

[...]/bottles/runners/affinity-photo3-wine9.13-part3

Bottles' user files path can be either:

  • $HOME/.local/share/bottles/ if installed natively, or
  • $HOME/.var/app/com.usebottles.bottles/ if installed via Flatpak.

Next, create a new custom Bottle using the added runner before installing dotnet48. You can install dotnet48 either manually or using winetricks:

WINEPREFIX=[...]/bottles/bottles/[bottle-name] winetricks dotnet48 corefonts

Fonts can alternatively be installed using the allfonts dependency from Bottles instead of winetricks' corefonts.

Finally, set the "Windows Version" back to win10 directly from your Bottle settings.

Q: Do I Really Need rum?

Look at how rum works, if you understand what you're reading and you believe you can work without it, go ahead! :​)

Edit this page on Codeberg
Last Updated:
Contributors: wanesty