Problem maintaining concurrent installs (OB + Release)

[Wikkus]

Hiya, font of all knowledge :)

 

I had to delete my release installation a while ago and for some considerable time was just running the OB. I now want to go back to having both, so I created a DCS_variants file, duplicated my OB into a new folder, did the edit on my variants file (Release) ran the executable, got to the menu screen, but it didn't pick up my settings from OB and instead had defaults. How do I exactly replicate my OB config but in Release?

 

Sorry if I'm being thick, but seriously, I need a lie down :)

 

Rik.

 

[AusGoose]

Thanks for asking this Rik, I am having the same problem. Followed the steps from previous (old) posts and nothing I do seems to get it working: both my OB and Release installs try to use the default folder. Put another way, irrespective of the dcs_variant.txt file, both installs just use the same saved games/DCS folder. Has anyone got the current release and beta builds and been able to get them using different saved games folders? If so: how? A couple people on our server having the same issue.

[AusGoose]

Ok,

 

After a few hours of playing around, I have managed to create a shortcut to my open beta which forces the use of a particular saved games folder, and launches in VR. The dcs_variant.txt seems to not be working any more, or I am doing it wrong. In any event, I couldn't get it to work.

 

So for those who want to do what I did to get two saved games locations, read on.

 

What I wanted: Two DCS installs; one Open Beta build (OB), one stable/release build (release), each with their own folder in saved games.

 

What did I try that didn't work: Most recent Skatezilla DCS updater, dcs_variant.txt method outlined in various places in these forums.

 

What did work: A desktop shortcut to the OB DCS which triggered the OB to use its own saved games folder, and launch in VR

 

How did I do it: Multiple DCS installs with individual saved games folders

 

1. Find the DCS install folder of the install build you wish to give a new saved games folder. I found mine at this location C:\Eagle Dynamics\DCS World\ this is my open beta build.

 

2. In the DCS install folder, find the DCS.exe file. Mine was here C:\Eagle Dynamics\DCS World\bin\DCS.exe.

 

3. Right click on the DCS.exe file and select 'send to > Desktop (Create Shortcut)'

 

4. Go to your desktop and find the newly created shortcut. Rename it if you choose through right clicking on the icon and selecting 'Rename' from the menu. I called my shortcut 'DCS Open Beta'.

 

5. Right click on the shortcut again and select Properties

 

6. In the Properties window, select the 'Shortcut' tab. Look for the box called 'Target'.

 

7. In that box, it should have the path to the DCS install. Edit it by going to the end of the link address and adding --force_enable_VR -w "DCS 2". The text in the quotes, in my case DCS 2, will become the name of your new DCS saved games location linked to that install folder. To clarify, after editing, my 'Target' field had the following entry:

 

"C:\Eagle Dynamics\DCS World\bin\DCS.exe" --force_enable_VR -w "DCS 2"

 

8. Click Apply on the Properties dialogue box. Now left double click to start DCS using the link you just made. You will need to sign in to DCS again, after which DCS should start in VR.

 

9. If you alt-tab out of DCS and check in explorer, you should find a new folder in saved games with the name you gave it at step 7. I found mine at C:\Users\joebloggs\Saved Games\DCS 2

 

Limitations: Starting my openbeta any other way than my new shortcut defaults back to the original DCS saved games folder location. Be warned if you want to keep your 'other' installs saved games folder pure. I keep a backup just in case...might be worth having two custom saved games folders, not sure if I'll do that.

 

I do hope this helps anyone who has experienced the same issue I have.

 

Goose out

[Wikkus]

Glad that you figured out something that works for you, however, I think we might be at cross-purposes a bit here despite our desired outcome being the same thing, i.e. two DCS installs; one OB, one release, each with their own folder in Saved Games.

 

So, I tried a different tack this afternoon and used Skatezilla's excellent GUI updater tool to initiate a totally new release version, fresh off the server.

(Advanced Update Options > Manually Initialize and Install w/DCS Update > populate the fields as required > step through the installation by moving down the task list)

 

I then launched this fresh install and after I'd entered my account credentials, it gave me a splash screen and wound up at the main menu. No modules present because it's a fresh installation, but modules waiting and ready to download.

 

Now, this shiny, new, virgin installation was totally vanilla; windowed, everything set to "low", defaults, etc. 1280x720 resolution, painfully loud volume, et al.

 

So, I immediately exited the sim, checked my Saved Games folder and, sure enough, there's a corresponding shiny, new, unmolested DCS folder sat there.

 

So, I go back to Skatezilla's utility and tell it to copy the config from my known working OB install to the virgin Release install

(Application Settings > Manage Config Folders > Source = Open Beta > Destination = Release > Copy)

Switch the launcher to point to the release version and {drum roll} it works!

 

Not sure why the DCS_variant file method didn't work, but hey ho.