-
Notifications
You must be signed in to change notification settings - Fork 5
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
Errors when starting Steam #58
Comments
Just to add, I'm having the same issues.
|
Unable to test via the handful of DOS games I have right now (Harvester, Wolfenstein 3D work fine with their included DOSBox binaries, but not if I select a specific Boxtron version, etc.) That being said, this snippet appears to supress the error messages when entering desktop mode, at least. diff --git a/run-dosbox b/run-dosbox
index 4641d11..357c0fc 100755
--- a/run-dosbox
+++ b/run-dosbox
@@ -156,6 +156,11 @@ def run(cmd_line, wait=False):
status = fakescripteval.iscriptevaluator(cmd_line)
sys.exit(status)
+ steam_app_id = os.environ.get('SteamAppId', '0')
+ if steam_app_id == '0':
+ log('Exiting because no steam app id')
+ sys.exit(0)
+
# we don't want to detect hardware until we're sure we are starting
# the actual game:
settings.setup() For others that might want an immediate fixNot that I'd recommend updating this way... |
I manually applied @evanjs's patch and it worked for me. |
Recently, I started getting errors from Boxtron upon launching Steam.
Based on errors logged to the terminal, it looks like this is because Steam is trying to run some
d3ddriverquery64.exe
with every compatibility tool when it starts; see ValveSoftware/steam-for-linux#11435.Roberta also logs errors to the terminal but does not create any dialog windows.
Meanwhile, Luxtorpeda just logs the following:
That output was added in luxtorpeda-dev/luxtorpeda#420 which I assume was intended to handle exactly this problem, so I wonder if something similar could be done in Boxtron as well. (Ideally, Steam would just skip non-Wine-based compatibility tools in whatever it's doing with
d3ddriverquery64.exe
, but I probably shouldn't count on Valve changing Steam to suit compatibility tools that aren't Proton.)The text was updated successfully, but these errors were encountered: