New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bypass Launcher causing tweakscale error. Cause and workaround within. #269
Comments
I have some bad news. With the However here is the Player.log Remember this is with moving the dlls out of D:\Steam\steamapps\common\Kerbal Space Program\GameData\TweakScale\Plugins\PluginData and into Plugins except for Scale_Redist.dll which thinks there's two instances of it if I do so. |
Humm… Interesting…
The DLLs are not being loaded correctly. You somehow fooled the Assembly Loader/Resolver into loading something, but this something wasn't loaded at all. Please install TweakScale as it should and run another Player.log. I want to see what's really happening . |
Still more weird, found the problem on loading Icons. It's not "file not found", it's really "Invalid Content", as the file were damaged…
|
Hunmm… doing some more analysis on the Player.log: This appears to be alright:
But this is where things get weird…
The I think they are patching the game at runtime…. |
(Bypass Launch Option used) Heres the KSP.log from the PDLauncher folder as you suspected it would be (from the KSP forums) |
(Bypass Launch Option used) Heres the KSP.log from the PDLauncher folder with tweakscale and the recall mod correctly installed. KSP.log |
(Launcher used as designed) Heres the KSP.log from the KSP main folder with tweakscale and the recall mod installed correctly |
Note the That might be what is redirecting the ksp.log to D:\Steam\steamapps\common\Kerbal Space Program\PDLauncher\ when the launcher isnt actually running. I wonder what would happen if the folder was completely removed. Oh. Interesting. I removed the PDLauncher folder. Ran it with the bypass and it came up with an error that a necessary executable is missing being D:\Steam\steamapps\common\Kerbal Space Program\PDLauncher\launcherpatcher.exe |
Then I removed the bypass and deleted PDLauncher and then ran and it did the same thing. KSP_x64.exe D:\Steam\steamapps\common\Kerbal Space Program\PDLauncher\launcherpatcher.exe |
On REDDIT, it was found that moving the GameData into PDLauncher will "fix" the problems. I didn't tested it, I will have a Windows machine available soon and then I will double check the stunt. I'm working on the new KSP.logs now. |
Oukey, here we go: (Bypass Launch Option used) This is with my movements of the DLLs.
(Bypass Launch Option used) Heres the KSP.log from the PDLauncher folder with tweakscale and the recall mod correctly installed.
(Launcher used as designed)This one shows not problems, TweakScale was fine. I think you switched some KSP.log!
In a way or another, the message passed trough. PD apparently is going to lockdown KSP 1 too, they are virtually locking everything out by using a new GameData subsystem. |
This is a dump of the commandline arguments passed to the executable. This clearly demonstrates that they are using a feature already present on KSP since 1.12.3 at least (as I have a report of KSP 1.12.3 with the same problem). In a way or another, the move is clear. Or someone at PD made a marvelous screw up, or they are going to lockdown the KSP1 ecosystem the same way they said they are doing with KSP2. |
I have gone to some wrong conclusions in the past. Lets wait to see. So... "D:\Steam\steamapps\common\Kerbal Space Program\KSP_x64_Steam" %Command% -popupwindow Log Files for the test (all tests before and this one were just loading KSP and going into the SPH and increasing/decreasing the size of a MK2 cockpit and leaving to the main menu and exiting) |
So do I.
Of course it works, we had already diagnosed the problem, being it the PWD being wrongly set. That remains to be understood is WHY the problem happened at first place. Not to mention that only a minority of the users will be going to the extra step of creating a shortcut and then using it to launch the game. Who configured Steam to misbehave like this at first place? |
Yeah True. Could have been done on purpose to stop people from bypassing the launcher in steam? |
I doubt it, but can't rule out neither. I have experienced some asinine moves from Squad in the past, but they are really uncommon - most of the time is an unfinished attempt to fix something that were hurried up into production without proper testings. Squad had done some really bad decision making in the past, and right now we have our "friend" GT reproducing some of these bad decision making on the modding scene. I didn't bashed him on Forum just because. If you care to search our past interactions (including here on github) you will see why I completely despise (most of) his interventions (besides agreeing that he is able to accomplish good things - what's end up contributing to my lack of patience with him: he can contribute positively if it's what he wants, so the logical conclusion is that he does what he does on purpose). |
I am not touching the topic of your interaction with him haha. Just talking about how to bypass the launcher could be pissing off people at Intercept Games/PD/Squad which I really didn't want to do. I just added the shortcut technique to a bug report someone did talking about the lack of ability to use -popupwindow with the new launcher....They are going to haaattteeee me now. |
Ouch! :D Ok!
Your guess is so good as mine at this point. If we imagine that our friend GT works for them somehow, then we can assume they are not happy at least to me. In a way or another, the only way to know is by doing it.
And, to tell you the true, I think the Steam Overlay will also be lost - but I will check it later. Can I close this issue so? |
Closing sure. We have gone as far as we can with this right? |
My nose thinks we had! :D Cheers! |
In a way or another, this is a follow up from what will be done about: |
@Lisias The issue with the bypass for the launcher in 1.12.4 is that it cant see the dlls in the PluginData (D:\Steam\steamapps\common\Kerbal Space Program\GameData\TweakScale\Plugins\PluginData) folder
Remove all files except for Scale_Redist.dll and put them into the Plugins folder
Showing the launch bypass on steam
An additional problem is that while the bypass for the launcher is being used is that that the mod cant see the icons in the \GameData\TweakScale\PluginData\Icons folder and its showing the error as per the screenshot
The text was updated successfully, but these errors were encountered: