Launch options not working for Source 2013 Multiplayer Mods

[amogan]

Since today (30th) launch options when starting from the Steam GUI don't work for Source SDK Base 2013 Multiplayer mods anymore. This may affect other SDK versions as well but I have not tested any. It works fine for the base game itself, just not on mods using it.

Tested on Windows 7 and 8.1, multiple machines.

Addendum: It works when you start the mod from outside Steam, for example with "steam.exe -applaunch 243750 -game <mod>" or via the hl2.exe. However when you do it through the steam.exe with "-applaunch" then it additionally adds any launch options you have set in Source SDK Base 2013 Multiplayer.

[Andi]

Can confirm, doesn't work on windows 8.1 either

[Tev]

As said here:
http://steamcommunity.com/groups/SteamClientBeta/discussions/0/360670708787404548/

It doesn't work for me when I played TIS Redux nor its 3rd episode which are both Source SDK 2007. Both me (Windows 10) and a friend of mine (Windows 7) have this issue, and can confirm the overlay previously worked on those.
EDIT: I don't know what I'm talking about.

[amogan]

Originally posted by Teutep:

... the overlay ...

This thread / bug report is about launch options, not the overlay. :)

[Tev]

Yeah, that's what I get for posting without coffee.

Took another look and d'oh. :) I'll strike it out.

I'd try the launch options, but I don't know which TIS Redux / The Intern's Story Part 3 would even support. -console; -novid and +fps_max 61 don't seem to trigger anything, but that might be normal with those games.

[amogan]

It works when you start the mod from outside Steam, for example with "steam.exe -applaunch 243750 -game <mod>" or via the hl2.exe. But when you do it through the steam.exe with "-applaunch" then it additionally adds any launch options you have set in Source SDK Base 2013 Multiplayer.

[Thundercracker]

Glad I'm not the only one, but this has been a problem for sooooo long. I can confirm that it's not working for Source SDK Base 2006 and 2007 games.

I tried your work around amogan but it will only launch Source SDK Base 2007 and if I want to change game to my mod "fas" it doesn't work because it's in another folder (steam/steamapps/sourcemods). Is there a way to change directory or specify the directory in command line?

When I use this in the target of my shortcut:

"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 218 -game fas

it throws the error "Setup file 'gameinfo.txt' doesn't exist in subdirectroy 'fas'. Check your -game parameter or VCONFIG setting

***UPDATE***
I just copied my fas folder to
C:\Program Files (x86)\Steam\steamapps\common\Source SDK Base 2007\
and now it works... this is not the most ideal solution but yeah... maybe third source mods are moving to the common folder just like with HL1 (goldsource).

[amogan]

You'll need to supply the absolute path to your mod e.g. "C:\Program Files\Steam\steamapps\sourcemods\fas" for <mod>. It has always been this way as far as I remember. Sorry I didn't mention that.

[Fatso]

I...don't get it(sorry if i sound like an idiot)but,where do i type "steam.exe -applaunch 243750 -game"?And where do i find "hl2.exe",it's not in the mod that i'm trying to add launch options to,and also since i'm trying to add launch options to a Source SDK Base 2006 mod,do i have to change 243750 to another number?

[Thundercracker]

Okay guys it seems the latest steam update changed things around. If you want mod specific launch options then you still need to make shortcuts as has been discussed before, however, the thing that got changed or "fixed" is that any launch options you put for your SDK Base, will be launched for the mods that are running on it. For example, I run Firearms: Source 2.0 (FA:S 2.0) on Source SDK Base 2007 and if I go to Library -> Tools -> Source SDK Base 2007 -> Right click -> properties -> set launch options, then what ever I put in here will be exected for FA:S or any other mod that uses this base such as Goldeneye: Source. If I go to Library -> games -> Firearms: Source 2.0 -> Right click -> properties -> set launch options, these launch options will still be ignored.

[Thundercracker]

To Fatso. I think you may be confused as to what to do. You don't actually have to mess around with "hl.exe", steam will do that for you if you just supply the appid. Now there's the important question, what appid do I use for SDK Base 2006? That's answered here (215):
https://steamdb.info/app/215/

Okay so, Fatso, assuming you know how to make a shortcut in the first place then follow these steps for your mod:


1. Get the full path for your mod, e.g. for me it was -
"C:\Program Files (x86)\Steam\steamapps\sourcemods\fas"
Let's call this string of text <mod> as amogan did already (don't forget that the quotation marks are needed).


2. Open up your shortcut properties and fill in the following for the "Target:" -

"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 215 -game <mod>

NOTE: you may use a different directory for your steam.exe e.g. "C:\Program Files\Steam\Steam.exe" and remember that <mod> is the string of text we obtained in step 1.
Put any launch commands you want after all of this, inside the target.
e.g for me I filled in:

"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 218 -game "C:\Program Files (x86)\Steam\steamapps\sourcemods\fas" -windowed -noborder

NOTE: I use a different appid (218 for SDK Base 2007)


3. In your shortcut properties fill in the "Start in:" field -
"C:\Program Files (x86)\Steam"
NOTE: you may use a different directory for your steam.exe e.g. "C:\Program Files\Steam\Steam.exe"


P.S. Thank you amogan for giving us that extra detail about the path of the mod, very useful/helpful.

[Fatso]

Originally posted by Thundercracker(AUS):

To Fatso. I think you may be confused as to what to do. You don't actually have to mess around with "hl.exe", steam will do that for you if you just supply the appid. Now there's the important question, what appid do I use for SDK Base 2006? That's answered here (215):
https://steamdb.info/app/215/

Okay so, Fatso, assuming you know how to make a shortcut in the first place then follow these steps for your mod:


1. Get the full path for your mod, e.g. for me it was -
"C:\Program Files (x86)\Steam\steamapps\sourcemods\fas"
Let's call this string of text <mod> as amogan did already (don't forget that the quotation marks are needed).


2. Open up your shortcut properties and fill in the following for the "Target:" -

"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 215 -game <mod>

NOTE: you may use a different directory for your steam.exe e.g. "C:\Program Files\Steam\Steam.exe" and remember that <mod> is the string of text we obtained in step 1.
Put any launch commands you want after all of this, inside the target.
e.g for me I filled in:

"C:\Program Files (x86)\Steam\Steam.exe" -applaunch 218 -game "C:\Program Files (x86)\Steam\steamapps\sourcemods\fas" -windowed -noborder

NOTE: I use a different appid (218 for SDK Base 2007)


3. In your shortcut properties fill in the "Start in:" field -
"C:\Program Files (x86)\Steam"
NOTE: you may use a different directory for your steam.exe e.g. "C:\Program Files\Steam\Steam.exe"


P.S. Thank you amogan for giving us that extra detail about the path of the mod, very useful/helpful.

Thanks!
But now for some reason the launch options are working for mods,BUT,you need to add them into the launch options of the required Source SDK version of the mod