Brief overview of the important changes in this release:
widevinemodules for encrypted content playback
swiftshaderfor CPU based GL acceleration on slower cards in Steam client
libstdc++.so.6to apply to games on separate Steam Libraries (partitions) so that Black Mesa launches again.
This release also features a new generic
lsi-exec entry point. This entry point is used by the main
lsi-steam) binary, and can be used to execute any given program under the LSI environment. This is useful for debugging. Future versions will add support for some GOG titles (ongoing).
LD_PRELOADvariables, allowing Simple Screen Recorders glinject to work.
DBUS_SILENCE_WARNINGSfor patched d-bus to fix message spam (only useful with this non-upstream patch or using the LSI snap)
redirect module now has a new workaround for the “Unity Black Screen Of Nope” issue. This issue is known in older Unity3D builds where the output renderer is clamped to
0x0 resolution when in fullscreen borderless mode. Many games default to this, hence the expression “black screen of nope”.
To alleviate this issue, the redirect module emulates the behaviour of the
-screen-fullscreen 0 CLI argument. The
$XDG_CONFIG_HOME/unity3d/*/prefs file is abstracted through SHM (
shm_open) and we rewrite the config on save/launch, writing an initial config if one doesn’t exist.
Specifically, we change a single preference on the fly:
<pref name="Screenmanager Is Fullscreen mode" type="int">0</pref>
This means all Unity3D games using this older prefs path will default to launching as a windowed game, even if the configuration already existed with fullscreen being activated. This alleviates the issue for many games (tested with “Keep Talking And Nobody Explodes” and others) - but obviously forces these games to not know about the fullscreen setting anymore. You can enable this again in-game, and this is effectively the price to pay for general compatibility. The game authors can alleviate this by updating to the latest build of Unity3D and issuing new Linux builds. You may also turn off this option through the
lsi-settings UI if you do not have any games that suffer from this common bug.
shim architecture shared by the
lsi-steam binary entry points now has support for running within snapd, within the
$SNAP_USER_COMMONfor more efficient/sane update paths
vdpaufrom host NVIDIA files dynamically
The following changes have happened upstream to allow support for LSI:
General support for biarch distros/Solus as a runtime snap:
All of that work both within LSI and on snapd wouldn’t make a lot of sense if you weren’t able to make use of the new Snaps! Right now we have our snaps living on the
edge channel in the snap store, and they can be downloaded provided you have a sufficiently new
snapd version. Currently you need to be running either a git/unstable or PPA (edgers) version of snapd to install them, and there are some known issues at present.
Please ensure that if you have manually installed the old snaps that you remove them before installing the new snaps.
sudo snap install --edge solus-runtime-gaming sudo snap install --edge --devmode linux-steam-integration
At this time Solus and Ubuntu are known to work with the latest versions of snapd and our snaps, though we appreciate testing and feedback via the LSI Issue Tracker. In the new year we will begin working on the last remaining items to allow full confinement for Steam, and will begin moving our snaps into the stable channels. At that point, we will make snaps the preferred method for installing Steam on Solus, and using LSI in general.