Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
War Thunder is native on Linux and Steam installs the Linux build there, which has linux64/aces instead of win64/aces.exe. Since win64/aces.exe was required, the game was never discovered on Linux.
On Linux the executable is now picked from what's installed: win64/aces.exe if the Windows build is there (game set to run through Proton), linux64/aces otherwise (it has an $ORIGIN rpath, so it finds the libraries next to it). The required file is aces.vromfs.bin, which both builds have.
Checked against a Steam install, both with the native build (linux64/aces) and switched to Proton (win64/aces.exe). Before this it wasn't discovered with the native build.