Linux Support: Difference between revisions

From Flashpoint Datahub
Jump to navigation Jump to search
(→‎Docker fix for firewalld users: Improved legibility, fixed wiki formatting and added a couple extra necessary steps)
(→‎Installation: Uploaded hotfix; changed SHA256 sum)
 
(109 intermediate revisions by 6 users not shown)
Line 1: Line 1:
Linux support in Flashpoint is currently experimental due to a lack of maintainers. This page describes the current state of our Linux support. If you need assistance with installing or playing, visit us at #flashpoint-mac-linux-help.
Linux support in Flashpoint is currently experimental due to a lack of maintainers. This page describes the current state of our Linux support. If you need assistance with installing or playing, ask in the <code>help</code> forum on the [https://flashpointarchive.org/discord Discord server].


As it stands, the Docker version of Flashpoint for Linux supports Flash, HTML5, Shockwave, Unity and Java. The exceptions are content that uses the Chromium browser, and Shockwave content that plays in-browser.
Flashpoint for Linux supports Flash, HTML5, Shockwave, Unity, Java and various other web platforms. Not every platform is supported, such as DevalVR and Viscape, because some may rely too heavily on Windows features and can't run through Wine.
If you want support for the other platforms that are Windows-exclusive, there are a few options to get the Windows version of Flashpoint running on Linux:
If you want support for platforms that are Windows-exclusive, there are 2 options:
* [https://bluemaxima.org/flashpoint/downloads/ Download the Windows version of Flashpoint] and run it in a Windows virtual machine. This is the recommended non-native option.
* [https://flashpointarchive.org/downloads Download the Windows version of Flashpoint] and run it in a Windows virtual machine. This is the recommended non-native option.
* [[#Using_Wine|Run the Windows version of Flashpoint with Wine]]. This works well on some computers, but does not work consistently.
* [[#Windows_Version_Using_Wine|Run the Windows version of Flashpoint with Wine]]. This may or may not work well depending on the exact build of Wine used.


Otherwise, download the [https://drive.google.com/file/d/1zgBrmyiMpSfW9xsZ9A4ejvR0lktWlTRR/view?usp=sharing latest Docker Flashpoint package] and [[#Manual Installation|install it]].
Otherwise, if you don't need support for those platforms, you may continue reading through this page.


== Manual Installation ==
== Compatibility ==
Flashpoint for Linux only officially supports the x86_64 architecture and, for compatibility and security reasons, the GNU C Library (glibc). This is because the launcher uses Electron, which doesn't support 32-bit x86 for Linux, and several binaries only have x86_64 + glibc versions. If you want to run Flashpoint on other architectures like ARM or RISC-V, you must use an emulator like [https://github.com/ptitSeb/box64 Box64]. Likewise, for C libraries other than glibc like musl, you must recompile everything you wish to use that's not already packaged, and link them with the desired C library. You may also use a glibc compatibility layer like [https://git.adelielinux.org/adelie/gcompat gcompat] for proprietary binaries, such as the native Flash projector.
 
The main Linux version is built on Debian 11, which uses glibc 2.31, making it the minimum supported version. Flashpoint cannot be built on older Debian versions without significant changes to the launcher, due to some dependencies being incompatible. Any distro that uses glibc 2.31+ should also be supported, including but not limited to:
* Ubuntu 20.04+
* Fedora 32+
* openSUSE Leap 15.3+
* Any distro based on the above, including by proxy
* Any rolling release distro maintained after February 2020
 
If you use a distro older than those listed, you must upgrade to a newer version to run Flashpoint.
 
== Main Version ==
The main version of Flashpoint for Linux contains everything we currently support on Linux, and includes its own libraries and Wine runtime. The libraries are used to run Flashpoint in a known-working container, and the Wine runtime contains the binaries and libraries that the Windows-only programs need to run. These allow us to support as many different distro configurations as possible (including both mutable and immutable ones), and efficiently run non-native programs through the Flashpoint launcher without taking up too much extra space.
 
If you use a mutable distro (i.e. one where the root file system can be modified) and do not want all of the components, you may choose to remove the <code>Libraries</code> and <code>FPSoftware/Wine</code> directories post-install. This will leave you with only the main Flashpoint files, which total about 2 GB. See [[#Dependencies|Dependencies]] for more information.
 
For the best experience, at least 4 GB of free space is recommended on the partition you wish to install Flashpoint to.
 
=== Installation ===
To install Flashpoint, follow these steps:
# Download [https://download.flashpointarchive.org/upload/fp14.0.3_lin_20251201.7z this archive file]. <small>(SHA256: <code>f393a98c5c35e229a744c102b0cb53270b1b4f1b3ebd40d604f98323444a4b1f</code>)</small>
# Extract the contents of the file to an '''empty''' directory that your user has read & write permissions for. This can be done graphically, or in the terminal by entering the following at the file's directory:<pre>7zr x fp*_lin_*.7z -oFlashpoint</pre>
# Open the directory you extracted Flashpoint to, then run <code>setup-desktop-entry.sh</code> to generate a desktop entry that opens the launcher. Alternatively, if you are unable to run desktop entries, run <code>start-flashpoint.sh</code> instead.
 
Once you've done that, Flashpoint is now installed. If you don't want to use the libraries and Wine runtime provided by Flashpoint, see [[#Dependencies|the Dependencies section below]].


=== Dependencies ===
=== Dependencies ===
First, install Flashpoint's dependencies.
'''If you're on an immutable distro, the following does not apply.'''
{| class="wikitable"
 
!colspan="9"|Dependency package names on various distros
If you don't plan on using the libraries and Wine runtime provided, you must first remove them from your Flashpoint install. To do so, delete the <code>Libraries</code> and <code>FPSoftware/Wine</code> subdirectories from the directory you extracted Flashpoint to. Afterwards, you'll need to install the following packages for everything to work properly. A dependency listed with more than one package for a given distro means you can choose any one package from that distro according to your needs.
|-
{|class="wikitable"
!Library/command name
!Distro
!Docker
!X11
!PulseAudio<span style="color:#0000ff">*</span>
!GTK3
!X11<span style="color:#0000ff">**</span>
!XHost
!NSS
!NSS
!PulseAudio
!PHP
!PHP
!bash
!<abbr title="Only required to extract components; not needed for runtime">7-Zip</abbr>
!Wine
!<abbr title="Not required on Fedora 40+ and its derivatives">32-bit Xcomposite</abbr>
!<abbr title="Not required on Fedora 40+ and its derivatives">32-bit LibPulse</abbr>
|-
|-
!Debian-like<span style="color:#0000ff"><small><sup>a</sup></small></span>
!<abbr title="*Ubuntu, Linux Mint, Pop!_OS, Zorin OS, etc.">Debian-like</abbr>
|(see [https://docs.docker.com/engine/install/debian/ this page])
|xserver-xorg-core / xwayland
|pulseaudio
|libgtk-3-0
|xserver-xorg-core
|x11-xserver-utils
|libnss3
|libnss3
|php
|rowspan=2|pulseaudio / pipewire-pulse
|bash
|rowspan=3|php
|rowspan=2|7zip
|([https://gitlab.winehq.org/wine/wine/-/wikis/Debian-Ubuntu link])
|libxcomposite1:i386
|libpulse0:i386
|-
|-
!Ubuntu-like<span style="color:#0000ff"><small><sup>b</sup></small></span>
!<abbr title="EndeavourOS, CachyOS, Garuda Linux, Manjaro, etc.">Arch-like</abbr>
|(see [https://docs.docker.com/engine/install/ubuntu/ this page])
|xorg-server / xorg-xwayland
|pulseaudio
|rowspan=2|gtk3
|xserver-xorg-core
|rowspan=2|nss
|x11-xserver-utils
|rowspan=3|wine
|libnss3
|colspan=2 style="background-color:#bfbfbf;"|<center>N/A</center>
|php
|bash
|-
|-
!Fedora-like
!Fedora-like
|(see [https://docs.docker.com/engine/install/fedora/ this page])
|xorg-x11-server-Xorg / xorg-x11-server-Xwayland
|pulseaudio
|rowspan=2|pulseaudio / pipewire-pulseaudio
|xorg-x11-server-Xorg
|p7zip
|xhost
|libXcomposite.i686
|nss
|pulseaudio-libs.i686
|php
|bash
|-
|-
!Arch-like<span style="color:#0000ff"><small><sup>c</sup></small></span>
!SUSE-like
|docker
|xorg-x11-server / xwayland
|pulseaudio
|libgtk-3-0
|xorg-server
|mozilla-nss
|xorg-xhost
|php7
|nss
|7zip
|php
|libXcomposite1-32bit
|bash
|libpulse0-32bit
|}
|}
<small><span style="color:#0000ff">a</span> : E.g. ChromeOS Terminal, MX Linux | <span style="color:#0000ff">b</span> : E.g. Linux Mint, Pop!_OS, Zorin OS | <span style="color:#0000ff">c</span> : E.g. Manjaro, SteamOS >=3.0</small>


'''Note:''' Chances are that Docker and PHP will be the only packages that you'll need to install, as most distributions come with the rest of the packages already pre-installed.
There are also some packages that aren't required, but can enhance your experience:
{|class="wikitable"
!Distro
!GTK2
!LibXt
|-
!Debian-like
|libgtk2.0-0
|libxt6
|-
!Arch-like
|rowspan=2|gtk2
|libxt
|-
!Fedora-like
|libXt
|-
!SUSE-like
|libgtk-2_0-0
|libXt6
|}
These packages are needed in order to use the native Flash projector, which is not enabled by default due to minor audio delay and performance issues. If you wish to enable it, go to your Flashpoint config, click the "Platforms" dropdown beside the Native Platforms setting and click the checkbox next to "Flash".


<span style="color:#0000ff">*</span> : PipeWire can also be used in place of PulseAudio by installing the <code>pipewire-pulse</code> package on Ubuntu-like and Arch-like distros, or <code>pipewire-pulseaudio</code> on Fedora-like distros. For Debian-like distros, see [https://wiki.debian.org/PipeWire#Using_as_a_substitute_for_PulseAudio.2FJACK.2FALSA this link].
To install any of the dependencies, use your distro's package manager:
 
<span style="color:#0000ff">**</span> : X11 can also be used within Wayland by installing the <code>xwayland</code> package on Debian-like and Ubuntu-like distros, <code>xorg-x11-server-Xwayland</code> on Fedora-like distros, or <code>xorg-xwayland</code> on Arch-like distros.
 
 
To install them, use your distro's package manager:
{|class="wikitable"
{|class="wikitable"
!Distro
!Distro
Line 75: Line 115:
|-
|-
!Debian-like
!Debian-like
|<code>sudo apt-get install {PACKAGE}</code>
|<code>sudo apt-get install $PKG</code>
|-
|-
!Ubuntu-like
!Arch-like
|<code>sudo apt-get install {PACKAGE}</code>
|<code>sudo pacman -S $PKG</code>
|-
|-
!Fedora-like
!Fedora-like
|<code>sudo dnf install {PACKAGE}</code>
|<code>sudo dnf install $PKG</code>
|-
!Fedora-like (old)
|<code>sudo yum install {PACKAGE}</code>
|-
|-
!Arch-like
!SUSE-like
|<code>sudo pacman -S {PACKAGE}</code>
|<code>sudo zypper install $PKG</code>
|}
|}


=== Setup ===
=== ChromeOS Extra Steps ===
Before you start, you need to [https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user configure Docker to be managed by a non-root user]. Once finished, you may have to reboot your computer if the permissions aren't applied properly when trying to run Docker commands as a non-root user.
For ChromeOS users, some additional steps will need to be taken for Flashpoint to run properly. It will be assumed that you already [https://support.google.com/chromebook/answer/9145439 set up a Linux terminal].


If you don't want to add your user to the <code>docker</code> group as above (e.g., for security: doing this allows all programs on your computer to have unrestricted administrator access to everything at all times) then there is an alternative, it just takes a bit more work.
By default, when transferring files from the ChromeOS host to the Debian guest in the terminal, execute permissions are removed from all files. This will prevent everything from running, including the Flashpoint launcher. To fix this, run the following command in the terminal, replacing <code>$DIR</code> with the path to the directory you have Flashpoint installed in:
chmod -R +x $DIR
This command will add execute permissions to all files in the directory recursively. After running it, you can then run <code>$DIR/start-flashpoint.sh</code> to open the launcher.


==== Optional: Configuring non-root Flashpoint ====
=== Nix Shell ===
The main Flashpoint files can also be launched under a Nix shell if Nix is installed:
<pre>{ pkgs ? import <nixpkgs> {} }:


Start by creating a wrapper script for <code>docker</code> that will automatically use <code>sudo</code> when you are not invoking Docker as root. Name it <code>docker</code>, make it executable and place it on your <code>$PATH</code>:
(pkgs.buildFHSEnv {
    name = "flashpoint";
    targetPkgs = pkgs: (with pkgs; [
        # Shell utils
        toybox
        # Electron for the launcher.
        electron
        # Flashpoint requirements
        pipewire pulseaudio
        gtk3 gtk2 nss php wine
        xorg.libX11 xorg.libXt xorg.libXcomposite
        # ldd requirements
        mesa #libgbm
        glib nspr at-spi2-atk cups dbus libdrm pango cairo expat libxkbcommon alsa-lib
        xorg.libXdamage xorg.libXext xorg.libXfixes xorg.libXrandr xorg.libxcb
        udev
    ]);
}).env</pre>
Simply save this code into a .nix file and run it with <code>nix-shell {file}.nix --run ./start-flashpoint.sh</code>.


<pre>
You can also use <code>steam-run</code> (<code>nix-shell -p steam-run --run "steam-run ./start-flashpoint.sh"</code>).
#!/usr/bin/env bash
export PATH="${PATH/$(dirname "$0"):/}"
askpass=()
if [[ -n "${SUDO_ASKPASS:-}" ]]; then
    askpass+=("-A")
fi
if [[ "$OSTYPE" != darwin* ]] && [[ "$EUID" != 0 ]]; then
    exec sudo "${askpass[@]}" -E -- "$0" "$@"
fi
exec docker "$@"
</pre>


Then you need to create an askpass script for <code>sudo</code>. Create a script that will print your sudo password to stdout. For example, my script retrieves my password from my password manager, <code>pass</code>, which will force authentication through a graphical dialog before retrieving the password. Technically you could just hardcode your password in the script, but this would sort of defeat the point of trying to be more secure in the first place.
== Minimal-Dependency Version ==
'''Due to the inherently barebones nature of this option, do not expect to receive help in the Discord if a specific game does not work.'''


Now, you can simply export the <code>SUDO_ASKPASS</code> environment variable to the path of your askpass script (make sure it is executable), make sure that your <code>docker</code> wrapper is on <code>$PATH</code>, and invoke <code>./flashpoint</code> as normal once you get to that step below.
If you are looking for a fully-native or minimal setup Flashpoint experience on Linux, ''Flashpoint Nano'' exists as a lightweight (albeit heavily limited) script-based alternative to the other installation options.


==== Nvidia GPUs ====
Only two platforms are supported: Flash (using [https://ruffle.rs Ruffle]; non-embedded entries only) and HTML5 (using [https://www.palemoon.org Pale Moon]). Each software is Linux-native, downloaded upon first launch and updated automatically.
If you have an Nvidia GPU and use a distro that isn't Arch-like, you will need to add Nvidia's repository and install the <code>nvidia-docker2</code> package. Follow the "Setting up NVIDIA Container Toolkit" instructions under the heading corresponding to your distro [https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html#docker here].


If you use an Arch-like distro, install either [https://aur.archlinux.org/packages/nvidia-container-toolkit <code>nvidia-container-toolkit</code>] or [https://aur.archlinux.org/packages/nvidia-docker <code>nvidia-docker</code>] from the AUR if you did or didn't already install Docker respectively.
=== Dependencies ===
 
Only a few command-line utilities that may not be available on your system by default are required: <code>tar</code>, <code>curl</code>, <code>sqlite3</code>, and <code>unxz</code> (from XZ Utils). You should be able to install these using your distro's package manager.
In both cases, you may have to restart the Docker service or reboot your computer to apply the toolkit.


=== Installation ===
=== Installation ===
Download the [https://drive.google.com/file/d/1zgBrmyiMpSfW9xsZ9A4ejvR0lktWlTRR/view?usp=sharing latest Docker Flashpoint package] if you haven't already and extract it somewhere.
# Download Nano from [https://github.com/WumboSpasm/flashpoint-nano the GitHub repository] by clicking the ''Code'' button and then ''Download ZIP''. Alternatively, if you have git installed, you can use the <code>git clone <nowiki>https://github.com/WumboSpasm/flashpoint-nano.git</nowiki></code> command to download the repository. The latter option may be preferable so you can download updates to the scripts using <code>git pull</code>.
 
# If you downloaded the ZIP archive, extract it using your method of choice.
Go to the place where you extracted it, and pull the docker images by running <code>./pull.sh</code>. They'll take ~3.5 GB.
# Enter the created directory and run the following command in the terminal: <code>./flashpoint.sh <entry-id></code>. You can find the ID of the desired entry using the [https://flashpointproject.github.io/flashpoint-database Flashpoint Database] search tool. If you wish to launch an additional application, simply append its ID to the end of your command (with a space separating it from the entry ID).


Finally, run the <code>./flashpoint</code> executable script to start the launcher.
== Windows Version Using Wine ==
Alternatively, you can attempt to run the Windows version of Flashpoint using Wine, which is a compatibility layer for Windows programs. There are several advantages to doing this, like being able to run more up-to-date versions of Flashpoint that have only been made for Windows. However, it is not guaranteed that Wine will work properly, as the experience varies greatly depending on the hardware, choice of distribution, and packages you have installed. For this to work, you currently need to install either the development or staging versions of Wine running a completely fresh prefix. How to install them depends on the distro, so consult [https://gitlab.winehq.org/wine/wine/-/wikis/Download WineHQ's download page] for instructions on yours. You will also need the <code>php</code> package for Flashpoint to work post-install.


As of now, you can install the latest Windows version of Flashpoint Infinity by running the [https://github.com/FlashpointProject/FlashpointComponentTools/releases/latest/download/FlashpointInstaller.exe installer] through Wine. To be able to run the installer, you need to install a recent version of Wine Mono, which should be provided upon creating a new Wine prefix or installed as a package on most distros. The process for installing Flashpoint this way is similar to how it is on Windows, except you may have to change the installation path to a location that can be written to, like your user directory. An example of a proper installation path would be <code>Z:\home\$USER\Flashpoint</code>, replacing <code>$USER</code> with your username. You may get an error upon finishing the installation; this is expected behavior. Quit the installer and kill it from your process manager if needed, and all of the files should be where you installed them.


Config files can be found in <code>./LinuxConf/</code> and <code>./FPSoftware/FSPConfigs/</code>.
Once done, you can then run <code>Launcher/Flashpoint.exe</code> through Wine and set the "Flashpoint Path" in the launcher's config to <code>..</code>, then click "Save and Restart" on the bottom of the page. If everything has been done correctly, you should now have a working Flashpoint install! If you are having issues running the launcher with Wine, you can instead try using various other "flavors" such as [https://github.com/GloriousEggroll/wine-ge-custom Wine GE], which has extra patches that aren't upstream. Users of Arch-like distros can install Wine GE as a [https://aur.archlinux.org/packages/wine-ge-custom package from the AUR], however no binary is provided, so it must be compiled.
 
Save data is stored in <code>./SaveData</code>. Java save data isn't persistent, because there's no standardized location for it.


== Troubleshooting ==
== Troubleshooting ==
=== Audio Glitches in Wine ===
Some users may experience audio glitches when running programs through Wine, like constant crackling or distortions. If this is happening to you, you may have to switch to a different audio driver. As of writing, Wine currently uses PulseAudio as the default preferred backend, but other backends are available. For example, to enable the ALSA driver, run the following command, replacing <code>$DIR</code> with the full path of the prefix you wish to modify:
WINEPREFIX=$DIR wine reg add 'HKCU\Software\Wine\Drivers' /v Audio /d alsa
To modify the default prefix, don't set WINEPREFIX. For reference, Flashpoint's prefix location relative to the installation directory is <code>FPSoftware/Wine</code>.


=== proxy.sh: "Permission denied" error ===
Switching audio drivers may or may not fix the problem right away. If you are still experiencing glitchy audio, please ask for help in the [https://flashpointarchive.org/discord Discord server].
 
Depending on your system's permissions, the <code>proxy.sh</code> script may throw a "permission denied" error in the launcher logs when launching a game, causing it to fail to start. To fix this, follow these steps:
# Close the Flashpoint launcher.
# Open <code>./LinuxConf/proxy.sh</code> in a text editor.
# Change <code>/var/lock/flashpoint-networking.lock</code> to <code>/tmp/flashpoint-networking.lock</code> and save the file.
# Relaunch Flashpoint.
 
=== cgroup subsystem devices not found: unknown ===
 
This error occurs most frequently on Pop!_OS 22.04, due to an outdated version of the Nvidia container runtime being packaged in the default repositories. If this applies to you, follow these steps:
# Close the Flashpoint launcher and stop the Docker service.
# Remove your current <code>nvidia-docker2</code> package, then remove its dependencies and configuration files by typing <code>sudo apt-get autoremove --purge</code> in the terminal.
# Create a text file in <code>/etc/apt/preferences.d</code> with the following contents:
Package: *
Pin: origin nvidia.github.io
Pin-Priority: 1002
Then save the file, update the package index using <code>sudo apt-get update</code>, reinstall the package, start the Docker service again, and relaunch Flashpoint.
 
=== Docker Fix for firewalld Users ===
 
Users of [https://firewalld.org/ firewalld] may run into issues with Docker when launching games. In this case, follow these steps:
<ol>
<li>
Run <code>sudo systemctl status docker</code> and look for the location of Docker's service file in the output. It is usually <code>/usr/lib/systemd/system/docker.service</code>.
</li>
<li>
Open the file in a text editor with root privileges and change the following line from:
<pre>ExecStart=/usr/bin/dockerd -H fd://</pre>
to:
<pre>ExecStart=/usr/bin/dockerd -H fd:// --ip-tables=false</pre>
</li>
<li>
Restart the Docker service by running <code>sudo systemctl restart docker.service</code>.
</li>
<li>
Run Flashpoint and install the content of your choosing, then close the launcher when finished.
</li>
<li>
Open the Docker service file again and revert the previous change to the line, then restart the Docker service again.
</li>
<li>
Relaunch Flashpoint and run the game again. It should now work.
</li>
</ol>
 
== Using Wine ==
 
Alternatively, you can attempt to run the Windows version of Flashpoint using [https://www.winehq.org/ Wine], which is a Windows compatibility layer. There are several advantages to doing this, like being able to run more up-to-date versions of Flashpoint that have only been made for Windows.
 
However, it is not guaranteed that Wine will work properly, as the experience varies greatly depending on the hardware and choice of distribution. For example, as of the time of writing, distros that use older versions of Wine for stability purposes like Linux Mint and old stable versions of Debian will likely work with the most recent version of Flashpoint. Newer versions like from Arch-based or other rolling-release distros will not work due to an unknown regression causing the launcher to not load correctly.
 
If you are having issues running Flashpoint with Wine, you can instead try using various other "flavors" such as [https://github.com/GloriousEggroll/wine-ge-custom Wine GE], which has extra patches applied that aren't in mainline Wine. Users of Arch-based distros can install Wine GE as a [https://aur.archlinux.org/packages/wine-ge-custom package from the AUR], however no binary is provided, so the package must be compiled.
 
Additionally, as of the time of writing, you will also have to install Wine Mono and the 32-bit (x86) version of the 2015 Visual C++ runtime into your Wine prefix. Wine Mono can be installed upon creating a new prefix or by installing the corresponding package for your distro, while the Visual C++ runtime will have to be manually installed. The easiest method is to use <code>winetricks</code>, which can be installed as a package on most distros. Once installed, you can run the application from your program manager, select the prefix that you want to use with Flashpoint, and then select "Install a Windows DLL or component." In the list that pops up, scroll until you see <code>vcrun2015</code> and select it for installation. You may get a few popups before being greeted with the installer; this is normal behavior.
 
You can also install the runtime directly from the terminal by entering the following:
$ winetricks vcrun2015
Once it's finished installing the runtime, you can close Winetricks and attempt to run Flashpoint through Wine using the prefix you installed everything to.
 
== Technologies ==
 
Flashpoint Infinity, like its Windows counterpart, uses <code>router.php</code> as a proxy server. But unlike Windows, Linux provides native ways to set per-application proxy settings, so no equivalent to the [https://github.com/FlashpointProject/FlashpointProxy Flashpoint Proxy library] is used. On Linux, each application is simply told via environment variables to use <code>localhost:22500</code> as a proxy server. For example, before Flashpoint Launcher opens the Flash projector, it sets the <code>http_proxy</code> environment variable to <code>http://localhost:22500/</code> in the docker container.
 
The [http://bluemaxima.org/flashpoint/faq/ Flashpoint FAQ] contains a list of all web game technologies ("Platforms") supported in the Windows version of Flashpoint. The Linux version currently supports a subset of these platforms. This is explained in detail below.
 
=== Supported Platforms ===
* Flash: Supported through Wine by default. Although a Linux Flash Projector exists, it suffers from graphical glitches on many systems. If you'd like to try your luck with the native projector, then tick it as a 'Native Platform' on the Config page.
* Shockwave: Supported through Wine.
* HTML5: Supported natively through the Basilisk browser.
* Java Applets: Supported natively using the Oracle JDK.
* Unity Web Player: Supported through Pipelight.
 
<noinclude>[[Category:Technologies]]</noinclude>


== Using the standalone projector ==
=== Launcher Sandbox Errors ===
Some users may receive the following error when attempting to run the launcher:
The SUID sandbox helper binary was found, but is not configured correctly.
To fix this, the permissions and owner of the sandbox have to be changed. Open a terminal in the <code>Launcher</code> directory of your Flashpoint install, and run the following:
chmod 4755 chrome-sandbox
sudo chown root:root chrome-sandbox
The first command will allow the owner of the sandbox to read, write and execute it; other users will only be able to read and execute. The second will set the root user and group as the owner of the sandbox. The root group should only contain the root user by default.


If you would like to run your own <code>.swf</code> file that is not packaged for Flashpoint, you can use the built-in Flash projector that is shipped with Flashpoint. Locate the Windows executable <code>FPSoftware/Flash/flashplayer_32_sa.exe</code> in the Flashpoint distribution you installed, and execute it with <code>wine</code> (you will have to install it separately, since Flashpoint on Linux invokes Wine through Docker). Make sure you have a 32-bit Wine installation. Pass the <code>.swf</code> file as a second argument to <code>wine</code>, after the <code>.exe</code>.
Afterwards, the launcher should now be able to open without issue. If you still encounter errors, try running <code>start-flashpoint.sh</code> with the <code>--no-sandbox</code> switch to fully disable sandboxing. If it works, add the switch to the end of the command that runs the launcher (either in the desktop entry or in the start script) so that you do not need to keep specifying it.


It's probably possible to use the native projector through the Docker setup, to avoid two separate Wine installations, but I haven't worked out how to do that quite yet.
== Optional Enhancements ==
=== Wine Wayland Support ===
'''Enabling this feature could break compatibility with some games/animations.'''


Obviously, this only works for games that are using the Flash technology, and are single-file and not site-locked. Flashpoint exists because many games are not like this, and require extra work.
Starting with Wine 8.4 and being officially added in Wine 10.0, a new display driver can be used to run Windows programs through Wayland instead of X11/Xwayland. To enable it, run the following command, replacing <code>$DIR</code> with the full path of the prefix you wish to modify:
WINEPREFIX=$DIR wine reg add 'HKCU\Software\Wine\Drivers' /v Graphics /d wayland,x11
To modify the default prefix, don't set WINEPREFIX. For reference, Flashpoint's prefix location relative to the installation directory is <code>FPSoftware/Wine</code>.


As an alternative to the standalone projector bundled with Flashpoint, you can use the Linux native projector, which can be downloaded from a previous version of the Adobe website [https://web.archive.org/web/20220331041116/https://www.adobe.com/support/flashplayer/debug_downloads.html here].
After making this change, all programs running in Wine from now on should be using Wayland.
<noinclude>
[[Category:Technologies]]
</noinclude>

Latest revision as of 21:48, 1 December 2025

Linux support in Flashpoint is currently experimental due to a lack of maintainers. This page describes the current state of our Linux support. If you need assistance with installing or playing, ask in the help forum on the Discord server.

Flashpoint for Linux supports Flash, HTML5, Shockwave, Unity, Java and various other web platforms. Not every platform is supported, such as DevalVR and Viscape, because some may rely too heavily on Windows features and can't run through Wine. If you want support for platforms that are Windows-exclusive, there are 2 options:

Otherwise, if you don't need support for those platforms, you may continue reading through this page.

Compatibility

Flashpoint for Linux only officially supports the x86_64 architecture and, for compatibility and security reasons, the GNU C Library (glibc). This is because the launcher uses Electron, which doesn't support 32-bit x86 for Linux, and several binaries only have x86_64 + glibc versions. If you want to run Flashpoint on other architectures like ARM or RISC-V, you must use an emulator like Box64. Likewise, for C libraries other than glibc like musl, you must recompile everything you wish to use that's not already packaged, and link them with the desired C library. You may also use a glibc compatibility layer like gcompat for proprietary binaries, such as the native Flash projector.

The main Linux version is built on Debian 11, which uses glibc 2.31, making it the minimum supported version. Flashpoint cannot be built on older Debian versions without significant changes to the launcher, due to some dependencies being incompatible. Any distro that uses glibc 2.31+ should also be supported, including but not limited to:

  • Ubuntu 20.04+
  • Fedora 32+
  • openSUSE Leap 15.3+
  • Any distro based on the above, including by proxy
  • Any rolling release distro maintained after February 2020

If you use a distro older than those listed, you must upgrade to a newer version to run Flashpoint.

Main Version

The main version of Flashpoint for Linux contains everything we currently support on Linux, and includes its own libraries and Wine runtime. The libraries are used to run Flashpoint in a known-working container, and the Wine runtime contains the binaries and libraries that the Windows-only programs need to run. These allow us to support as many different distro configurations as possible (including both mutable and immutable ones), and efficiently run non-native programs through the Flashpoint launcher without taking up too much extra space.

If you use a mutable distro (i.e. one where the root file system can be modified) and do not want all of the components, you may choose to remove the Libraries and FPSoftware/Wine directories post-install. This will leave you with only the main Flashpoint files, which total about 2 GB. See Dependencies for more information.

For the best experience, at least 4 GB of free space is recommended on the partition you wish to install Flashpoint to.

Installation

To install Flashpoint, follow these steps:

  1. Download this archive file. (SHA256: f393a98c5c35e229a744c102b0cb53270b1b4f1b3ebd40d604f98323444a4b1f)
  2. Extract the contents of the file to an empty directory that your user has read & write permissions for. This can be done graphically, or in the terminal by entering the following at the file's directory:
    7zr x fp*_lin_*.7z -oFlashpoint
  3. Open the directory you extracted Flashpoint to, then run setup-desktop-entry.sh to generate a desktop entry that opens the launcher. Alternatively, if you are unable to run desktop entries, run start-flashpoint.sh instead.

Once you've done that, Flashpoint is now installed. If you don't want to use the libraries and Wine runtime provided by Flashpoint, see the Dependencies section below.

Dependencies

If you're on an immutable distro, the following does not apply.

If you don't plan on using the libraries and Wine runtime provided, you must first remove them from your Flashpoint install. To do so, delete the Libraries and FPSoftware/Wine subdirectories from the directory you extracted Flashpoint to. Afterwards, you'll need to install the following packages for everything to work properly. A dependency listed with more than one package for a given distro means you can choose any one package from that distro according to your needs.

Distro X11 GTK3 NSS PulseAudio PHP 7-Zip Wine 32-bit Xcomposite 32-bit LibPulse
Debian-like xserver-xorg-core / xwayland libgtk-3-0 libnss3 pulseaudio / pipewire-pulse php 7zip (link) libxcomposite1:i386 libpulse0:i386
Arch-like xorg-server / xorg-xwayland gtk3 nss wine
N/A
Fedora-like xorg-x11-server-Xorg / xorg-x11-server-Xwayland pulseaudio / pipewire-pulseaudio p7zip libXcomposite.i686 pulseaudio-libs.i686
SUSE-like xorg-x11-server / xwayland libgtk-3-0 mozilla-nss php7 7zip libXcomposite1-32bit libpulse0-32bit

There are also some packages that aren't required, but can enhance your experience:

Distro GTK2 LibXt
Debian-like libgtk2.0-0 libxt6
Arch-like gtk2 libxt
Fedora-like libXt
SUSE-like libgtk-2_0-0 libXt6

These packages are needed in order to use the native Flash projector, which is not enabled by default due to minor audio delay and performance issues. If you wish to enable it, go to your Flashpoint config, click the "Platforms" dropdown beside the Native Platforms setting and click the checkbox next to "Flash".

To install any of the dependencies, use your distro's package manager:

Distro Package manager install command
Debian-like sudo apt-get install $PKG
Arch-like sudo pacman -S $PKG
Fedora-like sudo dnf install $PKG
SUSE-like sudo zypper install $PKG

ChromeOS Extra Steps

For ChromeOS users, some additional steps will need to be taken for Flashpoint to run properly. It will be assumed that you already set up a Linux terminal.

By default, when transferring files from the ChromeOS host to the Debian guest in the terminal, execute permissions are removed from all files. This will prevent everything from running, including the Flashpoint launcher. To fix this, run the following command in the terminal, replacing $DIR with the path to the directory you have Flashpoint installed in:

chmod -R +x $DIR

This command will add execute permissions to all files in the directory recursively. After running it, you can then run $DIR/start-flashpoint.sh to open the launcher.

Nix Shell

The main Flashpoint files can also be launched under a Nix shell if Nix is installed:

{ pkgs ? import <nixpkgs> {} }:

(pkgs.buildFHSEnv {
    name = "flashpoint";
    targetPkgs = pkgs: (with pkgs; [
        # Shell utils
        toybox
        # Electron for the launcher.
        electron
        # Flashpoint requirements
        pipewire pulseaudio
        gtk3 gtk2 nss php wine
        xorg.libX11 xorg.libXt xorg.libXcomposite
        # ldd requirements
        mesa #libgbm
        glib nspr at-spi2-atk cups dbus libdrm pango cairo expat libxkbcommon alsa-lib
        xorg.libXdamage xorg.libXext xorg.libXfixes xorg.libXrandr xorg.libxcb
        udev
    ]);
}).env

Simply save this code into a .nix file and run it with nix-shell {file}.nix --run ./start-flashpoint.sh.

You can also use steam-run (nix-shell -p steam-run --run "steam-run ./start-flashpoint.sh").

Minimal-Dependency Version

Due to the inherently barebones nature of this option, do not expect to receive help in the Discord if a specific game does not work.

If you are looking for a fully-native or minimal setup Flashpoint experience on Linux, Flashpoint Nano exists as a lightweight (albeit heavily limited) script-based alternative to the other installation options.

Only two platforms are supported: Flash (using Ruffle; non-embedded entries only) and HTML5 (using Pale Moon). Each software is Linux-native, downloaded upon first launch and updated automatically.

Dependencies

Only a few command-line utilities that may not be available on your system by default are required: tar, curl, sqlite3, and unxz (from XZ Utils). You should be able to install these using your distro's package manager.

Installation

  1. Download Nano from the GitHub repository by clicking the Code button and then Download ZIP. Alternatively, if you have git installed, you can use the git clone https://github.com/WumboSpasm/flashpoint-nano.git command to download the repository. The latter option may be preferable so you can download updates to the scripts using git pull.
  2. If you downloaded the ZIP archive, extract it using your method of choice.
  3. Enter the created directory and run the following command in the terminal: ./flashpoint.sh <entry-id>. You can find the ID of the desired entry using the Flashpoint Database search tool. If you wish to launch an additional application, simply append its ID to the end of your command (with a space separating it from the entry ID).

Windows Version Using Wine

Alternatively, you can attempt to run the Windows version of Flashpoint using Wine, which is a compatibility layer for Windows programs. There are several advantages to doing this, like being able to run more up-to-date versions of Flashpoint that have only been made for Windows. However, it is not guaranteed that Wine will work properly, as the experience varies greatly depending on the hardware, choice of distribution, and packages you have installed. For this to work, you currently need to install either the development or staging versions of Wine running a completely fresh prefix. How to install them depends on the distro, so consult WineHQ's download page for instructions on yours. You will also need the php package for Flashpoint to work post-install.

As of now, you can install the latest Windows version of Flashpoint Infinity by running the installer through Wine. To be able to run the installer, you need to install a recent version of Wine Mono, which should be provided upon creating a new Wine prefix or installed as a package on most distros. The process for installing Flashpoint this way is similar to how it is on Windows, except you may have to change the installation path to a location that can be written to, like your user directory. An example of a proper installation path would be Z:\home\$USER\Flashpoint, replacing $USER with your username. You may get an error upon finishing the installation; this is expected behavior. Quit the installer and kill it from your process manager if needed, and all of the files should be where you installed them.

Once done, you can then run Launcher/Flashpoint.exe through Wine and set the "Flashpoint Path" in the launcher's config to .., then click "Save and Restart" on the bottom of the page. If everything has been done correctly, you should now have a working Flashpoint install! If you are having issues running the launcher with Wine, you can instead try using various other "flavors" such as Wine GE, which has extra patches that aren't upstream. Users of Arch-like distros can install Wine GE as a package from the AUR, however no binary is provided, so it must be compiled.

Troubleshooting

Audio Glitches in Wine

Some users may experience audio glitches when running programs through Wine, like constant crackling or distortions. If this is happening to you, you may have to switch to a different audio driver. As of writing, Wine currently uses PulseAudio as the default preferred backend, but other backends are available. For example, to enable the ALSA driver, run the following command, replacing $DIR with the full path of the prefix you wish to modify:

WINEPREFIX=$DIR wine reg add 'HKCU\Software\Wine\Drivers' /v Audio /d alsa

To modify the default prefix, don't set WINEPREFIX. For reference, Flashpoint's prefix location relative to the installation directory is FPSoftware/Wine.

Switching audio drivers may or may not fix the problem right away. If you are still experiencing glitchy audio, please ask for help in the Discord server.

Launcher Sandbox Errors

Some users may receive the following error when attempting to run the launcher:

The SUID sandbox helper binary was found, but is not configured correctly.

To fix this, the permissions and owner of the sandbox have to be changed. Open a terminal in the Launcher directory of your Flashpoint install, and run the following:

chmod 4755 chrome-sandbox
sudo chown root:root chrome-sandbox

The first command will allow the owner of the sandbox to read, write and execute it; other users will only be able to read and execute. The second will set the root user and group as the owner of the sandbox. The root group should only contain the root user by default.

Afterwards, the launcher should now be able to open without issue. If you still encounter errors, try running start-flashpoint.sh with the --no-sandbox switch to fully disable sandboxing. If it works, add the switch to the end of the command that runs the launcher (either in the desktop entry or in the start script) so that you do not need to keep specifying it.

Optional Enhancements

Wine Wayland Support

Enabling this feature could break compatibility with some games/animations.

Starting with Wine 8.4 and being officially added in Wine 10.0, a new display driver can be used to run Windows programs through Wayland instead of X11/Xwayland. To enable it, run the following command, replacing $DIR with the full path of the prefix you wish to modify:

WINEPREFIX=$DIR wine reg add 'HKCU\Software\Wine\Drivers' /v Graphics /d wayland,x11

To modify the default prefix, don't set WINEPREFIX. For reference, Flashpoint's prefix location relative to the installation directory is FPSoftware/Wine.

After making this change, all programs running in Wine from now on should be using Wayland.