A Launcher Apk

[Janeth Counter]

BestPractice

It's good practice to download and install the Designer Launcher every time you install a new release of Ignition. The Designer Launcher is a separate application and is not part of an Ignition release, so it's important not to have an outdated Designer Launcher shortcut residing on your desktop

Until the point when someone finds an exploit and you didn't apply the patch since it's just a launcher. There's certainly less risk of an exploit with a smaller codebase but running out-of-date software is generally bad practice and I think particularly egregious in this case since updating the designer launcher is minimal risk to your production environment

Whenever an Application is launched from a Launcher, the Launcher will check to see if it needs an update. If the Gateway containing launched application is several revisions ahead of the Launcher, the Launcher will provide a popup notifying you that an update is available.

However manual upgrades can be performed. Simply download and run a new launcher installer from a more recent Ignition Gateway. During installation, simply set the installation directory to the same directory as the old launcher.

As of 8.0.13's bundled client/designer launcher, you'll get a prompt if you connect to a gateway that's got a significantly different version of the launcher available. Not quite auto-updates, but pretty good.

...

That aside, they only get better, so there's certainly no harm in updating

I think ultimately the issue is that of communication. Once a project gets above a certain size you will have different people controlling the gateway software installations vs those who are building the application. So there is always the chance (ok 100% certainty) that one group doesn't talk to the other about what version of software is in use. Thus is makes sense to automatically minimize the friction by getting the computers to do what they do best - talk to each other.

My test gateway is running on Ubuntu (just to see how Ignition handles linux) and this morning Ubuntu told me that there were new updates available. After doing said updates (1) I could no longer open the Inductive website in Firefox (2) Thus Ubuntu stopped me from downloading some software called Ignition HMI, that's apparently full of exploitable holes

This is on 20.04.1 LTS updated as of today. Firefox 84.0.2 (64 bit). Running in a VM under Windows 10

I just loaded youtube.com and www.wikipedia.org from firefox within this system, but I can't get to support.mozilla.com

But I've also had the firefox crash reporter pop up a few times today.

nslookup works for inductiveautomation.com and returns 52.52.32.221

But I can't ping it. Firefox fails to load, but it will redirect from the to the url of the site before dying.

But I can get to the correct inductive site via 2 other systems (windows and mac) so I know it's just the Ubuntu system. My guess is something was screwed up with the update, but as this is a test system I don't really care too much about that aspect.

Same problem here, I even have the same certificate on the Ignition gateway and the ssl termination point in front of it (a web application firewall). Designer launcher works directly to the gateway, but not through the WAF (SSL Certificate not found). The certificate is trusted: LetsEncrypt.

All, not sure if it has been addressed elsewhere in the forums, but Designer Launcher using Self Signed certificates on a Gateway with redundancy needs to have the Subject Alternates included in the Master and Backup gateways. It will ask to trust both certificates. There should be a note in the section stating this is required for Gateways using redundancy.

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.

3a8082e126