I prefer appimages, it feels much more “open” than flatpak ever will.

Flatpak: install flatpost and flatseal.

Appimage: Download appimaged appimage to ~\Applications and run once.

then

Flatpak: Go to site for cool software I heard of, see it’s flatpak with a link on the page. Click link, wait for flatpost to open, wait for flatpost to update repos, get cool software and possibly another copy of mesa and gnome compat stuff, then head to flatseal to fix drive/device permissions as needed.

Appimage: Go to site for cool software I heard of, see it’s an appimage, download said appimage to ~\Applications, appimaged automatically loads in a desktop entry and we’re done.

As far as updates, all the appimages that are in active development that I use, offer auto-updating when I open them, plus I’m not reliant on a centrally-controlled repo of the packages (which if it dies, takes all updates with it).

I feel appimage would be an easier adoption for people fresh to linux, as it follows the same model as windows or macos (download executable, install app), even for the initial setup of appimaged.

And either way, there’s no “winner” here, if we’re playing that game, native installs still win. Every distro supports (and uses) those by default, except for ubuntu, who has money on pushing snaps.

I tried different guides, and eventually went to the source, this worked great for me.

From SE Discord, posted by “lord.of.woe”:

Space Engineers Linux Installation Guide Last Updated 2025-07-24

Prerequisite Packages

git

wget

WINE

Step 1: Install GE-Proton9-25 and GE-Proton10-X. There are several methods you can use to install this, but this guide uses only common terminal commands. (Edit: I used Protonplus for this)

wget -qO- https://github.com/GloriousEggroll/proton-ge-custom/releases/download/GE-Proton9-25/GE-Proton9-25.tar.gz | tar xzvf - -C "${HOME}/.steam/steam/compatibilitytools.d"
wget -qO- "$(curl -s https://api.github.com/repos/GloriousEggroll/proton-ge-custom/releases/latest | grep "\"browser_download_url\": \".*\.tar\.gz\"" | cut -d'"' -f4)" | tar xzvf - -C "${HOME}/.steam/steam/compatibilitytools.d"

Step 2: Remove local Space Engineers data. ‼️ WARNING: THIS WILL PERMANENTLY DELETE ALL SAVES, GAME DATA, ETC. THAT ARE NOT BACKED UP TO THE STEAM CLOUD OR ELSEWHERE. ‼️

export STEAMAPPS_PATH=${HOME}/.steam/steam/steamapps # edit as necessary
rm -rf ${STEAMAPPS_PATH}/compatdata/244850

Step 3: Restart Steam

Step 4: Change the compatibility layer in Steam to GE-Proton9-25.

Step 5: Launch Space Engineers in Steam and close the game upon reaching the main menu.

Step 6: Install dotnet48. DO NOT USE PROTONTRICKS.

WINEPREFIX=${STEAMAPPS_PATH}/compatdata/244850/pfx winetricks --force -q dotnet48

or experimentally

WINE=${HOME}/.steam/steam/compatibilitytools.d/GE-Proton9-25/files/bin/wine64 
WINEPREFIX=${STEAMAPPS_PATH}/compatdata/244850/pfx ${HOME}/.steam/steam/compatibilitytools.d/GE-Proton9-25/protonfixes/winetricks --force -q dotnet48

Step 7: Change the compatibility layer in Steam to GE-Proton10-X, where X is the minor version.

Step 8: Launch the game and hope everything worked.

last played Jan 24

Hard no.

We loved the first, but the second adds the stupid infection thing, and was in the “ok, playable” pile at the start, but all the glitches and bugs made us stop. Between day/night not working for non-hosts, buildings with huge map holes in them, and very poorly scripted quests we dropped it. The final straw was when we were doing side stuff, ignoring the main mission, and passed over a building that was part of a later stage in the main mission, causing us to softlock, then on restart being at the later step in the main mission. Just trash programming.

If you really want to play it, pirate it. Don’t give money for it.

this is true, anything requiring constant updates and calling home will probably have an issue eventually

I got several “Nook Simple Touch” a few years ago and they’ve been able to read whatever I’ve thrown at them so far.

They’re running on android 2.1!

I had to do some digging to find older versions of book apps that’d run on them, but this is the internet, the apks are out there.

Another option is if you have coax installed for tv/cable, and aren’t using it, even just in the rooms you want to connect wires through, MoCA might work.

I agree that everyone should stop using windows 10 this year.

Nobara for gamers, Mint for everyone else. Done and done.

Sorry for the confusion, but STL files are usually manifold 3d renders, for printing. No subtitles here unfortunately. I’m not even aware of a paid service/site for subtitles, is that a thing?

Only one I know is materialize.is

I’m still trying to find a way to get an invite…

The Spanish Fly

For Android: learn the hard reset combo for your phone, especially if you encrypt it.

After rebooting, pattern/PIN will be required to decrypt the phone. Biometrics won’t work for this step. This is what graphene does for security, tries to keep the phone in a “before first unlock” state by rebooting on a timer. You can’t even read anything over USB/ADB, it’s scrambled until you unlock the phone.

The only drawback to just keeping your phone in this state is none of your apps are loaded, so no notifications/updates/processing at all.

Reposting as top level comment also: these are PWDIS drives: if you’re not using them somewhere with sata 3.2/3.3, you need to use an adapter for the power plug, or some tape, to block pins 1-3 (3.3v) as supplying it to these causes them to reset. Might be worth doing the taping anyway, if you’re using an enclosure or cage (where you can’t use the adapters) Just be aware.

2nd catch, behind the power on time: PWDIS drives: if you’re not using them somewhere with sata 3.2/3.3, you need to use an adapter for the power plug, or some tape, to block pins 1-3 (3.3v) as supplying it to these causes them to reset. Might be worth doing the taping anyway, if you’re using an enclosure or cage (where you can’t use the adapters)

Nintendo went after a emu dev team that was actively (and demonstratively) enabling piracy for something they are currently selling. On top of that, the dev team is making significant money off of that work, to the tune of 30k/mo. Every other dev is probably thinking “finally, the other shoe drops on this obvious outcome”, most avoid making money off it, and also avoid current systems, both for just this reason. The relieving part is Nintendo’s argument isn’t about the emulator specifically, there’s nothing in the injunction stopping yuzu from continuing, and a settlement means no legal precedent.

Edit: Read more, the settlement includes stopping development.

I mean, small developers who set up a money-making pateron based on an emulator for a currently sold system, without providing a way to pull your own system info or games from carts (and is therefore heavily reliant on piracy of things currently being sold by the parent company to run) is basically screwed, but this isn’t news, and pretty much every other emu dev would run away screaming from such a setup.

They really put themselves in this boat, but since that money-making pateron is a thing, they’re probably wiping those tears with dollar bills.

-128 sounds like an error for sure. move your hub closer could help. If you’re sure it’s not a distance/signal issue it’s the hub itself.

And I love how it’s the opposite of other console approaches.

Everyone else: “let’s rope some devs into exclusives, and make some more in house, that’ll lock them in!”

Valve: “let’s develop improvements to OSS publicly, so it runs better on PC for everyone (and our product)”

can I 3d print PETG objects, use them, put them in the dishwasher, and then safely reuse them?

No.

Replace the extruder. The plastic one will break, and screw up your day. It may already be broken even. Anything is better, even a drop-in metal copy of the existing one. If you want to spend a lil $$ to future-proof yourself, look into a BMG.