Skip to content

docs(godot): Add Steam, SteamOS, and Proton support page#17115

Merged
limbonaut merged 3 commits intomasterfrom
limbonaut/docs/godot-steam-support
Mar 26, 2026
Merged

docs(godot): Add Steam, SteamOS, and Proton support page#17115
limbonaut merged 3 commits intomasterfrom
limbonaut/docs/godot-steam-support

Conversation

@limbonaut
Copy link
Collaborator

@limbonaut limbonaut commented Mar 25, 2026

DESCRIBE YOUR PR

Add a new documentation page for Steam environment support in the Godot SDK (added in 1.5.0).

Covers automatic Steam detection (steam tag, Proton runtime filtering) and troubleshooting for the scout runtime libcurl incompatibility, including a warning about the Godot editor on Steam being locked to scout.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

limbonaut and others added 2 commits March 25, 2026 11:07
Document automatic Steam environment detection added in SDK 1.5.0,
including the steam tag, Proton runtime filtering, and a
troubleshooting section for the scout runtime libcurl incompatibility.

Refs getsentry/sentry-godot#613
Co-Authored-By: Claude <noreply@anthropic.com>
The Steam version of the Godot editor is locked to the scout runtime,
which has the libcurl incompatibility. Recommend using the standalone
editor from godotengine.org instead.

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Mar 25, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview, Comment Mar 25, 2026 10:35pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Preview Mar 25, 2026 10:35pm

Request Review


```
ERROR: Can't open dynamic library: libsentry.linux.debug.x86_64.so.
Error: libcurl.so.4: version `CURL_OPENSSL_4' not found
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Such errors keep popping up in many contexts. Maybe we should consider resolving the symbols at runtime with dlopen() + dlsym()... 🤔

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering myself what could be the right solution here. If I remember correctly from my past investigation, there was some conundrum in the past with the Debian-shipped libcurl, and the one in the scout container exactly has that problem. I don't recall specifics.

We could try detecting bad lib and container environment, and try locating the right lib from the host. Steam runtime should provide the host FS at /run/host.

Copy link
Contributor

@coolguyzone coolguyzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>
@codeowner-assignment codeowner-assignment bot requested a review from a team March 25, 2026 22:21
@limbonaut limbonaut merged commit e8330ab into master Mar 26, 2026
18 checks passed
@limbonaut limbonaut deleted the limbonaut/docs/godot-steam-support branch March 26, 2026 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants