Bypass Steam Drm

[Consuela Ellett]

Isthere a way to bypass the steam launcher? My steam wont work anymore, and wont connect to the internet and wont let me play the game anymore. So is there a way to bypass steam to play the game again, or do i need to download a cracked version just because of this?

Well, before re installing it wouldn't connect to the internet, no matter what connection, what settings in my computer (disabled everything, firewall, antivirus, everything) And after re installing, it just wont update or connect at all, it will just say Steam main exception, To run steam you must first connect to the internet.

Go to the steam web site and instal steam VIA the internet download, you exe is corrupted, antvirus tagged it ,you did say it was running, correct? so uninstall it, browse to steams network and reinstall it from there, I know that works for sure, and you do not need any games to install steam.

First off, try following luthien's advice. But before re-installing, run the registry cleaner in CCleaner (if you don't have CCleaner, just download it) to clean out any potential remaining keys from New Vegas in your Registry - just to be certain.

Ok, apparently it was something weird with a steam update. I cant still play normally but steam seems to be working. For some reason the only way to play the game is installing it in another folder, and use FMM to launch NVSE.

With the latest 1.12.4 update, SQUAD / Private Division decided to introduce an additional launcher to the game which will start up after hitting the "Play" button in Steam instead of launching the game directly. IMO this is rather annoying and doesn't provide any actual benefits, in fact, it actually causes some trouble especially for mods.

Since the update, me and others figured out multiple ways to circumvent the launcher which come with their own benefits and drawbacks, so here are a few for you guys to choose from, depending on which solution fits the best for you

@R-T-B wrote this wrapper which replaces the original executable of the launcher. Simply replace the "LauncherPatcher.exe" provided by them with the one from the stock game and you're already done and ready to go.

Steam allows to setup individual launch options for each game, which can be used to redirect the target for the "Play" button in your Steam library. This particular solution by @Gotmachine redirects the button to point to a shortcut, which then again points to the game executable:

Doing that will have the side effect of having KSP running from the wrong working directory.

In stock KSP, the only likely side effect will be that the KSP.log file will be generated in the "PDLauncher" directory, but this will definitely cause cascading side effects on various mods.

So, this was the solution I came up with like an hour after the update but which turned out to be problematic later on. Works in the same way as the previous solution but instead of redirecting the "Play" button to a shortcut, it gets redirected to the games executable:

The window is not resizable to show the full command but I guess you get it If you are having trouble to find the path to your game executable, you can right click the game in your library -> "Manage" -> "Browse local files". This will open up a window with your game files, showing the path at the top navigation bar.

This is basically a combination of solution #2 and #3 but instead of redirecting the "Play" button to the game executable or a shortcut of it, it gets redirected to the windows command line (CMD) which then is used to launch the game. Choosing this solutions allows you to eliminate the drawback of missing steam features from solution #2.

Normally, in the KSP directory, there should be two executables: KSP. and KSPLauncher. .

Steam now launches KSPLauncher.whatever . To get rid of the launcher, the only thing to do is to find where the path to the executable is stored within Steam and replace KSPLauncher.whatever by KSP.whatever .

I hope everyone was able to find a solution which fits bets for their situation but if not, you're always welcome to ask questions right here in the thread. If any other solution comes up to fill up a niche, I'll happy add it to the list, same goes for linux and MacOS versions of the game. Also, any feedback is always welcome

2 cruisers, 1 frigate, 1 corvette and a starfighter still lag to the point that its borderline unplayable (and i dont even wanna know what would happen if i opened fire and the game had to render all the cannon trails/explosions/parts being shot off)... That and not all of my mods work either, at least the super critical stuff works...

@panzer1bAre you sure you wanted to post that here instead of the update announcement thread?

And as far as I have read, the update never claimed to improve performance, just some bug fixes for tutorials and clock, as well as adding this rather unwanted launcher.

ah, different platforms different executable names. Fun. I could make my bypasser program fire an external editable script file, and then maybe it could be used to defeat a variety of launchers that just launch another executable. That's not a bad idea actually.

Worst. KSP itself will start to look for and save files on the wrong place - while this ordeal were being diagnosed on my side, it was found that KSP.log was being written inside the PDLauncher's directory. I didn't further tested this, but I'm unsure about how settings.cfg, partdatabase.cfg and perhaps even the savegames would behave on this situation.

On my add'ons, I choose to stick with Stock and normalized my pathnames to work with the PWD the KSP likes - using absolute pathnames instead is less than ideal because it makes porting code to handhelds and console more problematic (and, hey, Steam Deck is a thing! I'm dying to grab one!). The unreparse stunt made by the mono runtime is already bad enough.

Yet more fun: on MacOS, we follow the NextStep convention: an Application is a folder those name ends with ".app" and inside we have all the resources needed (or symlinked) for it. It's elegant to say the least, installing and uninstalling applications is pretty straightforward. But it's a pain to call them programatically, we usually do a shell with "open /full/path/to/Application.app" and let the OS do the rest.

About the problem at hands: what happened is that the Program Working Directory, PWD (or Current Working Directory - CWD, or Default Directory - different names on different O.S.s for the same thing) was being set inside the PDLauncher folder, and not on the KSP's root directory anymore. And so, everybody that is relying on the PWD being correctly set (including KSP itself, as the KSP.log ends up on the wrong place due the stunt) gets screwed as things are not reachable anymore from the places it used to be.

I know, there is already a thread about this ... see How to pass the steam age check using curl? ... but I'm a new user and can't comment in an existing thread and the answer marked as solution there doesn't work anymore.

Another question. I had my CABG X 4 about 3 months ago. I have been hitting the gym and feel pretty good, however I do enjoy hitting both the steam room and sauna. I don,t stay in long and still feel good but I have been told this is dangerous. Any thoughts?

I'd check with your Cardiologist. You could have some issues because of any medication you might be on. Hich heat (such as those found in Saunas and Steam rooms) has a different effect on different people, raising some's blood pressure while lowering others.

3a8082e126