Properly Circumventing The Launcher

[Zefnoly]

I stil had a few issues circumventing with the way everyone was doing it. Even with my game at a custom install location, variouds mods would generate "gamedata" folder inside the original PD Launcher folder storing configs there. Causing various problems.

This is because steam would make the game think of that as the root folder for the executable even if you used commands to launch from elsewhere.

You need to make steam launch parameters refer to a shortcut of the exe file instead of the exe file directly. The shortcut contains the information about where the game should run from, like what should be considered a root folder.

As explained in this specific post on the official forums:
https://forum.kerbalspaceprogram.com/index.php?/topic/210409-how-to-bypass-the-new-launcher-added-in-update-1124-steam/&do=findComment&comment=4195798

Gonna copypaste the explanation here to do it properly this time.

Originally posted by Gotmachine:

- Open your KSP root folder (In Steam, right click on the game > Browse local files). Usually this will be "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program".
- Right-click on KSP_x64.exe > Create shortcut
- Rename the shortcut to "KSP_x64_Steam"
- In Steam, open the game properties, and in the "Launch Options" field, put the path to the shortcut between quote, with :

"C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_x64_Steam" %command%

Additionally. If you want to keep the PD launch folder empty and want the PD launcher gone entirely. You need to make a new empty textfile. Make it an EXE file and name it the name of the PD launcher exe. This will tell steam the launcher stil exists. But let you have the folder empty with no risk of the launcher persisting at all if you want to go the extra step. The reason you cant delete it entirely is because steam will check if the exe file exists, and will prompt an update of the game if it finds it missing.

[Operation40]

yes! finally something that works with mods
the shortcut is clever, cause it sets the "starting location" to the correct folder

thanks!

[DumpsterFire]

Easiest way was to uninstall lol After they installed Redshell Spyware onto our systems, im not trusting this launcher not to be malicious. Private Division isnt trust worthy

[Thaurane]

Or... use one of the many bypasses for the launcher found and continue to enjoy the game.

[Zefnoly]

Originally posted by Thaurane:

Or... use one of the many bypasses for the launcher found and continue to enjoy the game.

Which bypasses would that be? Cuz this is one of them that prevents mods from breaking. Other bypasse ive seen only bypass launcher, but does not solve the issues with mods...

[Dedelblute3]

I literally just ended task on task manager. Hasn't closed KSP yet.

[Manwith Noname]

Originally posted by Zefnoly:

Which bypasses would that be? Cuz this is one of them that prevents mods from breaking. Other bypasse ive seen only bypass launcher, but does not solve the issues with mods...

Options and alternatives:

1) Run the game directly from the executable bypassing Steam completely.
2) Add the KSP executable as a non Steam game and run it from there.
3) Use tools or manually edit the appinfo.vdf file to remove the launcher from the play button.
4) Probably something else.

Though the comment was most likely in response to the person who said the solution was to uninstall.

Edit: I don't suggest people try to edit the appinfo.vdf manually but it can be done.

[Toastie Buns]

Originally posted by Manwith Noname:

2) Add the KSP executable as a non Steam game and run it from there.

This is the easiest and quickest method, surprised it's not mentioned more

[Manwith Noname]

Heh, it was one of the first responses I made when the game updated but some people really want to keep tracking their play time or keep their screenshots attached to the same library.

I've got a vague feeling you can probably game the system by naming your non Steam game "220200" or ensuring it accurately matches the configured name for the game but I don't know for sure if it works as I have never tried it in this context. I have done this for other games when trying to workaround issues with Steam Controller configs. Then again, turned out the best solution for that was opting in to the Steam Beta where "it just works".

[Backroomshoe289]

What a mess. None of this should be required for an 11 year old game. Jerk move.

[Toastie Buns]

Originally posted by Manwith Noname:

or keep their screenshots attached to the same library.

When I used to do it, I'd just replace a random screenshot using the screenshot manager, changing the file name to match whatever I'd replaced.
Because I was lazy, I would often not do that, instead it would be uploaded as the non Steam game title, which was "Kerbal Screenshot Program" and I'd occasionally get messages asking how to get the screenshot program when posting pictures to a thread

[GunsForBucks]

Just for info sake... this option disables broadcasting being seen by steam. You can broadcast to yourself but the ID loop to make it show up on the broadcasting page for public seems to not work.

I went back to the .exe one for full functionality of steam features.

[Zefnoly]

Originally posted by GunsForBucks:

Just for info sake... this option disables broadcasting being seen by steam. You can broadcast to yourself but the ID loop to make it show up on the broadcasting page for public seems to not work.

I went back to the .exe one for full functionality of steam features.

Although this breaks mods as they will think the PD Launcher folder is the root folder for the game. It works fine if you are vanilla but many mods do not like it. Even KSP will behave strangely storing log files etc. inn there...

[Manwith Noname]

Yeah, I kinda felt like even the vanilla game might start throwing files there. Potentially things like craft and saves too.