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

[Bug]: macos m1: Launching from steam starts the intel version #9710

wrenger opened this issue Nov 19, 2021 · 2 comments

[Bug]: macos m1: Launching from steam starts the intel version #9710

wrenger opened this issue Nov 19, 2021 · 2 comments


Copy link

wrenger commented Nov 19, 2021

Version of OpenTTD


Expected result

I've seen that OpenTTD has a universal version for macos, which can also be installed by Steam.
The Problem is that the game Starts as intel (emulated over rosetta 2) when launched from Steam. When the is launched directly from Finder, it starts in arm mode as expected. I'm not sure if this is a Steam Problem or something went wrong on your side (like packaging the old non-universal steam api... release notes).

PS: M1 MacBook Air, Steam Build: 13.10.21

Actual result

OpenTTD starts in intel mode, not arm (Apple).

Steps to reproduce

  1. Launch the game from the Steam Library
  2. Open the Activity and look for the (which is displayed as intel not Apple in the Kind column).
Copy link

glx22 commented Nov 19, 2021

I think it's related to how steam launches games, and I guess steam is still an intel only app.

Copy link

Sadly, nothing we can do about this. Steam launches in Intel mode, and as such all games Steam launches do too. Despite us shipping an Universal build (as you found out).

Only when Steam ships an universal build this will resolve itself. Till that time, better to start the game from Finder. Sorry ...

PS: we don't use the SDK, so that is not relevant to us. It helps native games work with the SDK, but still requires launching from Finder .. sad times.

Going to close this issue now, as really there is nothing we can do about it :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

3 participants