KUAR Posted June 30, 2023 Share Posted June 30, 2023 It appears so, lots of moans about it above. Doesn't really bother/affect me but I appreciate that for some people it's one step too many. Quote Link to comment Share on other sites More sharing options...
munix Posted June 30, 2023 Share Posted June 30, 2023 (edited) 3 hours ago, Matt Lowne said: Did this hotfix remove the ability to launch KSP 2 directly from the .exe file, forcing us to use the PD launcher? I can no longer launch the game via the .exe, it just loads the PD launcher instead. Yep, it definitely did. One workaround seems to be to take the KSP2_x64.exe file from 0.1.3 and replace the current one with it (credit to @schlosrat). 2 hours ago, KUAR said: It appears so, lots of moans about it above. Doesn't really bother/affect me but I appreciate that for some people it's one step too many. It might not affect the average user too much, but for us modders who might launch the game like 50 times per day when working on a mod and testing it, it's an extremely annoying change, to the point that multiple modders already said they won't continue their work until this is gone. Edited June 30, 2023 by munix Quote Link to comment Share on other sites More sharing options...
Norantio Posted June 30, 2023 Share Posted June 30, 2023 Thanks for the DRM Quote Link to comment Share on other sites More sharing options...
schlosrat Posted June 30, 2023 Share Posted June 30, 2023 (edited) 37 minutes ago, Norantio said: Thanks for the DRM @Norantio, you don't have to put up with this, there is a very simple fix. I posted about it on the 0.1.3.0 thread but really should have posted about it here. If you don't happen to have a copy of the 0.1.3 game on your machine I believe there's a way to use Steam's beta access to get a previous version that way. I was fortunate in that I normally have several copies of the game on my machine for different purposes (unmodded for bug reporting, modded for playing, and modded with debug for development), but if you don't and you got your game from Steam you may want to look into pulling down a copy of 0.1.3 just so you can get the Ksp2_x64.exe launcher from it. @DfA-DoM reported that apparently if you got the game from the PD store it doesn't do this. I've no way to confirm that other than to buy another copy of the game, and it's frankly surprising, but perhaps that's also a way to get around this. Edited June 30, 2023 by schlosrat Quote Link to comment Share on other sites More sharing options...
Spicat Posted June 30, 2023 Share Posted June 30, 2023 12 minutes ago, schlosrat said: @Norantio, you don't have to put up with this, there is a very simple fix. I posted about it on the 0.1.3.0 thread but really should have posted about it here. If you don't happen to have a copy of the 0.1.3 game on your machine I believe there's a way to use Steam's beta access to get a previous version that way. I was fortunate in that I normally have several copies of the game on my machine for different purposes (unmodded for bug reporting, modded for playing, and modded with debug for development), but if you don't and you got your game from Steam you may want to look into pulling down a copy of 0.1.3 just so you can get the Ksp2_x64.exe launcher from it. @DfA-DoM reported that apparently if you got the game from the PD store it doesn't do this. I've no way to confirm that other than to buy another copy of the game, and it's frankly surprising, but perhaps that's also a way to get around this. Okay, we had a discussion about this in the discord, apparently it's due to the fact that the .exe launch steam and thus launch the launcher (It didn't do that before): And apparently the steam command bypassing the launcher still works: "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program 2\KSP2_x64.exe" %command% I don't think it's intentional, but I will wait before an official communication to have an opinion about this. Quote Link to comment Share on other sites More sharing options...
Alexoff Posted June 30, 2023 Share Posted June 30, 2023 I won't be too surprised if the next patch adds the impossibility of bypassing the launcher with drm. Still, T2 is quite jealous of its games. Quote Link to comment Share on other sites More sharing options...
atomontage Posted June 30, 2023 Share Posted June 30, 2023 (edited) I also wonder why it isn't in the changelog. It is a change, right? Let me guess: to not make the crowd angrier, you decided to do it quietly. I also wonder why is this launcher even needed? I mean, you get the news from Steam. Right? What does this launcher has that Steam has not? We're tired of launching a launcher from a launcher. WE WANT TO PLAY GAMES. Edited June 30, 2023 by atomontage Quote Link to comment Share on other sites More sharing options...
Mitokandria Posted June 30, 2023 Share Posted June 30, 2023 1 hour ago, Spicat said: Okay, we had a discussion about this in the discord, apparently it's due to the fact that the .exe launch steam and thus launch the launcher (It didn't do that before): And apparently the steam command bypassing the launcher still works: "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program 2\KSP2_x64.exe" %command% I don't think it's intentional, but I will wait before an official communication to have an opinion about this. I was apparently already using this. That would explain why I didn't notice. Quote Link to comment Share on other sites More sharing options...
Davidian1024 Posted June 30, 2023 Share Posted June 30, 2023 4 hours ago, Matt Lowne said: Did this hotfix remove the ability to launch KSP 2 directly from the .exe file, forcing us to use the PD launcher? I can no longer launch the game via the .exe, it just loads the PD launcher instead. I don't think it did. Something may have changed, but I really don't think they did anything to force you to need to launch the game from the launcher. I say this because I'm on Linux, and I've been having to launch the game directly from the .exe for quite a while. After Valve updated Proton (the thing that let's us Linux gamers play Windows games) to version 8.0 the launcher started crashing. So, I simply can't run it from the launcher. Were people launching it outside of Steam? It could be that the latest version can't be launched directly outside of Steam. At least not without some effort. I'm essentially doing this: (mentioned by @Spicat) "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program 2\KSP2_x64.exe" %command% I want to mention that the above command should probably be this instead: (note the added #) "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program 2\KSP2_x64.exe" #%command% Otherwise %command% will be expanded to whatever command Steam normally runs to launch the game, and that will get passed to KSP2_x64.exe as parameters. Which will probably be ignored. But, just to be safe. In any case, I don't think there's anything nefarious going on here. Quote Link to comment Share on other sites More sharing options...
Scarecrow71 Posted June 30, 2023 Share Posted June 30, 2023 12 minutes ago, Davidian1024 said: In any case, I don't think there's anything nefarious going on here. I disagree. Player numbers have been dwindling for some time now, and the only counts that the company can get are through Steam (as there are no metrics captured for Epic or direct-download from the store). What better way to boost numbers than to force people back into using the launcher? Quote Link to comment Share on other sites More sharing options...
Davidian1024 Posted June 30, 2023 Share Posted June 30, 2023 Just now, Scarecrow71 said: I disagree. Player numbers have been dwindling for some time now, and the only counts that the company can get are through Steam (as there are no metrics captured for Epic or direct-download from the store). What better way to boost numbers than to force people back into using the launcher? But they're not forcing people back into using the launcher. Quote Link to comment Share on other sites More sharing options...
Periple Posted June 30, 2023 Share Posted June 30, 2023 Well done! I know hotfixes can be a hassle what with all the merging but kudos to you for getting this one out, and if you can make this a regular thing that would be real progress! Quote Link to comment Share on other sites More sharing options...
Anth Posted June 30, 2023 Share Posted June 30, 2023 Bug reported. I had @Zabbytelling me that the executable was running the launcher. I thought that's crazy until I saw steam respond to me double clicking on the 0.1.3.1 executable. I also bypass the launcher so I had no idea. Quote Link to comment Share on other sites More sharing options...
Redneck Posted June 30, 2023 Share Posted June 30, 2023 Why does this game even need a launcher? Quote Link to comment Share on other sites More sharing options...
Strawberry Posted June 30, 2023 Share Posted June 30, 2023 6 minutes ago, Redneck said: Why does this game even need a launcher? The answer is very likely take two mandate Quote Link to comment Share on other sites More sharing options...
Redneck Posted June 30, 2023 Share Posted June 30, 2023 6 minutes ago, Strawberry said: The answer is very likely take two mandate Well we will just have to remedy that now wont we? I WONT be apart of any data collection if that is what is happening here! Quote Link to comment Share on other sites More sharing options...
Anth Posted June 30, 2023 Share Posted June 30, 2023 8 minutes ago, Redneck said: Well we will just have to remedy that now wont we? I WONT be apart of any data collection if that is what is happening here! As long as they aren't taking my personal information I am fine with them taking all my game play data, system specs, logfiles. It all helps to make the game better. Quote Link to comment Share on other sites More sharing options...
RaBDawG Posted June 30, 2023 Share Posted June 30, 2023 On 6/27/2023 at 6:55 PM, Intercept Games said: KSP2 v0.1.3.1 Hotfix Release Notes Bug Fixes Flight Atmospheric Drag not correctly applied to capsule after decoupling [Original Bug Report] UI/UX Procedural fairing editor buttons overlap one another in VAB [Original Bug Report] SUBMITTING BUG REPORTS AND FEEDBACK If you'd like to provide feedback about this build, there are many different ways to do so: Submit Feedback through the Game Launcher Suggest a Change on the Forums Join us on Discord to discuss potential changes Bug reports should be shared to: KSP Forums Bug Reports <-- This rocket denotes an issue or change that community members directly helped by sharing or suggesting it to our dev team. Thanks to all of you who send in bug reports and suggestions! THATS IT?! Quote Link to comment Share on other sites More sharing options...
Redneck Posted June 30, 2023 Share Posted June 30, 2023 (edited) 4 minutes ago, Anth12 said: As long as they aren't taking my personal information I am fine with them taking all my game play data, system specs, logfiles. It all helps to make the game better. I am the opposite. I prefer to opt out or at least an option to do so Edited June 30, 2023 by Redneck Quote Link to comment Share on other sites More sharing options...
Davidian1024 Posted June 30, 2023 Share Posted June 30, 2023 I want to point out that it's possible that this could be due to recent updates Valve made to Steam. The Steam runtime could've contained an update that's causing this. I can say this much for sure. It's not that the Private Division launcher is being forced to be run. It's that the Steam Client is being forced to be run. Further, the PD launcher can still be bypassed. See @Spicat's comment on how to do that. Quote Link to comment Share on other sites More sharing options...
MechBFP Posted June 30, 2023 Share Posted June 30, 2023 1 minute ago, Davidian1024 said: I want to point out that it's possible that this could be due to recent updates Valve made to Steam. The Steam runtime could've contained an update that's causing this. I can say this much for sure. It's not that the Private Division launcher is being forced to be run. It's that the Steam Client is being forced to be run. Further, the PD launcher can still be bypassed. See @Spicat's comment on how to do that. I was going to say the same thing, given the recent steam updates. Using that same %command% workaround caused problems in KSP1 as a result of what directory it was looking at. I wouldn't be surprised if it causes problems now or later as well with KSP2. Quote Link to comment Share on other sites More sharing options...
cocoscacao Posted June 30, 2023 Share Posted June 30, 2023 Wait... Was this bug present only for decoupler + command pods? Were fuel tanks, engines etc affected? Quote Link to comment Share on other sites More sharing options...
kdaviper Posted June 30, 2023 Share Posted June 30, 2023 43 minutes ago, RaBDawG said: THATS IT?! That's all that was supposed to be in the hot fix unless I missed something Quote Link to comment Share on other sites More sharing options...
Anth Posted June 30, 2023 Share Posted June 30, 2023 Quote Link to comment Share on other sites More sharing options...
KSP2 Alumni Dakota Posted June 30, 2023 KSP2 Alumni Share Posted June 30, 2023 Yesterday's v0.1.3.1 Hotfix that was released on Steam accidentally included Steam's built-in DRM due to a misconfiguration on our end. KSP2 is DRM-free, just like KSP1. An update was just pushed Steam to address this. Sorry for the headache! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.