DCS Locations to Update

Demo Video: https://youtu.be/vNCVxp5b6vY

Helios 1.6 supports multiple active DCS installations, including different versions. For example, some users have a release installation of DCS and another install containing the OpenBeta version. Helios can now configure both of these.

The configuration for this is "DCS Locations to Update", which is a collapsible configuration section shared by multiple configuration dialogs. You only configure this set of locations once and it will then be used by all the interfaces and components that need to know about DCS installations.

When you configure your DCS installations, use the "Add Location" button for each installed copy of DCS. Helios will try to guess where your DCS copies are installed based on the registry, based on common locations, and based on folder names that some people use. In the file browser that is shown when you click "Add Location," the left sidebar will have a section "Profile Editor" that has all the guesses that Helios made for your machine if those folders exist. You can click on those to jump to them or just navigate to the root of each DCS installation. The root is that folder which contains the file autoupdate.cfg and Helios wants you to navigate to it and select it.

Steam Support

On Steam installations, there will not be any autoupdate.cfg file, so select the dcs.exe file in the bin folder instead. Do not install any hacked up autoupdate.cfg files into a Steam install, as this will cause problems. You may find some posts on the internet that tell you to do this, but this advice is out of date.

Disable versus Remove

You can temporarily stop Helios from configuring a particular installation of DCS by unchecking the box marked "Write files to this location."

You can permanently stop Helios from configuring a particular installation of DCS by selecting the "X" icon on the right. This won't do anything to your DCS files; it just stops Helios from configuring this installation.