Try adding `env --` in front of the command option. e.g. ``` env -- MANGOHUD=1 %command% -force-d3d12 ```

... env --` in front of the command option. > > e.g. > > ``` > env -- MANGOHUD=1 %command% -force-d3d12 > ``` I can confirm ...

... I confirm that `MANGOHUD=1 %command%` is working as expected. In the experimental steamrt3c-based client it now ...

... Since yesterday's beta client update, a workaround is to use `env -- MANGOHUD=1 %command%`.

... on paper), but environment variables (examples: `gamescope` and `MANGOHUD=1`) are unable to be used in Steam RT3 ...

... for now. `NODEVICE_SELECT=1 ENABLE_VKBASALT=0 MANGOHUD=1 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia gamemoderun %command%`

... options after %command%, my launch options are now these ``MANGOHUD=1 MANGOHUD_CONFIG=fps_only STEAM_COMPAT_RUNTIME_SDL2=classic %command% -novid -nojoy``

... MANGOHUD=1 MANGOHUD_CONFIG=fps_only SDL_VIDEODRIVER=x11 %command% -novid -nojoy ``` Environment variables need to be before the `%command%`, and ...

... The workaround is to use launch options like `env -- MANGOHUD=1 %command%` instead. This regression is tracked in ...

... if your launch options look like `FOO=bar %command%` (for example `MANGOHUD=1 %command` or `PROTON_LOG=1 %command ...

... add the mangohud command %command% or MANGOHUD=1, or MANGOHUD_DLSYM=1 in the games, and the information still ...

... 4ead-a1f2-5cb7e63677f9) ### Software information I use Orginal Command & Conquer 3 DVD from ~2007 update 1.9 patched ...