Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam Runtime Soldier Engine Building #345

Closed
82 tasks done
d10sfan opened this issue Jan 26, 2021 · 0 comments
Closed
82 tasks done

Steam Runtime Soldier Engine Building #345

d10sfan opened this issue Jan 26, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@d10sfan
Copy link
Member

d10sfan commented Jan 26, 2021

This adds support for running games in Steam Runtime Soldier. With this version, there will be two compatibility tools, the original one named "Luxtorpeda" and one called "Luxtorpeda (Runtime"). Engines have to be re-built to support the new runtime, so not all games will be supported in the runtime mode at this time. See https://luxtorpeda-dev.github.io/packages.html for the package list between the two.

This ticket should be used to report any issues with the new runtime built engines, along with any other lux-related issues.

The original version will still work as normal and normal engine downloads will still work in non runtime mode.

I've been working on switching to using the new runtime, since it offers alot more recent tooling and packages, leading to less builds that have to be done. As well, it should lead to better compatibility, since the runtime is a known system. Before, I was using a combination of the old steam runtime, which was causing more and more issues, and ubuntu 18.04 which didn't always provide good compatibility.

As part of these changes as well, I've streamlined the way that libraries that are not part of the runtime (like fluidsynth or ffmpeg) are built, which makes the build scripts alot simpler.

Currently, not every game is supported as I have to fix each engine build and test them, but you can see which ones are supported in the new runtime by going to the packages.html page and clicking on runtime.

Until they are all there, if you download the alpha release, you'll get luxtorpeda (the original one) or luxtorpeda (runtime). The runtime one will use the new runtime. The original is now frozen, in that it will still work, but no updates are being made to it.

Eventually, newer versions of the client will only have "runtime", although you could still use the older client for the original if you ever needed to. My goal is to do that once I've completed porting all the engines over.

Engines (Either Completed Or Open Pull Requests)

  • 1oom
  • arxlibertatis
  • augustus
  • avp
  • bstone
  • chocolate-doom
  • classic-rbdoom-3-bfg
  • commander-genius
  • cortex-command
  • ctp2
  • daikatana
  • darkplaces-2017
  • dhewm3
  • doomsday
  • dosbox-staging
  • dxx-rebirth
  • easyrpg-player
  • ecwolf
  • eduke32
  • engge
  • eternaljk
  • etqw
  • exhumed
  • fs2open
  • ftequakeworld
  • good-robot
  • gzdoom
  • hammerofthyrion
  • ioquake3
  • iortcw
  • ja2-stracciatella
  • jk2mv
  • julius
  • koi-farm
  • nblood
  • objectn
  • openapoc
  • opengothic
  • openhexagon
  • openjk
  • openlara
  • openloco
  • openmw
  • openmw-tes3mp
  • openrct2
  • opentomb
  • openxcom
  • openxcom-oxce
  • openxray
  • perimeter
  • prboom-plus
  • prey2006
  • quake3e
  • quake4
  • quakespasm-spiked
  • raze
  • rbdoom-3-bfg
  • realrtcw
  • rednukem
  • reminiscence
  • reone
  • residualvm
  • rigelengine
  • rottexpr
  • runelite
  • runescape
  • scummvm
  • serious-engine
  • shockolate
  • solarus
  • source-sdk-2013
  • unreal-gold
  • ut2004
  • ut99
  • vkquake
  • vkquake2
  • voidsw
  • warzone2100
  • wigzdoom
  • wrath-darkplaces
  • yquake2
  • zandronum

References

https://gitlab.steamos.cloud/steamrt/soldier/sdk
https://github.com/ValveSoftware/Proton/blob/proton_5.13/toolmanifest_runtime.vdf

https://github.com/ValveSoftware/steam-runtime/blob/master/doc/steamlinuxruntime-known-issues.md#sharing-directories-with-the-container (kdialog?)
flathub/com.valvesoftware.Steam#394 (comment)

@d10sfan d10sfan transferred this issue from luxtorpeda-dev/luxtorpeda Jan 31, 2021
@d10sfan d10sfan transferred this issue from luxtorpeda-dev/packages Mar 16, 2021
@d10sfan d10sfan transferred this issue from luxtorpeda-dev/luxtorpeda May 3, 2021
@d10sfan d10sfan added the enhancement New feature or request label May 3, 2021
@d10sfan d10sfan assigned d10sfan and unassigned d10sfan Jul 6, 2021
@d10sfan d10sfan self-assigned this Aug 10, 2021
@d10sfan d10sfan pinned this issue Sep 16, 2021
@d10sfan d10sfan changed the title Investigate new Steam Runtime as possibility for building against Steam Runtime Soldier Engine Building Sep 17, 2021
@d10sfan d10sfan closed this as completed Sep 25, 2021
@d10sfan d10sfan unpinned this issue Sep 25, 2021
@d10sfan d10sfan reopened this Sep 25, 2021
@d10sfan d10sfan pinned this issue Sep 25, 2021
@d10sfan d10sfan unpinned this issue Sep 25, 2021
@d10sfan d10sfan closed this as completed Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant