Difference between revisions of "Bottles"
m (→Installation: Add references) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[https://github.com/bottlesdevs/Bottles Bottles] is | [https://github.com/bottlesdevs/Bottles Bottles] is a Wine front-end to easily manage and run Windows games (or other applications) on Linux that don't have [[Lutris]] install scripts. Some people even prefer it for games that do have a script, as Bottles only focuses on Wine. It comes with a nice user interface and has many features like [https://github.com/ishitatsuyuki/LatencyFleX LatencyFleX] integrated, MangoHud and Gamescope support. | ||
== Installation == | |||
Bottles developpers recommend to install it through the official Flatpak (it will come with sandboxing by default)<ref>https://wiki.archlinux.org/title/Bottles#Installation</ref>. Installing drivers<ref>https://github.com/lutris/docs/blob/master/InstallingDrivers.md</ref>, Wine and its optional dependencies<ref>https://www.gloriouseggroll.tv/how-to-get-out-of-wine-dependency-hell/</ref><ref>https://github.com/lutris/docs/blob/master/WineDependencies.md</ref> can also help to run games. | |||
== Usage == | |||
Once installed, you should set up components and create your first bottle<ref>https://docs.usebottles.com/getting-started/first-run</ref>. “Wine prefixes” or “bottles” are basically directories where files used to run your games are stored. The file hierarchy is almost the same as a Windows installation. | |||
To import a custom configuration<ref>https://docs.usebottles.com/bottles/backups</ref>, click the "⋮" button at the top right and choose “Import...”. From there, you can click on the “Configuration” option and choose your YAML configuration file. Once the import has started, cancel the Wine Mono installation if you don't need it, go through installers when prompted and wait for the import to finish. Then, go back to the main menu and into your bottle. Finally, change its settings. | |||
But don’t import a configuration file from the bottle creation menu. It’s broken for now<ref>https://github.com/bottlesdevs/Bottles/issues/2374</ref> as it doesn’t keep some metadata (like bottle name, environment variables or selected runner). Only its dependencies seem to be imported. | |||
== Installing games == | |||
If you need to install dependencies for your apps, note that Bottles doesn’t use Winetricks<ref>https://docs.usebottles.com/faq/where-is-winetricks</ref>. Some of them are missing compared to Winetricks but you can still install them manually. | |||
Once you created your bottle manually or imported a configuration, you can add files to its directory. For archived games, unzip them into under the “drive_c” into the “Program Files” directory or at another location. Then, go back into your bottle settings, add a custom program shortcut<ref>https://docs.usebottles.com/bottles/programs#add-sustom-programs</ref> and a desktop entry<ref>https://docs.usebottles.com/bottles/programs#add-programs-to-your-desktop</ref>. You can also rename the shortcut in Bottles before doing that. For games coming with an installer, just copy the executable inside your bottle path and run it. | |||
Some games might require special tweaks so you should create one bottle per game or engine to avoid conflicts between game configurations. You can also check out [https://appdb.winehq.org/ AppDB] or [https://www.protondb.com/ ProtonDB] and read feedbacks from users. | |||
== File Locations == | |||
The easiest way is to go to your game prefix "Details" page in Bottles, click the "⋮" button and "Browse Files...". It will open the Wine prefix in your file browser. From here, the path is the same as it would be on Windows. | |||
If you want to find it manually, you can find the Wine prefix in <code>~/.var/app/com.usebottles.bottles/data/bottles/bottles/<prefix></code>, where <code><prefix></code> is the name that you gave to the bottle. | |||
== Gamescope support == | |||
Install Gamescope, go into your bottle settings, enable “Gamescope” option in the “Display” section and configure it. Nvidia users will have to enable Direct Rendering Manager kernel mode setting<ref>https://wiki.archlinux.org/title/Gamescope#Requirements</ref> to use it. | |||
== MangoHud support == | |||
Install MangoHud, go into your bottle settings and enable “Monitor Performance” option in the “Performance section”. | |||
Latest revision as of 04:39, 13 May 2025
Bottles is a Wine front-end to easily manage and run Windows games (or other applications) on Linux that don't have Lutris install scripts. Some people even prefer it for games that do have a script, as Bottles only focuses on Wine. It comes with a nice user interface and has many features like LatencyFleX integrated, MangoHud and Gamescope support.
Installation
Bottles developpers recommend to install it through the official Flatpak (it will come with sandboxing by default)[1]. Installing drivers[2], Wine and its optional dependencies[3][4] can also help to run games.
Usage
Once installed, you should set up components and create your first bottle[5]. “Wine prefixes” or “bottles” are basically directories where files used to run your games are stored. The file hierarchy is almost the same as a Windows installation.
To import a custom configuration[6], click the "⋮" button at the top right and choose “Import...”. From there, you can click on the “Configuration” option and choose your YAML configuration file. Once the import has started, cancel the Wine Mono installation if you don't need it, go through installers when prompted and wait for the import to finish. Then, go back to the main menu and into your bottle. Finally, change its settings.
But don’t import a configuration file from the bottle creation menu. It’s broken for now[7] as it doesn’t keep some metadata (like bottle name, environment variables or selected runner). Only its dependencies seem to be imported.
Installing games
If you need to install dependencies for your apps, note that Bottles doesn’t use Winetricks[8]. Some of them are missing compared to Winetricks but you can still install them manually.
Once you created your bottle manually or imported a configuration, you can add files to its directory. For archived games, unzip them into under the “drive_c” into the “Program Files” directory or at another location. Then, go back into your bottle settings, add a custom program shortcut[9] and a desktop entry[10]. You can also rename the shortcut in Bottles before doing that. For games coming with an installer, just copy the executable inside your bottle path and run it.
Some games might require special tweaks so you should create one bottle per game or engine to avoid conflicts between game configurations. You can also check out AppDB or ProtonDB and read feedbacks from users.
File Locations
The easiest way is to go to your game prefix "Details" page in Bottles, click the "⋮" button and "Browse Files...". It will open the Wine prefix in your file browser. From here, the path is the same as it would be on Windows.
If you want to find it manually, you can find the Wine prefix in ~/.var/app/com.usebottles.bottles/data/bottles/bottles/<prefix>, where <prefix> is the name that you gave to the bottle.
Gamescope support
Install Gamescope, go into your bottle settings, enable “Gamescope” option in the “Display” section and configure it. Nvidia users will have to enable Direct Rendering Manager kernel mode setting[11] to use it.
MangoHud support
Install MangoHud, go into your bottle settings and enable “Monitor Performance” option in the “Performance section”.
- ↑ https://wiki.archlinux.org/title/Bottles#Installation
- ↑ https://github.com/lutris/docs/blob/master/InstallingDrivers.md
- ↑ https://www.gloriouseggroll.tv/how-to-get-out-of-wine-dependency-hell/
- ↑ https://github.com/lutris/docs/blob/master/WineDependencies.md
- ↑ https://docs.usebottles.com/getting-started/first-run
- ↑ https://docs.usebottles.com/bottles/backups
- ↑ https://github.com/bottlesdevs/Bottles/issues/2374
- ↑ https://docs.usebottles.com/faq/where-is-winetricks
- ↑ https://docs.usebottles.com/bottles/programs#add-sustom-programs
- ↑ https://docs.usebottles.com/bottles/programs#add-programs-to-your-desktop
- ↑ https://wiki.archlinux.org/title/Gamescope#Requirements