Problem updating with default missions on different drive

[doveman]

The default missions often consist of videos and take up over 7GB (FC-3, KA-50, SU-25T) which I can't spare on my SSD, so I've moved them to my Saved Games folder. So I have

 

Saved Games\DCS\Missions\FC-3\Default Mission\EN\

 

and then I make a Junction to that in my DCS install folder. I was using Symbolic Links before, which worked but I found they didn't with X-Plane, so I switched to using Junctions for everything. This works fine except for when I go to update DCS, as it wants to copy some of the missions to a _backup00x folder and throws up an error about not being able to copy from one drive to another.

 

The only way round this I've found so far is to delete the Junctions, copy all the missions back to the original places (so it doesn't have to download them all again), do the update, copy any new/updated files back to Saved Games and then recreate the Junctions again. This is obviously tedious, so I was wondering if anyone can think of a better solution, or maybe only ED can fix this by changing something in their update code?

Edited July 27, 2014 by doveman

[Flagrum]

As the default missions often consist of videos and take up over 7GB (FC-3, KA-50, SU-25T) which I can't spare on my SSD, so I've moved them to my Saved Games folder so I have

 

Saved Games\DCS\Missions\FC-3\Default Mission\EN\

 

and then I make a Junction to that in my DCS install folder. I was using Symbolic Links before, which worked but I found they didn't with X-Plane, so I switched to using Junctions for everything. This works fine except for when I go to update DCS, as it wants to copy some of the missions to a _backup00x folder and throws up an error about not being able to copy from one drive to another.

 

The only way round this I've found so far is to delete the Junctions, copy all the missions back to the original places (so it doesn't have to download them all again), do the update, copy any new/updated files back to Saved Games and then recreate the Junctions again. This is obviously tedious, so I was wondering if anyone can think of a better solution, or maybe only ED can fix this by changing something in their update code?

I have no solution, but perhaps an idea for c0ff for a small change on his side that could help with this issue: instead of creating the backup folders directly in the DCS installation directory, create them in a subfolder.

 

i.e. instead of

...\DCS World\_backup.00n

 

create them as

...\DCS World\Backup\_backup.00n

 

This way someone could have "Backup" point to somewhere else, i.e. the same drive as the mission files in the OPs case. That should solve the problem, shouldn't it?

[doveman]

I have no solution, but perhaps an idea for c0ff for a small change on his side that could help with this issue: instead of creating the backup folders directly in the DCS installation directory, create them in a subfolder.

 

i.e. instead of

...\DCS World\_backup.00n

 

create them as

...\DCS World\Backup\_backup.00n

 

This way someone could have "Backup" point to somewhere else, i.e. the same drive as the mission files in the OPs case. That should solve the problem, shouldn't it?

 

Thanks for the idea but I don't think that will work actually. Although that will allow me to make a Junction to Backup\ in Saved Games\DCS\ and thus it will be on the same drive as the missions and so shouldn't throw up an error when moving those, if it needs to move a file from the install folder to backup, that will involve moving files between drives and so we'll get the error then instead.

[Flagrum]

Hrm, true. :doh::D