X Launcher Pro Latest Version

[Novella Poinsett]

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.

I also tried going into the Zwift folder and deleting the ZwiftLauncher version 1.0.0.0 file, then running the latest ZwiftSetup download again, stone me it just went and put ZwiftLauncher version 1.0.0.0 right back in there!

My next step was to completely uninstall Zwift and all of its components from my PC, I then manually downloaded it again from the website and reinstalled it. I went back into the Zwift folder and lo and behold, ZwiftLauncher version 1.0.0.0 is there again! WTF?

In the meantime, I can confirm that the logs in our systems show that you are indeed running Launcher version 1.1.11 on all activities after January 11, 2024. You can confirm this as well by looking at your Log.txt files for each activity, these can be found in the Documents/Zwift/Logs folder.

Thanks for the details, you can ignore that file version as it is different than the actual Launcher version, although we will look into what it takes to keep that up to date so we can avoid confusion like this in the future.

I was thinking I could make a batch script that would check if the vision client launcher was installed and if not silently install it then launch. If we upgrade our server we would want to then upgrade the launcher, but if it sees the launcher already exists it will not install the new version. Any suggestions on how I could tell if the user needs a new version of the client installed?

When did you get that message? I installed Vision Client Launcher 8.0.11 and when I launched it did not say anything about a new version. Then I launched a project against a gateway that is running 8.0.16 and it did not say anything about a version difference.

Is it not good practice to be running the Vision Client Launcher at the same or higher version of the gateway? I am trying to think about how we can push out new versions of the Vision Client Launcher before we upgrade our gateway without having to tell people to go download it.

Would it be a big ask to have a command line parameter to visionclientlauncher.exe that would give the version? That way I can just install it silently and users do not have to be bothered about upgrading something they no nothing about.

How does it call /system/gwinfo? is that a parameter to visionclientlauncher.exe? is that a command inside the vision client launcher. I was hoping there was something I could call from the windows command line that would tell me what version a gateway is on.

I think this might actually work. In the response there is the version of gateway. Is there a certain way I can do the request so I can get an object that is easy to work with, possibly a json object? I did a rest method request and got back this string

I currently have the installer executable sitting on a network drive so every PC can access it and silently run it. However, every time the launcher has an update, would the installer need to get redownloaded off the gateway?

It seems your making this out to be more complicated than it needed to be. The launcher only updates its version when you update the gateway. We use standard IT software deployment tools to push out the new version to all our client PCs after we update the GW.

Ah that makes sense. We went through a series of upgrades to 8.1 recently. Our dev instance stepped through a few 8.1 versions which prompted a couple launcher updates. Due to being new to 8, I thought the launcher was being independently updated. In that case, we can just force a fresh install script when we update. Thanks.

When trying to open DWG's from explorer the default application is set to Autocad DWG Launcher which is found in "C:\Program Files\Common Files\Autodesk Shared\AcShellEx". However, when I try to open files from explorer I get this warning message: "Windows cannot find 'C:\Program Files\Autodesk\AutoCAD 2015\acad.exe'

I think this is the problem, I have the correct application set to open DWG's but that application is looking for a version that is no longer installed on my machine. Can I set Autocad DWG Launcher to look for the correct version (LT 2015)? I have tried repair and a reinstall to no avail.

The Autocad Shell Launcher always remembers the last Autocad program which opened a file. I have this problem as well. If I have opened a drawing in DWGviewer and then double click a drawing in Windows to open it, it will open it in DWGviewer.

To get round this open up LT on it's own, then using the FILE, OPEN menu open up a drawing. Now you can close LT and you will find the next time you double click on a drawing it should open it up in LT

Unfortuantely this doesn't work, I have been opening and closing drawings using LT for a few days now, and the launcher doesn't seem to be remembering that I have been opening files with LT, it is still looking for Autocad 2015.

In Windows, right click on one of the drawings. In the menu that pops up click on PROPERTIES. On the GENERAL tab, what does it say the drawing should open with? If it says DWGLAUNCHER, click on CHANGE and then you can force it to open in LT, or if it says AUTOCAD 2015 change it to DWGLAUNCHER.

I have done this as you say telling DWG's to launch with LT, however, it then opens multiple instances of Autocad which isn't ideal. I just can't understand why the DWG launcher will not 'link' to LT. I even tried deleting the Shell folder in common files and doing a reinstall, but it still wants to open with Autocad 2015! grrr.

I was having basically the same probblem. The difference in my situation was that i had just (last week) upgraded from ACADE 2012 to 2014. When I would double click a file to open, I would get the error on the attached image "file error,png". I had found some "solutions" on theh Autodesk website, but they did not solve my problem.

After doing some digging on my computer I found that the probelm was being casued by my registry. See attached registry image file. the first entry in the Apps folder was for ACADE2012 the next entry was for 2014. Since I am no longer running 2012 I deleted that first entry after closing AutoCAD.

after the whole story, this is the answer. In my case was from 2015 to 2016 and shellex was still linked to 2015. I didn't had the choice like yours to delete one entry, but I could edit instead the entries to the paths where I saw 2015 to 2016 (given the fact that was similar path).

3a8082e126