Anth

For some reason KSP.log isn't generated while the launcher bypass is in place. I added player.log instead and indicated the line where it mentions the icon issue. Texture/jpg compression issues are typical entries in the KSP log for some reason even without mods. No idea why or if they are a real issue or not.

Chill please. I am only here to help. I don't actually use the mod at all. In fact I don't even use steam for KSP usually. Its only purpose is so I can copy it out to another folder. My only goal was to figure out why mods aren't working with 1.12.4 when there's nothing in the patch notes that indicate any mod related changes. I have 20 or mods. None of them were affected by bypassing the launcher as far as I can tell. There are multiple people complaining about issues with 1.12.4 which appear to be mod related. I was just trying to figure out what was going on so I could get a bug report out asap. Lets hope that KSP2 modding wont be as annoying as you have been experiencing. Not sure if this is relevant because I only run on PC but I have KSP on GOG (minus the DLCs) as well as steam. On GOG the pdlauncher is missing from 1.12.4.

Well do note that moving the dlls did actually work when moved. KSP did see them and I could use TweakScale in the SPH and in the craft worked in scene, but I have very little modding experience so I don't know how that could cause issues elsewhere.

@Blufor878When using a bypassing the launcher tweakscale cant see the dlls in the correct location. It appears to work when the bypass isn't being used. The bypass is something put into the steam launch command line Now all I need to do is put it all together for @Lisiasin the github @Lisias https://github.com/net-lisias-ksp/TweakScale/issues/269

@LisiasTry moving all the dlls from the \TweakScale\Plugins\PluginData folder and put them into the Plugins folder except for Scale_redist.dll? So less mods are working maybe.

Yeah I just found the same thing. I compared the log of without the bypass and to one with the bypass. Why tweakscale cant see the DLLs I dont know. I am reinstalling KSP 1.12.4 with just the tweakscale mod to see if I can figure it out without any other mods.

SHADOWS_FLIGHT_PROJECTION = 1 SHADOWS_KSC_PROJECTION = 1 SHADOWS_TRACKING_PROJECTION = 1 SHADOWS_EDITORS_PROJECTION = 1 SHADOWS_MAIN_PROJECTION = 1 SHADOWS_DEFAULT_PROJECTION = 1 Find all of these in the settings.cfg file and make sure they are all set to 1

@Lisiasso is there a problem with tweakscale or not? I have been trying to break 1.12.4 with my mods and nothing is working. Well to be clear, the mods I used for 1.12.3. Not my mods.

First Issue: I can't replicate. Second Issue: It's caused by the "Add Burn Time to Margin" option. If selected it somehow changes the time to the first maneuver node instead. I agree, that should be an easy fix.

@karazak Can you send me a copy of the ksp.log file via a private message? You aren't the only one with problems. My KSP is good. But others have been complaining.

Well be warned the launcher is on all versions of KSP now.

Here's a few easy fixes or work arounds that could be put into a patch update without too much effort: For a clean install of 1.8 and above the shadows show up as bands across the ground. Also the shadows are shimmering when they shouldn't be. The simple fix is in the settings.cfg file. Some of the settings are set to zero when they should be set to one. In 1.12 wheels slide down hills. This includes the landing legs. For wheels we can access the friction control and increase it until the wheels stop sliding however the landing legs doesn't have friction control for the action menus because of one setting in the config files for them. This can be turned on quite easily. Its not a fix but its an extremely simple work around that doesn't mean digging into the code and doing lots of testing. Does anyone else know of really small little problems like above that could have really easy fixes?

Remaining bugs? KSP1 has 100s of them The launcher just takes up hard drive space if you are bypassing it. And they did fix the tutorials and some stock alarm issues

Ok lets say that the launcher doesnt exist. Then KSP2 will be advertised in 3 places: https://www.kerbalspaceprogram.com/ Steam: The KSP1 news page (where we click above to start KSP1) Steam: The KSP2 store page We as KSP1 players can avoid all three even if we use steam by using the shortcut on the desktop (windows) The Launcher allows two things: Constant advertising to the KSP1 player even if they use the shortcut each time they use KSP1 as long as its connected to steam. The advertising can be modified, added, removed etc without having to change the code of KSP1. Benefits to KSP1 players having the launcher: Seeing the progress of early access to determine when they want to buy it up to when KSP2 1.0 is released Seeing how early access is going just from an interest level. If you really want to stop the launcher from running the easiest way is to create a shortcut directly the KSP executable (avoids steam entirely) and put that on your desktop. Its not that big a deal.

Right Click on Kerbal Space Program in the left menu of steam and then click on Beta. Then change to 1.12.3. It wont stop the launcher but the previous version will be restored.

What if you change the version to 1.12.3? This could be a mod incompatibility problem (though I have no idea what in the update could have caused that)

That's the second complaint of decreased performance that I have seen. I wonder what could be causing that

Indeed. However this is more directed towards Squad/Intercept Games than us. If they want us using the new launcher then it needs to have -popupwindow working. I have your technique in the following post (last entry):

@karazakIf that doesn't work I recommend changing the version to 1.12.3 which you can do in the Beta tab of the properties of KSP on steam Right Click on Kerbal Space Program and select Properties. then choose the Beta Tab and use the drop down menu. It looks like the following:

I have a semi fix for it @Vl3d Search for the following files in the KSP Folder landingLegLT-1.cfg landingLegLT-2.cfg landingLegLT-5.cfg Open each file and search for autoFrictionAvailable and change it to True and then you will be able to change the friction like you can with wheels with the action menu. Its not a 100% fix but it gives you 100% control over the issue. Can't remember the name of the person who figured it out. Look to the following link (click on the title): Look at the last post I did. Its a fix for another issue but also will remove the launcher but will keep KSP linked to steam.

-popupwindow caused KSP1 to be able to be borderless before 1.12.4 Putting this into Steam (like the below screenshot) no longer works because the KSP application is blocked by the launcher. Link to bug report: https://bugs.kerbalspaceprogram.com/issues/28671

Oh. The new launcher blocks the -nopopupwindow command from getting to KSP. I always use this because I want the window to stay up when I use my other monitor.

Here is another way to fix it and have steam work: "D:\Steam\steamapps\common\Kerbal Space Program\KSP_x64.exe" %Command% -popupwindow Replace the bolded type with your personal path. -popupwindow makes it borderless. It can be removed if you don't need it that way. Put that into the following window in Steam (right click on Kerbal Space Program in steam and click Properties): Note the %Command% must be in there or it won't work. This does bypass the new Launcher. If you want that to be working use the following substituting your path: "D:\Steam\steamapps\common\Kerbal Space Program\PDLauncher\LauncherPatcher.exe" %Command% Note that -nopopupwindow doesnt work with the launcher if you use it.

I created a post here for that issue. There are two work arounds in there to counter that issue. I think I have another too I can add which does also remove the launcher from startup.

That wasn't the main reason for doing the update. The launcher is. Its for advertising purposes for KSP2