Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Short answer: No. It just doesn't work like that. The only one responsible to what applies to game launch options is the steam client.
Long answer:
Wrappers wont work as they target process and children threads, but children or friendly processes run on its own, windows games on linux always bring up a wine process, native linux games have its own executable.
Environment variables may work depending on Steam internal implementation. If steam is running games on a separate shell, or pushing and clearing the environment variable stack, then those wont be inherited into a children process.
It is dependant on what launch options are available on a per game basis as set by the developer.
For example on Windows you may need to edit an ini file to add parameters such as directx switch to 9, a resolution not available via the in-game settings etc.
This mostly don't apply to windows. Environment variables for linux are applied on launch basis per process. There are games not working, as well as hardware performing poorly if some flags are not set up. It is cumbersome to do this for every single game you install, every time. Same with process wrappers. See "Who is this useful for" section. Also check the screenshot for two good examples of variable + wrapper available for all games/processes in linux.