Skip to content

1.0.7

Choose a tag to compare

View all tags
@viktor-ferenczi viktor-ferenczi released this 17 May 19:48
· 4 commits to main since this release
1.0.7
3cd6223
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This is a custom Pulsar for Linux build which uses this plugin for Linux compatibility. (Eventually it will be integrated into the official Pulsar repository.)

Beta release - Bugs may occur, plugins and mods may be incompatible. Please see below.

Installation

The recommendation is to use the Native build if possible, since it is more compatible with Steam. Use the Flatpak build as a fallback if the Native build does not work and you don't plan to develop plugins. Workshop access works properly in both builds.

Once installed, both builds create a start menu entry. Search for: Pulsar

Some plugins and mods may be incompatible.

Please report any bugs on the Pulsar Discord in the linux-native-bugs channel. Thanks!

Troubleshooting

Please also see the Known issues sections below.

Pulsar cannot find Space Engineers

If you have installed Space Engineers to a folder location other than Steam's default, then before installation you need to specify where SE can be found:

export SPACE_ENGINEERS_ROOT=/path/to/your/SteamLibrary/steamapps/common/SpaceEngineers/

Pulsar does not start

  1. Check ~/.config/Pulsar/info.log for errors.
  2. If a plugin fails to load, then remove it by editing ~/.config/Pulsar/Profiles/Current.xml.

If the Native build is missing some library dependencies, then please see Dependencies of the Native build below.

Any game issues

  1. Collect the relevant logs from ~/.config/SpaceEngineers/
  2. Submit a bug report on the Pulsar Discord in the linux-native-bugs channel.

Steam launch settings (optional)

  • Native: ~/.local/share/Pulsar/Interim %command%
  • Flatpak: flatpak run io.github.SpaceGT.Pulsar %command%

We suggest using the start menu entry instead.

Specifying startup arguments

Edit the start menu entry and add the arguments, for example: -skipintro

Configuration and game data folders

  • Pulsar (plugin selection, profiles): ~/.config/Pulsar
  • Space Engineers (different from Proton): ~/.config/SpaceEngineers

Both the Native and Flatpak builds use the same folders.

Known issues

Both builds

  • Start Steam before running the game, otherwise you won't have access to your saved blueprints and worlds and the workshop features. This is normal SE behavior. The difference is that on Windows SE starts Steam if not running, but on Linux it does not.
  • There is no visible progress bar during the initial shader compilation, and it may take 15+ seconds depending on your machine. This happens only on the first startup of the game and after game updates. Please be patient.
  • Select Performance mode in Linux; if you select Power Saving, the game and background video may be laggy.
  • If you have both an integrated and a dedicated GPU, select the dedicated GPU in the Display settings, then apply and restart the game.
  • On some systems the "Fullscreen" mode may be broken, due to the back-buffer resolution not matching the selected screen resolution. To recover from a broken fullscreen state delete ~/.config/SpaceEngineers/SpaceEngineers.cfg. Workaround is to use "Fullscreen Window" mode and auto-hide the OS taskbar if it would be shown above the game. Please report if your system is affected, so we can fix this.
  • Most plugins work, but the ones depending on Windows only features (like WinForms) or hard-coding path separators will break and needs to be fixed by their respective authors.

Flatpak build only

  • Steam cannot follow the game's state properly. The game's indication gets stuck in "Running" state until Steam is restarted. This is a technical limitation due to Flatpak's PID isolation, which prevents Steam from checking the state of the game's process.
  • Steam overlay does not work. Same technical limitation as with process state.
  • When switching back to windowed mode, not all available window sizes are listed. The workaround is to resize the window with the mouse as needed (it is possible on Linux, wasn't on Windows), so those "resolutions" don't matter anyway. Maximizing the window should work just fine.
  • Not suitable for plugin development, since you cannot connect your debugger to the running game. Use the Native build instead or build from sources.

Dependencies of the Native build

Download and install the latest .NET 10 runtime or SDK from Microsoft:

These dependencies must be installed from your package manager or built on your system from sources:

  • X11 or XWayland
  • Vulkan 1.3-capable GPU driver
  • Vulkan loader (libvulkan.so) 1.3+
  • SDL 3.x
  • OpenAL (openal-soft) 1.x
  • Opus codec 1.x
Assets 4
Loading