Launcher Zip File Download
Kam Bergmann
Can anyone help me with why the App Launcher in Portal (v10.7) does not show the apps and/or tools that come with a subscription? There is a long list of "Essential Apps" bundles but I am unable to add them to the launcher. Anyone else have this problem? I have found it may have been a bug in earlier versions but no documentation for 10.7. Thanks!
Same problem. Kaspersky Lab launcher 30% CPU usage. Try switching it off and on again. So go to KIS settings, click on File Anti-Virus, make sure Security level is Optimal, turn File Anti-Virus off, save, confirm. You will receive warning notifications. Turn File Anti-Virus back on, save, confirm. Kaspersky Lab launcher should now be using 0 to 0.4% CPU usage.
This is just a wrapper launcher for Kerbal Space Program steam installs to bypass Take Twos KSP2 oriented launcher. Fully passes steam command lines to the KSP exe (unlike Take Twos) and properly sets up the working path, source code is here for all to view. Releases are here:
yeah I went with the newest .net core version because it has linux/mac support. Ironically, it doesn't help much/any because there are no linux/mac builds of this launcher yet (as it is unaware of their executable names), so need to either
Just thinking outloud. Anyone know if the *nix builds ship this new launcher gizmo? If it doesn't then why am I bothering lol? If it does, what's the executable names of the launcher and main game binary there?
Remove the dumb launcher. it degrades performance as well as my faith in the company to do well by its customers. Whoever on the KSP community team reads this: Go back to Take Two, tell them their forced bloatware aint working out with this title, and get rid of the thing.
You can run the game without the launcher. KSP_x64.exe from the game's directory runs just fine. For convenience, you can create a shortcut to it or even add it to Steam under Games->Add a non-Steam game... option. It seems to work just fine this way. A bit crap that PD is trying to push this, but so long as the game keeps working without the launcher, I consider it a minor annoyance rather than a barrier.
The launcher has not been proven to do anything to affect the game negatively. Why would they remove it just because "you don't like it"? There really is no arguing against someone making a plain complaint. I think the launcher is nice and should stay, it's an easy place to provide feedback to the developers without having to go to some other platform where it might not be read.
A launcher has been in the game since as long as I remember, it's just been broken in almost every version. I think what's new here is that the launcher is on Steam. I don't play KSP on Steam, but I can see that being annoying, even if there are ways around it.
Nobody liked the launcher when it was first introduced, way back when. At which point it was OPTIONAL and you could simply start the game without it. Not sure if that's still possible with the Steam version, but with the regular version it is.
There's absolutely NO NEED for that bloody launcher (or indeed for any launcher) except as a marketing tool and/or to force the player to log in on some account to be able to access their game (useful for MMOs, not for single player games unless you're going to introduce item malls. Looking at you Take-Two, EA, Ubisoft, Blizzard, et. al.).
Plenty of people dislike it simply for the fact its completely redundant in every way possible, is that not valid enough reason?
Plenty of people hate it because of the company associated with it and potential data collection routes.
Let the reviews speak for themselves, unless this launcher is mandatory for functionality in the sequel (in which case its still redundant for KSP1) most will not like it, myself included. For Jools sake i even reactivated my old KSP forum account just for this issue specifically.
It does tho. It breaks modded games. Even with circumvention it seems to bug out some mods in weird ways. They beleive the folder for the launcher is the "root folder" of KSP and store configs etc... in a gamedata folder they make inside the launcher folder. It is very strange and Im seeing more errors than usual Even with a custom install location where I litterally use commands on steam to launch from a custom location. I have my game on a seperate drive than where steam installs it.
Using the luanch parameters to make steam launch from the custom location. Yet mods are making a "gamedata" folder inside the PD launcher folder in the steam install location. Steam install does not even have the mods nor is what steam is launching. So why is this happening? It seems the new steam setups to make this launcher work is doing weird things to the way the game runs. I am now forced to launch the game without steam. Which means I loose my FPS counter, steam screenshots and the steam playtime counter.
Fixed the problem with this post. No longer an issue. And again. Before now these mods wouldnt have this problem. The launcher introduced a change that these mods didnt take into consideration, basically breaking them. And since this problem is now on all versions of the game. Proper workarounds needs to be found as older versions of mods may not be updated to solve this.
Here is the solution
This is where to locate the three types of log files. The ones called Launcher_log.txt, Launcher_log(old1, 2, 3, etc).txt are for the launcher. The ones called log.txt, log(old1,2, 3, etc).txt are the game app log files. We may want those too for good measure.
Since we have quite an extensive pipeline already developed around using an in-house launcher (for better or worse), it would be a massive pain to try and get everything working using Shotgun Desktop.
If you are using the old shotgun config, you would just change the paths.yml to a path to your program_launcher.py
If you are using the new config2 then you could easily change the windows/linux/mac paths to your launcher.py paths.