Differences

This shows you the differences between two versions of the page.

--- systems:bottles [2023/10/08 02:03] – created atari
+++ systems:bottles [2024/08/22 07:36] (current) – note about unintegration made more obvious atari
@@ Line 1: / Line 1: @@
 ====== Bottles ======
-//[[https://usebottles.com/|Bottles]]// is a virtual application/gaming platform for setting up preconfigured environments to support a large set of Windows applications/games on Linux. In other words: //Bottles// gives you the possibility to run almost any Windows application/game on Linux with currently much better compatibility than Batocera's [[systems:windows|native WINE implementation]]. Chances are high that you will be able to run any Windows game not running on the native Batocera WINE implementation. Nevertheless, be aware that //Bottles// is not officially supported by Batocera developers, which means in case of problems you "only" have the unofficial troubleshooting support of the Batocera community (mostly via [[https://discord.com/invite/ndyUKA5|Discord]]).
+<WRAP center round important>
+The bottles flatpak is not officially integrated. This wiki page's instructions may not work for all situations and Batocera cannot provide support help for it, use at your own discretion. If wanting to play Windows games, [[:systems:windows|WINE]] and [[:systems:steam|Steam]] are available.
+</WRAP>
+[[https://usebottles.com/|Bottles]] is a virtual application/gaming platform for setting up pre-configured environments to support a large set of Windows applications/games on Linux.
 ===== Installation =====
-On the Batocera main menu press ''Alt+F1'' on your keyboard, then navigate to ''Applications'' → ''flatpak-config'' (if a warning message appears, just confirm by clicking ''OK''). Then, in the searchbar on the top of the screen, search for //Bottles// and install the //Bottles// application by clicking on ''Install'':
+On the Batocera main menu press ''[F1]'' on your keyboard, then navigate to **Applications** -> **flatpak-config** (if a warning message appears, just confirm by clicking **OK**). Then, in the searchbar on the top of the screen, search for //Bottles// and install the //Bottles// application by clicking on **Install**:
 [{{:systems:bottles_01.png?400|"Bottles" installation}}]
-Confirm by clicking on ''Yes'' and wait for the installation process to be finished (click on ''Show details'' if you want to check the installation progress, which can take a couple of minutes).
-As soon as the Installation process has finished, click on ''Close'', then click on ''File'' → ''Close Window''. Now, back on the Batocera main screen, update the gamelist. //Bottles// application should now be available in the ''Ports'' section. If so, you have already successfully installed //Bottles// on your Batocera system!
+Confirm by clicking on **Yes** and wait for the installation process to be finished (click on **Show details** to show the installation progress, which can take a couple of minutes). As soon as the installation process has finished, click on **Close**, then click on **File** -> **Close Window**. Now, back on the Batocera main screen, update the gamelist. The Bottles application should now be available in the Ports section. If so, you have successfully installed Bottles on your Batocera system!
 ===== Preparing the Bottles environment =====
-To keep things abstracted it is recommended to create a new gaming system folder ''/userdata/roms/bottles'' which holds all Windows game data source folders you want to play (you could also keep all your Windows games inside the ''/userdata/roms/windows'' folder if you want to keep things together and be able to use //Bottles// and Batocera's native WINE implementation in parallel for any of your Windows games). To do so launch a [[:access_the_batocera_via_ssh|SSH/Xterm]] session and execute the following command:
+To keep things abstracted it is recommended to create a new gaming system folder ''/userdata/roms/bottles'' to hold all the bottle data. To do so launch a [[:access_the_batocera_via_ssh|SSH/Xterm]] session and execute the following command:
 <code>mkdir -p /userdata/roms/bottles</code>
-The according ''/userdata/roms/bottles'' folder has now being created. Now you have to make sure that //Bottles// has access to the ''/userdata'' folder and all of its subfolders because it obviously needs access to the according game files. Do so by executing the following command:
+The according ''/userdata/roms/bottles'' folder has now being created. Grant Bottles access to the ''/userdata'' folder and all of its subfolders:
 <code>flatpak override com.usebottles.bottles --filesystem=/userdata</code>
 ===== Setting up a game (example) =====
-The following example will cover the game [[https://store.steampowered.com/app/2022910/Twin_Cobra/|Twin Cobra]]: \\ First of all, [[:add_games_bios|copy]] the game's main source data folder to ''/userdata/roms/bottles''. Then start //Bottles// via the Batocera ''Ports'' system section:
+The following example will cover the game [[https://store.steampowered.com/app/2022910/Twin_Cobra/|Twin Cobra]].
+[[:add_games_bios|Copy]] the game's main source data folder to ''/userdata/roms/bottles''. Then start //Bottles// via the Batocera ''Ports'' system section:
 [{{:systems:bottles_02.png?200|Start "Bottles"}}]
-Navigate through the initial //Welcome to Bottles// screen (don't close it!). Then, on the according last screen, confirm by clicking on the ''Continue'' button and then on ''Start using Bottles'' (the initial setup can take a couple of minutes, this step only has to be done once after a fresh //Bottles// installation).
+Navigate through the initial //Welcome to Bottles// screen (don't close it!). Then, on the last screen, confirm by clicking on the **Continue** button and then on **Start using Bottles** (the initial setup can take a couple of minutes, this step only has to be done once after a fresh Bottles installation).
 First of all, additionally to the bottle runners already installed by default, you should add the most common and most compatible one(s) as follows:
 From the //Bottles// main menu click on the "Hamburger" icon:
 [{{:systems:bottles_03.png?300|"Hamburger" icon}}]
 Click on ''Preferences'' and navigate to ''Runners''. From there click on ''Proton GE'' which opens a dropdown menu. Select the most recent one from the top of the list (currently ''ge-proton8-16'') by clicking on the download icon (''Download & Install''):
 [{{:systems:bottles_04.png?400|Install additional runner(s)}}]
 It can take a couple of minutes for an additional runner to install, just wait for it to finish installing.
-Now close the ''Runners'' window which brings you back to the main //Bottles// menu.
-From there, on the left upper corner, create a new bottle by clicking on the ''+'' symbol:
+Now close the ''Runners'' window which brings you back to the main //Bottles// menu.
+From there, on the left upper corner, create a new bottle by clicking on the **+** symbol:
 [{{:systems:bottles_05.png?300|Create a new bottle}}]
-In the ''Name'' input field give the bottle a meaningful custom name by inserting the game's name (''TwinCobra'' in this case). For the ''Environment'' section select the ''Gaming'' radio button (which will set up an optimized gaming environment bottle automatically) and then click on ''Create'' (don't worry, you can change the according runner later):
+In the //Name// input field give the bottle a meaningful custom name by inserting the game's name ("TwinCobra" in this case). For the //Environment// section select the **Gaming** radio button (which will set up an optimized gaming environment bottle automatically) and then click on **Create** (the runner can be changed later):
 [{{:systems:bottles_06.png?300|Initial bottle settings}}]
-Wait for the bottle to be set up which can take a couple of minutes.
-Confirm the success message by clicking on ''Close''.
+Wait for the bottle to be set up which can take a couple of minutes. Confirm the success message by clicking on **Close**. Navigate to **Bottles** on the top register card menu. From there you can see all available bottle(s) you have created, in this case the one you have just created:
-Navigate to ''Bottles'' on the top register card menu. From there you can see all available bottle(s) you have created, in this case the one you have just created:
 [{{:systems:bottles_07.png?500|Bottle}}]
-Click on the bottle, which will open up the bottle's settings menu.
-From there you can do a lot of stuff to customize the according bottle. We will only cover the most common settings here as every game potentially needs its own settings to run successfully and optimized.
+Click on the bottle, which will open up the bottle's settings menu. From there you can do a lot of stuff to customize the according bottle. We will only cover the most common settings here as every game potentially needs its own settings to run successfully and optimized. First of all let's take on look on how you can change the according bottle runner:
-First of all let's take on look on how you can change the according bottle runner:
-Click on ''Runner'' and from the appearing dropdown menu select the according //ge-proton// runner you have just installed previously (Sidenote: This is just an example on how to install/change a bottle runner. For the specific game //Twin Cobra// leave the runner on ''soda'' as ''ge-proton'' will currently not work for //Twin Cobra//!):
+Click on **Runner** and from the appearing drop-down menu select the according //ge-proton// runner you have just installed previously (Sidenote: This is just an example on how to install/change a bottle runner. For the specific game //Twin Cobra// leave the runner on ''soda'' as ''ge-proton'' will currently not work for //Twin Cobra//!):
 [{{:systems:bottles_08.png?400|ge-proton runner}}]
-Wait for the runner to be changed which can take a couple of seconds.
-Scroll down to the ''Compatibility'' section and click on ''Working Directory''. From the newly opened window click on ''+ Other Locations'' and navigate to the according game's main folder, then click on ''Open'':
+Wait for the runner to be changed which can take a couple of seconds. Scroll down to the //Compatibility// section and click on **Working Directory**. From the newly opened window click on **+ Other Locations** and navigate to the according game's main folder, then click on **Open**:
 [{{:systems:bottles_09.png?400|Working directory}}]
-Now scroll up to the top and on the top left corner click on the back arrow symbol (''Go Back''), which brings you back to the main bottle screen. From there click on ''Add Shortcuts...'', navigate to your game's main folder where the according game's executable file (''<myGame>.exe'') is located, highlight the according game's executable file and click on ''Add'':
+Now scroll up to the top and on the top left corner click on the back arrow symbol (**Go Back**), which brings you back to the main bottle screen. From there click on **Add Shortcuts...**, navigate to your game's main folder where the according game's executable file (''<myGame>.exe'') is located, highlight the according game's executable file and click on **Add**:
 [{{:systems:bottles_10.png?400|Executable (.exe) file}}]
 Now, for later automation reasons, you have to remember two things:
   * There is the bottle's unique **main name** being shown on top of the main bottle menu screen.
-  * There is the bottle's unique **executable name** being shown under the ''Programs'' section (This is due to you can have multiple executables per bottle which in theory gives you the possibility to install multiple games within a single bottle, but for abstraction and compatibility/dependency reasons it is strongly recommended to set up an unique bottle per game (you have been warned!).):
+  * There is the bottle's unique **executable name** being shown under the //Programs// section (This is due to you can have multiple executables per bottle which in theory gives you the possibility to install multiple games within a single bottle, but for abstraction and compatibility/dependency reasons it is strongly recommended to set up an unique bottle per game).
 [{{:systems:bottles_11.png?400|Bottle's name and game's executable name}}]
-Keeping the bottle's name and the game's executable name in mind, let's now do the automation part which lets you start the bottle's according executable with just a single click like usually in every other gaming system in Batocera:
+Keeping the bottle's name and the game's executable name in mind, let's now do the automation part which lets you start the bottle's according executable with just a single click like usually in every other gaming system in Batocera.
 Via [[:access_the_batocera_via_ssh|SSH/Xterm]] create an according start script file by executing the following command:
 <code>nano /userdata/roms/bottles/<myGame>.sh</code>
 Paste the following content (adjust the according ''<myBottleMainName>'' and ''<myBottleExecutableName>'' variables with the according values according to your setup:
 <code>
 #!/bin/bash
@@ Line 60: / Line 94: @@
 chown -R root:audio /var/run/pulse
 chmod -R g+rwX /var/run/pulse
-su - batocera -c "DISPLAY=:0.0 flatpak run --command=bottles-cli com.usebottles.bottles run -b '<myBottleMainName>' -p '<myBottleExecutableName>'"
+su - batocera -c "DISPLAY=:0.0 flatpak run --command=bottles-cli com.usebottles.bottles run -b '<myBottleMainName>' -p '<myBottleExecutableName>' --args-replace"
 </code>
 Here's an example for the game ''Twin Cobra'':
-[{{:systems:bottles_12.png|Start script example}}]
-Save the file and quit the editor.
+[{{:systems:bottles_12.png?1000|Start script example}}]
-Now make the according start script executable by executing the following command (replace ''<myGame>'' with the according game name (avoid spaces if possible)):
+Save the file and quit the editor. Now make the according start script executable by executing the following command (replace ''<myGame>'' with the according game name (avoid spaces if possible)):
 <code>chmod +x /userdata/roms/bottles/<myGame>.sh</code>
 Now symlink the according start script to your ''/userdata/roms/ports'' folder by executing the following command (replace ''<myGame>'' with the according game name (avoid spaces if possible)):
 <code>ln -s /userdata/roms/bottles/<myGame>.sh /userdata/roms/ports/<myGame>.sh</code>
 Now, from the Batocera main screen, update the gamelist. The according game's start script you've just created should now appear in the ''Ports'' system section:
 [{{:systems:bottles_13.png?400|Ports}}]
 You can now start the according game like every other game in Batocera.
 **Optional:** Feel free to add the according ''/userdata/roms/bottles/videos'' and ''/userdata/roms/bottles/images'' folders manually via [[:access_the_batocera_via_ssh|SSH/Xterm]] to add the according media data per game afterwards. You can create those folders by executing the following command:
 <code>mkdir -p /userdata/roms/bottles/videos /userdata/roms/bottles/images</code>
-**Optional:** If for the future you want to keep in mind which games are set up by //Bottles//, you can add a ''[Bottles]'' tag to the according games by renaming them via ES as follows: \\ Highlight the according game → long-press the "Enter" key on the keyboard → Select ''EDIT THIS GAME'S METADATA'' → Select ''Name'' → Add a ''[Bottles]'' tag to the game's name:
+**Optional:** If for the future you want to keep in mind which games are set up by //Bottles//, you can add a ''[Bottles]'' tag to the according games by renaming them via ES as follows: \\ Highlight the according game -> long-press the ''[Enter]'' key on the keyboard -> **EDIT THIS GAME'S METADATA** -> Select **Name** -> Add a ''[Bottles]'' tag to the game's name:
- [{{:systems:bottles_15.png?400|"[Bottles]" tag}}]
+[{{:systems:bottles_15.png?400|"[Bottles]" tag}}]
 This way the according games will appear with an additional ''[Bottles]'' tag on the ''Ports'' section:
 [{{:systems:bottles_16.png?300|"[Bottles]" tag}}]
@@ Line 85: / Line 130: @@
 ==== Game not starting ====
-As always, when a game does not start as expected, this can have multiple reasons. From experience it can be said that the most common problems for games failing to run via //Bottles// is due to missing dependencies (see below on how to install dependencies), wrong bottle runners (see tutorial step //Setting up a game (example)// above on how to install/change a bottle runner), and/or wrong CPU synchronization settings. \\
+As always, when a game does not start as expected, this can have multiple reasons. From experience it can be said that the most common problems for games failing to run via //Bottles// is due to missing dependencies (see below on how to install dependencies), wrong bottle runners (see tutorial step //Setting up a game (example)// above on how to install/change a bottle runner), and/or wrong CPU synchronization settings.
-For changing CPU synchronization settings, open the according bottle and then navigate to: \\
-''Options'' → ''Settings'' → ''Performance'' → ''Synchronization'': \\ Changing this setting from ''Esync'' (default) to ''Fsync'' often resolves the problem of games not starting as expected. \\
+For changing CPU synchronization settings, open the according bottle and then navigate to:
+**Options** -> **Settings** -> **Performance** -> **Synchronization**:
+Changing this setting from ''Esync'' (default) to ''Fsync'' often resolves the problem of games not starting as expected.
 You can also have a look into the main Batocera [[:troubleshooting|logfiles]] which may be helpful sometimes too.
 ==== Dependencies ====
-If you know or you want to try which additional dependencies (e.g. //Microsoft Visual C++ Redistributable// (vcrun), //.NET//, etc.) your game needs to run, you can add/remove those dependencies as follows: \\
+If you know or you want to try which additional dependencies (e.g. //Microsoft Visual C++ Redistributable// (vcrun), //.NET//, etc.) your game needs to run, you can add/remove those dependencies as follows:
-Open the according bottle and then navigate to: \\
-''Options'' → ''Dependencies'' \\
+Open the according bottle and then navigate to:
+**Options** -> **Dependencies**
 From here you can add/remove any dependencies listed.
 ==== Controller issues ====
-Open the according bottle and then navigate to: \\
+Open the according bottle and then navigate to:
-''Tools'' → ''Legacy Wine Tools'' → ''Control panel'' \\
-From there you can check the ''dinput'' and/or ''xinput'' controllers being recognized by //Bottles// (Beware: This option is only available if the according chosen runner for your bottle supports this setting (e.g. //ge-proton//).
+**Tools** -> **Legacy Wine Tools** -> **Control panel**
+From there check the ''dinput'' and/or ''xinput'' controllers being recognized by //Bottles//. This option is only available if the according chosen runner for your bottle supports this setting (e.g. //ge-proton//).
 ==== Map hotkeys to quit bottle games ====
 If you want to map the hotkey-combo keys to the according game to quit the according game as for other Batocera gaming systems, you can do so by creating an according ''.keys'' file as follows by executing:
 <code>nano /userdata/roms/ports/<myGame>.sh.keys</code>
-Paste the following content:
+Paste in the following content:
 <code>
 {
@@ Line 124: / Line 181: @@
 }
 </code>
-Save the file and quit the editor. \\
-If you need the same for the //Bottles// application itself, this can be done by creating the following file with the same content as described above: \\
+Save the file and quit the editor.
+If you need the same for the //Bottles// application itself, this can be done by creating the following file with the same content as described above:
 ''/userdata/roms/flatpak/Bottles.flatpak.keys''
+==== Bottle prefix location ====
+If for whatever reason you need it, you can find the prefix location for your specific bottle here:
+''/userdata/saves/flatpak/data/.var/app/com.usebottles.bottles/data/bottles/bottles''