You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Steam, you can use %command% to specify a prefix/suffix for launching applications.
So if you like to run hl2.exe -dx9 you can either input -dx9 or %command% -dx9. This allows you to prepend launch options, too, so you can launch the game with a wrapper. There's no official documentation on this (Volvo pls fix) but a bit of discussion on Steam's Linux github.
If you'd like to use libstrangle to limit a game's FPS in Steam, you could use it by entering strangle 60 %command% -dx9.
I would like this to be possible (and visible in the UI) for Bottles, too. To avoid confusion with familiarity, I propose that we'd use the same method Steam uses and replace %command% with the game's executable (or rather: with bottles' wrapper and the executable).
Alternatively you could use the command line to use a program to then run bottles which then runs an application, but that's not convenient and may confuse users who are less technical.
The text was updated successfully, but these errors were encountered:
This may be easy to implement. I'm currently trying to implement libwine in Bottles and there is an task that should help to achieve what you need: bottlesdevs/libwine#3 (extracted from bottlesdevs/libwine#2)
In Steam, you can use
%command%
to specify a prefix/suffix for launching applications.So if you like to run
hl2.exe -dx9
you can either input-dx9
or%command% -dx9
. This allows you to prepend launch options, too, so you can launch the game with a wrapper. There's no official documentation on this (Volvo pls fix) but a bit of discussion on Steam's Linux github.If you'd like to use libstrangle to limit a game's FPS in Steam, you could use it by entering
strangle 60 %command% -dx9
.I would like this to be possible (and visible in the UI) for Bottles, too. To avoid confusion with familiarity, I propose that we'd use the same method Steam uses and replace
%command%
with the game's executable (or rather: with bottles' wrapper and the executable).Alternatively you could use the command line to use a program to then run bottles which then runs an application, but that's not convenient and may confuse users who are less technical.
The text was updated successfully, but these errors were encountered: