I didn't find these directions compiled anywhere for the GOG linux version and it took me a while to figure it out, so thought I'd post here.

GOG FTL Linux (current ftl_advanced_edition_1_6_12_2_34795.sh) works on my Acer Chromebook Spin 11 in Crostini.

Enable Crostini and Crostini GPU support. Find directions easily on Google.

Download the FTL installation script and place in the "Linux files" directory on the Chromebook with the Files app. Open the Crostini linux terminal and run the installation script.

Currently, it seems like GOG forgot to include start.sh, so I created one in the game directory and edited permissions to make it executable.

My start.sh contains:
----------------------
#!/bin/sh

cd "/home/*YOURNAME*/GOG Games/FTL Advanced Edition/game"

MESA_GL_VERSION_OVERRIDE=3.0 "/home/*YOURNAME*/GOG Games/FTL Advanced Edition/game/FTL" ""
----------------------

The "MESA_GL_VERSION_OVERRIDE=3.0" prefix was necessary because it was running 3.1 by default and resulting in a black screen on startup.

Once I got video working, I didn't have any audio.

I ran these commands in the terminal:
sudo apt-get update
sudo apt-get dist-upgrade
rm -rf ~/.config/pulse

Then CTRL-ALT-T to open the crosh terminal and enter the following:
vmc stop termina

Then the .desktop shortcut that the installer creates should be able to be run from the ChromeOS start menu, and can even be pinned to the task bar.

This GOG linux version seems to be running great for me on Crostini. I doubt it's officially supported, but I'll take it.

I had originally installed the Steam version and had to use the MESA override, but also had to enable other compatibility options and, while it ran, it stuttered and audio wasn't playing smoothly. This GOG version is working much better for me.

Good luck!

Thanks for the tip. I got it to run. Only problem is the pointer is not working. Can you use the pointer in the game window?

I have #exo-pointer-lock enabled and am on V80 beta BTW.

I didn't have to configure anything for pointer. It just worked for me from the beginning, as far as I recall.

Are you running in windowed mode or full screen? If full screen, how did you configure for opening in full screen?

EDIT: Hmm switching from the Google keyboard to the Brydge one and it is working for me now. Switching to full screen broke it so I needed to run in windowed mode and reboot before it worked again.