Linux Support: Difference between revisions

From Flashpoint Datahub
Jump to navigation Jump to search
(Updated to 20250219)
 
(46 intermediate revisions by 5 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 <code>flashpoint-help</code>.
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> channel on the [https://flashpointarchive.org/discord Discord server].


As it stands, Flashpoint for Linux supports Flash, HTML5, Shockwave and Java, with Unity only being supported on the Docker version. 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 a few options to get the Windows version of Flashpoint running on Linux:
* [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 works well on some computers, but does not work consistently.


Otherwise, follow any of the instructions below.
Otherwise, if you do not need support for those platforms, you may continue reading through this page.
== Automated Installation ==


=== Notes ===
== Compatibility ==
Flashpoint for Linux only officially supports the x86_64 architecture. This is because the launcher uses Electron, which does not support 32-bit x86 for Linux, and several included binaries only have x86_64 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].


This build is recommended for use on the Steam Deck, and on distros with an immutable rootfs. If you do not fit this criteria, it is recommended that you follow the [[#Manual_Installation|manual installation instructions]] instead.
The current Linux version of Flashpoint 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


QEMU and PHP are bundled in an included Junest Arch proot Appimage.
If you use a distro older than those listed, you must upgrade to a newer version to run Flashpoint.


=== Current Issues ===
== Main Version ==
This version of Flashpoint for Linux is split up into 3 different parts; the main files, which contain everything that Flashpoint itself and the platforms need to work; the libraries, which can be used to run Flashpoint in a known-working container (like an immutable version); and the Wine runtime, which has everything that the Windows-only programs need to run and nothing more. The main files are required for Flashpoint to work, but the others are optional, and you can decide if you want to download them based on your preferences.


QEMU with the default <code>-display none</code> crashes upon launch, but displays fine allowing the GTK window to appear. The install script accounts for this.
It's recommended to have at least 4 GB of free space for the smoothest experience with all the components. You can possibly get away with less if you [[#Dependencies|already have the dependencies installed]] on your system.


If running on the Steam Deck Game Mode session, mouse is locked to QEMU size and Flash games in Wine only render black. It is recommended to use desktop mode on the Deck.
=== Main Files ===
To install the main Flashpoint files, follow these steps:
# Download [https://download.unstable.life/upload/fp14.0.1_lin_main_20250219.7z this archive file].
# 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 fp14.0.1_lin_main_*.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.


HTML5/Unity/browser games that use <code>FPSecure/Basilisk</code> are a hit and miss for compatibility. This is down to the browser interaction with Wine.
Once you've done that, Flashpoint is now installed. If you don't want to or can't [[#Dependencies|install the dependencies]], you should also download the optional components below.


=== Instructions ===
=== Libraries ===
'''If you already have all the dependencies listed in the Dependencies section installed, you can skip this.'''


# Download [https://drive.google.com/file/d/11NQoGTWkvA4CxCbGhAVD-o9nMNkzxndb/view?usp=drivesdk this archive file] to a memorable folder.
This section will assume you've [[#Main Files|already downloaded and extracted the main files as described above]].
# Change directory to the folder it was moved to.
# <pre>$ tar xvf fp121linux.tar.gz</pre>
# Run <code>install_flashpoint.sh</code> within a terminal session to see the progress.


You will end up with a Flashpoint folder. Run <code>start-flashpoint.sh</code> within to start the Launcher.  
To install the libraries, follow these steps:
# Download [https://download.unstable.life/upload/fp14.0.1_lin_libs_20250219.7z this archive file].
# Extract the contents of the file to the <code>Libraries</code> directory of your Flashpoint install.
# If you already have a desktop entry, rerun <code>setup-desktop-entry.sh</code> to generate a new one that'll load the binaries and libraries from the <code>Libraries</code> directory instead.


== Manual Installation ==
When finished, your Flashpoint install should automatically use the binaries and libraries you've extracted instead of your system ones.
 
=== Wine Runtime ===
'''If you already have all the dependencies listed in the Dependencies section installed, you can skip this.'''
 
This section will assume you've [[#Main Files|already downloaded and extracted the main files as described above]].
 
To install the Wine runtime to run Windows programs, follow these steps:
# Download [https://download.unstable.life/upload/fp14.0.1_lin_wine_20250219.7z this archive file].
# Extract the contents of the file to the <code>FPSoftware/Wine</code> directory of your Flashpoint install.
 
If done correctly, Flashpoint should detect the Wine install you've extracted and use that instead of the one on your system, if applicable. The advantage of doing this over just using the system Wine is that the custom runtime is fine-tuned for Flashpoint; it only contains the executables and DLLs needed to run Flashpoint's Windows-only programs. Doing this reduces overall load times for Wine applications, and reduces the size of the prefix that Wine generates/updates.


=== Dependencies ===
=== Dependencies ===
First, install Flashpoint's dependencies.
'''If you already downloaded and extracted all the optional components, you can skip this.'''
{| class="wikitable"
 
!colspan="9"|Dependency package names on various distros
If you are not using the optional components provided above, you'll need to install the following packages for Flashpoint 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
!PulseAudio<small><sup><span style="color:#0000ff">1</span></sup></small>
!X11
!X11<small><sup><span style="color:#0000ff">2</span></sup></small>
!GTK3
!GTK3
!NSS
!NSS
!PulseAudio
!PHP
!PHP
!7-Zip
!Wine
!Wine
!bash
!32-bit Xcomposite*
!32-bit LibPulse*
|-
|-
!Debian-like<span style="color:#0000ff"><small><sup>a</sup></small></span>
!Debian-like
|pulseaudio
|xserver-xorg-core / xwayland
|xserver-xorg-core
|libgtk-3-0
|libgtk-3-0
|libnss3
|libnss3
|php
|rowspan=2|pulseaudio / pipewire-pulse
|(see [https://wiki.winehq.org/Debian this page])
|rowspan=3|php
|bash
|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>
!Arch-like
|pulseaudio
|xorg-server / xorg-xwayland
|xserver-xorg-core
|rowspan=2|gtk3
|libgtk-3-0
|rowspan=2|nss
|libnss3
|wine
|php
|lib32-libxcomposite
|(see [https://wiki.winehq.org/Ubuntu this page])
|lib32-libpulse
|bash
|-
|-
!Fedora-like
!Fedora-like
|pulseaudio
|xorg-x11-server-Xorg / xorg-x11-server-Xwayland
|xorg-x11-server-Xorg
|rowspan=2|pulseaudio / pipewire-pulseaudio
|gtk3
|p7zip
|nss
|([https://gitlab.winehq.org/wine/wine/-/wikis/Fedora link])
|php
|libXcomposite.i686
|(see [https://wiki.winehq.org/Fedora this page])
|pulseaudio-libs.i686
|bash
|-
|-
!Arch-like<span style="color:#0000ff"><small><sup>c</sup></small></span>
!SUSE-like
|pulseaudio
|xorg-x11-server / xwayland
|xorg-server
|libgtk-3-0
|gtk3
|mozilla-nss
|nss
|php7
|php
|7zip
|wine
|wine
|bash
|libXcomposite1-32bit
|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, EndeavourOS</small>
<small>* Not required on Fedora 40+ and its derivatives</small>
 
'''Note:''' Chances are that Wine 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:
There are also some packages that aren't required, but can enhance your experience:
{| class="wikitable"
{|class="wikitable"
!colspan="9"|Optional dependencies
!Distro
|-
!GTK2
!Library/command name
!LibXt
!GTK2<small><sup><span style="color:#0000ff">3</span></sup></small>
!LibXt<small><sup><span style="color:#0000ff">3</span></sup></small>
|-
|-
!Debian-like
!Debian-like
|libgtk2.0-0
|libgtk2.0-0
|libxt6
|libxt6
|-
!Arch-like
|rowspan=2|gtk2
|libxt
|-
|-
!Fedora-like
!Fedora-like
|gtk2
|libXt
|libXt
|-
|-
!Arch-like
!SUSE-like
|gtk2
|libgtk-2_0-0
|libxt
|libXt6
|}
|}
<small><span style="color:#0000ff">1</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].
<span style="color:#0000ff">2</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.
<span style="color:#0000ff">3</span>: Required for native Flash support. To support versions <27, the 32-bit version of this package must be installed instead.</small>


To install them, use your distro's package manager:
To install them, use your distro's package manager:
Line 120: Line 139:
|-
|-
!Debian-like
!Debian-like
|<code>sudo apt-get install {PACKAGE}</code>
|<code>sudo apt-get install $PKG</code>
|-
!Fedora-like
|<code>sudo dnf install {PACKAGE}</code>
|-
!Fedora-like (old)
|<code>sudo yum install {PACKAGE}</code>
|-
|-
!Arch-like
!Arch-like
|<code>sudo pacman -S {PACKAGE}</code>
|<code>sudo pacman -S $PKG</code>
|}
 
=== Setup ===
Make sure you have at least 4 GB of free space, and that you have <code>p7zip</code> installed to be able to extract from 7z files.
 
=== Installation ===
# Download [https://drive.google.com/file/d/186DlQraQTjYBl21YCOc2ULonUjZ5JECz/view this archive file].
# Extract the contents of the file to an '''empty''' folder that your user has read & write permissions for. This can be done graphically, or in the terminal by entering the following in the directory the file is in:<pre>$ 7zr x fp12_linux_*.7z -oFlashpoint</pre>
# Open the folder you extracted Flashpoint to, then run <code>start-flashpoint.sh</code> to open the launcher.
After the installation is complete, you should not move any files in the Flashpoint folder at all. Moving the wrong file/folder could break the entire program until it is moved back.
 
A README document is provided that has most of the instructions shown in this section, as well as some additional notes.
 
== Docker Version ==
'''This version is outdated and support for it may be dropped soon.'''
 
=== Dependencies ===
First, install Flashpoint's dependencies.
{| class="wikitable"
!colspan="9"|Dependency package names on various distros
|-
!Library/command name
!Docker
!PulseAudio<small><sup><span style="color:#0000ff">1</span></sup></small>
!X11<small><sup><span style="color:#0000ff">2</span></sup></small>
!XHost
!NSS
!PHP
!bash
|-
!Debian-like<span style="color:#0000ff"><small><sup>a</sup></small></span>
|(see [https://docs.docker.com/engine/install/debian/ this page])
|pulseaudio
|xserver-xorg-core
|x11-xserver-utils
|libnss3
|php
|bash
|-
!Ubuntu-like<span style="color:#0000ff"><small><sup>b</sup></small></span>
|(see [https://docs.docker.com/engine/install/ubuntu/ this page])
|pulseaudio
|xserver-xorg-core
|x11-xserver-utils
|libnss3
|php
|bash
|-
|-
!Fedora-like
!Fedora-like
|(see [https://docs.docker.com/engine/install/fedora/ this page])
|<code>sudo dnf install $PKG</code>
|pulseaudio
|xorg-x11-server-Xorg
|xhost
|nss
|php
|bash
|-
|-
!Arch-like<span style="color:#0000ff"><small><sup>c</sup></small></span>
!SUSE-like
|docker
|<code>sudo zypper install $PKG</code>
|pulseaudio
|xorg-server
|xorg-xhost
|nss
|php
|bash
|}
|}
<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, EndeavourOS</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.
=== Nix Shell ===
The main Flashpoint files can also be launched under a Nix shell if Nix is installed:
<pre>{ pkgs ? import <nixpkgs> {} }:


<small><span style="color:#0000ff">1</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].
(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>.


<span style="color:#0000ff">2</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.</small>
You can also use <code>steam-run</code> (<code>nix-shell -p steam-run --run "steam-run ./start-flashpoint.sh"</code>).


=== Setup ===
== Minimal-Dependency Version ==
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 relog if the permissions aren't applied properly when trying to run Docker commands as a non-root user.
'''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 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.
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.


==== Optional: Configuring non-root Flashpoint ====
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.


Start by creating a wrapper script for Docker 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>:
=== 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.
<pre>
#!/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, your script could retrieve the password from a password manager like <code>pass</code>, which will force authentication through a graphical dialog before retrieving it. Technically you could just hardcode your password in the script, but this would defeat the point of trying to be more secure in the first place.
 
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.
 
==== Nvidia GPUs ====
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.
 
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.
# 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).


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.
== 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.


Finally, run the <code>./flashpoint</code> executable script to start the launcher.
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 home 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.


At this point, you can try to run the Windows version of the launcher through Wine, but it's recommended that you download the [https://github.com/FlashpointProject/launcher/releases/latest native Linux launcher] as a 7z file and replace everything in the <code>Launcher</code> directory with the files extracted from it. You may need to install the <code>p7zip</code> package to be able to extract from the file. Once done, you can then run <code>Launcher/flashpoint-launcher</code> 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!


Config files can be found in <code>./LinuxConf/</code> and <code>./FPSoftware/FSPConfigs/</code>.
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 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 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:
# 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>.
# 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>
# Restart the Docker service by running <code>sudo systemctl restart docker</code>.
# Run Flashpoint and install the content of your choosing, then close the launcher when finished.
# Open the Docker service file again and revert the previous change to the line, then restart the Docker service again.
# Relaunch Flashpoint and run the installed content again. It should now work.


== Optional Enhancements ==
== Optional Enhancements ==
=== Wine Wayland Support ===
'''Enabling this feature could cause unforeseen bugs and break compatibility with some games/animations. Do so at your own risk.'''


=== Wayland Support ===
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:
'''This does not apply to the manual version, which already has this enhancement applied.'''
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>.
The Flashpoint launcher is based on a version of Electron that has experimental support for running through Wayland instead of X11/Xwayland. If you use a Wayland compositor, like Mutter or Kwin, then you can enable this feature by opening the script used to run the launcher in a text editor and changing the following line from:
"./Launcher/flashpoint-launcher"
to:
"./Launcher/flashpoint-launcher" --ozone-platform-hint=auto
After making this change, the launcher should now open through Wayland when running the script. This only affects the launcher; content that runs in X11/Xwayland will continue to do so.
 
If you are following the [[#Using_Wine|Wine installation instructions]] below, you will have to make your own script and give it execute permissions to do this.
 
== Using Wine ==
 
Alternatively, you can attempt to run the Windows version of Flashpoint using 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, 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 [https://wiki.winehq.org/Download download page] for instructions on yours. Additionally, you will also need the <code>qemu-system-x86</code> and <code>php</code> packages installed 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 the .NET framework via 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 home folder. An example of a proper installation path would be <code>Z:\home\$name\Flashpoint</code>, where you replace <code>$name</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 most of the files (including all of the ones that are needed for Flashpoint to work) should be where you installed them.
 
At this point, you can try to run the Windows version of the launcher through Wine, but it's recommended that you download the [https://github.com/FlashpointProject/launcher/releases/latest native Linux launcher] as a 7z file and replace everything in the <code>Launcher</code> folder with the files that are extracted from it. You may need to install the <code>p7zip</code> package to be able to extract the contents of the file. Once done, open <code>./Data/services.json</code> in a text editor and change the following line from:
"filename": "qemu-system-i386.exe",
to:
"filename": "qemu-system-i386",
This will start your installed QEMU program instead of attempting to run the bundled EXE file. You can then run <code>./Launcher/flashpoint-launcher</code> 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! Note that not all platforms will work when installing Flashpoint this way, as Wine is not a perfect simulation of a typical Windows environment.
 
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.
 
== Technologies (Docker) ==
 
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 (Docker) ===
* 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 (Docker) ==
 
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>.
 
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.
 
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.


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 22:38, 19 February 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 channel 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 a few options to get the Windows version of Flashpoint running on Linux:

Otherwise, if you do not need support for those platforms, you may continue reading through this page.

Compatibility

Flashpoint for Linux only officially supports the x86_64 architecture. This is because the launcher uses Electron, which does not support 32-bit x86 for Linux, and several included binaries only have x86_64 versions. If you want to run Flashpoint on other architectures, like ARM or RISC-V, you must use an emulator like Box64.

The current Linux version of Flashpoint 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

This version of Flashpoint for Linux is split up into 3 different parts; the main files, which contain everything that Flashpoint itself and the platforms need to work; the libraries, which can be used to run Flashpoint in a known-working container (like an immutable version); and the Wine runtime, which has everything that the Windows-only programs need to run and nothing more. The main files are required for Flashpoint to work, but the others are optional, and you can decide if you want to download them based on your preferences.

It's recommended to have at least 4 GB of free space for the smoothest experience with all the components. You can possibly get away with less if you already have the dependencies installed on your system.

Main Files

To install the main Flashpoint files, follow these steps:

  1. Download this archive file.
  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 fp14.0.1_lin_main_*.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 or can't install the dependencies, you should also download the optional components below.

Libraries

If you already have all the dependencies listed in the Dependencies section installed, you can skip this.

This section will assume you've already downloaded and extracted the main files as described above.

To install the libraries, follow these steps:

  1. Download this archive file.
  2. Extract the contents of the file to the Libraries directory of your Flashpoint install.
  3. If you already have a desktop entry, rerun setup-desktop-entry.sh to generate a new one that'll load the binaries and libraries from the Libraries directory instead.

When finished, your Flashpoint install should automatically use the binaries and libraries you've extracted instead of your system ones.

Wine Runtime

If you already have all the dependencies listed in the Dependencies section installed, you can skip this.

This section will assume you've already downloaded and extracted the main files as described above.

To install the Wine runtime to run Windows programs, follow these steps:

  1. Download this archive file.
  2. Extract the contents of the file to the FPSoftware/Wine directory of your Flashpoint install.

If done correctly, Flashpoint should detect the Wine install you've extracted and use that instead of the one on your system, if applicable. The advantage of doing this over just using the system Wine is that the custom runtime is fine-tuned for Flashpoint; it only contains the executables and DLLs needed to run Flashpoint's Windows-only programs. Doing this reduces overall load times for Wine applications, and reduces the size of the prefix that Wine generates/updates.

Dependencies

If you already downloaded and extracted all the optional components, you can skip this.

If you are not using the optional components provided above, you'll need to install the following packages for Flashpoint 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 lib32-libxcomposite lib32-libpulse
Fedora-like xorg-x11-server-Xorg / xorg-x11-server-Xwayland pulseaudio / pipewire-pulseaudio p7zip (link) libXcomposite.i686 pulseaudio-libs.i686
SUSE-like xorg-x11-server / xwayland libgtk-3-0 mozilla-nss php7 7zip wine libXcomposite1-32bit libpulse0-32bit

* Not required on Fedora 40+ and its derivatives

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

To install them, 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

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 home 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.

At this point, you can try to run the Windows version of the launcher through Wine, but it's recommended that you download the native Linux launcher as a 7z file and replace everything in the Launcher directory with the files extracted from it. You may need to install the p7zip package to be able to extract from the file. Once done, you can then run Launcher/flashpoint-launcher 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 Flashpoint 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.

Optional Enhancements

Wine Wayland Support

Enabling this feature could cause unforeseen bugs and break compatibility with some games/animations. Do so at your own risk.

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.