Install/move modules to another drive?

[Laer]

Hi. Is there a way to install or move terrain modules to another drive, while still keeping DCS on the original drive?

 

 

My SSD only has 50gigs left, and if I demo/buy another terrain module, it (assumedly) won't fit. So, I'm wondering if I could (for now) install modules on some other drive, and point to that extra drive in DCS somehow.

 

 

Eventually, I'll probably be getting a larger SSD, and installing all of DCS there, but for now, I can't.

 

 

In a pinch, would I be able to just temporarily manually move my existing Persian Gulf install folder to another drive, install the preview Nevada map,try it, then delete Nevada and move the Persian Gulf map back to its original location. Obviously, PG would not be useable moved to its new (temp) location, but would it work again once I move the folder back to the DCS drive after deleting Nevada?

 

 

I'd like to test Nevada out, but only have 50gigs left on the SSD where DCS is installed.

 

 

 

 

 

 

ALSO, I'm confused about the Nevada map requirements. It seems to say that it requires 120gigs of drive space for the map (although can, at minimum, operate using 60gigs), but then there's a note saying it needs an extra 36gig of space). So, what's up with all that? What is the minimm abount of space I need on a drive (with DCS World installed on it) to also add the Nevada map?), just to test it out during this preview week?

 

 

 

 

 

Win7 Premium

Edited April 10, 2020 by Laer

[Fri13]

Yes. You need to create link of module to another drive where it exists.

 

C:\dcs\modules\wanted --> X:\new\folder\wanted

 

This way wanted module is on another drive.

 

Haven't now time to explain deeper the soft and hard linking but you find more about it here.

[Laer]

Thanks for the reply.

 

 

Open question to Fri13 or any other users:

 

So, are we talking just a regular (manually made) shortcut sitting in the Terrains folder of the DCSWorld/Mods folder?

 

If so, how would you specify the install location of the newly purchased/previewing terrain? Isn't it just a checkbox in the Available Modules section of the Module Manager, which then automatically just installs it with the base install of DCS?

 

Again, I want to preview Nevada tomorrow, but only have 50gigs on my DCS SSD, so I'm looking for some sort of (temp) solution to do that. I'll get a larger SSD later.

[Rudel_chw]

So, are we talking just a regular (manually made) shortcut sitting in the Terrains folder of the DCSWorld/Mods folder?

 

Not a regular shortcut, you should use the windows command: mklink /J to create a hardlink between one file path and another path located on another drive. The hardlinks are invisible to DCS and it allows the program to still see the terrains like if they were on the original path.

 

Here is a sample case:

 

https://forums.eagle.ru/showpost.php?p=4131524&postcount=2

 

On your case, I would copy the whole dcs/mods/terrains/ folder to the larger drive, then I would delete the terrains folder on the original drive and finally run the command:

 

Mklink /J terrains new path/terrains

 

Here is more info about hardlinks:

 

https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

 

Test it with some small folders first, to gain experience with the process.

 

:thumbup:

[Laer]

Thanks for the info, Rudel chw. I have to admit, that's a bit new and intimidating, but certainly looks like a solution.

 

 

What would happen, though, if I just (for the sake of a temp solution to allow me to preview Nevada for a day) manually move the Persian Gulf folder in the DCSWorld/Mods/Terrains folder to a temp (inaccessible) drive, and install Nevada there (with the newly aquired drive space resulting from the move) for now? (Then, deleting Nevada, and moving Persian Gulf back to it's original spot)

 

 

 

 

ALSO: I've read up on Symbolic/Hard links, and I think I pretty much get it. But, what I don't understand, is whether that command line action creates any kind of visible file in any of the directories, or some indication of its existance. As well, how do you then delete that hard link? Remember, I am just wanting to use this to preview (for a day) the Nevada map, which I don't have room for on my DCS drive.

Edited April 10, 2020 by Laer

[Rudel_chw]

Thanks for the info, Rudel chw. I have to admit, that's a bit new and intimidating, but certainly looks like a solution.

 

Well, undoubtedly the best solution is to purchase a bigger SSD drive and move the whole DCS folder there .. other solutions are more complicated, sorry about that.

 

What would happen, though, if I just (for the sake of a temp solution to allow me to preview Nevada for a day) manually move the Persian Gulf folder in the DCSWorld/Mods/Terrains folder to a temp (inaccessible) drive, and install Nevada there (with the newly aquired drive space resulting from the move) for now?

 

Most likely it wont work, because the installer will see that a current map folder is missing and will simply redownload it together with the new Map.

 

ALSO: I've read up on Symbolic/Hard links, and I think I pretty much get it. But, what I don't understand, is whether that command line action creates any kind of visible file in any of the directories, or some indication of its existance.

 

It cant create anything or DCS wouldn’t be fooled onto believing that it is a folder .. it looks like a folder, but windows adds a small arrow to its icon, so you can be aware that it is a link rather than a folder. See my pictures.

 

As well, how do you then delete that hard link?

 

Did you read the article that I linked on my previous post? :noexpression:

[Laer]

Hi, Rudel chw... Ya, a larger SSD is the obvious proper solution, but not something that I can do today (Nevada preview is tomorrow). Not even sure the computer store is open, let alone if it's a good idea to go there. Eventually, though, I will upgrade it, as I said.

 

 

Too bad I can't just temporarily move the Persian Gulf map... but, you're probably right about it trying to load it. At this point, I'm not even sure the 50gig + the 32(?)gig I'd get from the move would be enough for Nevada, which claims it needs 160gigs... plus 36gigs(?!) more on top of that. Ugh...

 

 

Ya, I more or less get the link thing... just wasn't previously familiar with it, so I wasn't sure if it created any files as a result, and if you then delete that file to delete the link.

 

 

The reason I ask about the deletion, is because the article only referenced deleting Symbolic links, not hard links, which I'd be using.

 

 

As well, I found other articles/threads about difficulty deleting links, although it may just be in reference to links to items that are being used when you are trying to delete them. There were other references to third party apps required to delete them, etc.... and since I'm not well-versed in this sort of thing, I was concerned I'd mess something up with the system or the DCS install, which I couldn't reset/fix.

 

 

Okay, well, I guess I'll just pass on previewing Nevada... If it truly needs 160gigs (plus possibly 36gigs on top of that), then I'll probably not be buying it anyway. Why is it so huge compared to Persian Gulf and the Caucasus map??

[Rudel_chw]

... Okay, well, I guess I'll just pass on previewing Nevada... If it truly needs 160gigs (plus possibly 36gigs on top of that), then I'll probably not be buying it anyway. Why is it so huge compared to Persian Gulf and the Caucasus map??

 

On my PC, the Maps use this amount of space:

 

Caucasus: 98.2 GB

Nevada: 33.8 GB

Normandy: 15.4 GB

Persian Gulf: 32.8 GB

 

The 160 GB requirement is probably the space of the Map + DCS.

[Laer]

Yup, on mine, Caucasus is 16gigs, and PG is 32gigs. (Why do we have a difference on the Caucasus map?)

 

 

Weird... and now that I checked, the Buy page for PG also states the same specs as Nevada... 60gigs minimum, 160gigs recommended, plus an 'additional 35gigs'...

 

 

Ya, maybe they are including the base program, and only the 'additional' is the maps requirement... although they are saying 35gigs for PG, when both of us have it as (say) 33gigs.

 

 

Well, if that's the case, maybe I CAN fit Nevada on there, since it would fit in the remaining 50gigs of drive space I have. Certainly seems more likely the map is around 35, than 160+35!

 

 

Okay, well, as odd as that is, that's good. I can try Nevada tomorrow.

 

 

I'll be getting a larger drive sometime (since DCS is surely to increase in size when the new free map arrives), plus I'm sure XPlane11 (which is also on that drive) will be expanding over time.

 

 

Just needed a quick solution for tomorrow's Nevada preview. Seems like I should be okay.

 

 

Thanks guys...

[Rudel_chw]

Yup, on mine, Caucasus is 16gigs, and PG is 32gigs. (Why do we have a difference on the Caucasus map?)

 

Sorry, my mistake .. yes Caucasus is 16.1 GB

[Art-J]

Yup, on mine, Caucasus is 16gigs, and PG is 32gigs. (Why do we have a difference on the Caucasus map?)

 

 

Weird... and now that I checked, the Buy page for PG also states the same specs as Nevada... 60gigs minimum, 160gigs recommended, plus an 'additional 35gigs'...

 

 

Ya, maybe they are including the base program, and only the 'additional' is the maps requirement... although they are saying 35gigs for PG, when both of us have it as (say) 33gigs.

 

 

Well, if that's the case, maybe I CAN fit Nevada on there, since it would fit in the remaining 50gigs of drive space I have. Certainly seems more likely the map is around 35, than 160+35!

 

 

Okay, well, as odd as that is, that's good. I can try Nevada tomorrow.

 

 

I'll be getting a larger drive sometime (since DCS is surely to increase in size when the new free map arrives), plus I'm sure XPlane11 (which is also on that drive) will be expanding over time.

 

 

Just needed a quick solution for tomorrow's Nevada preview. Seems like I should be okay.

 

 

Thanks guys...

 

Yes, the min. space requirements include base DCSW package, although 160 sounds excessive, as barebones install takes about 75 GB once installer is finished. Which brings us to another problem - you forgot installer needs some temporary space for extracting downloaded archives and moving files around (maybe that's where total "160" comes from?). How much for installation of Nevada - I don't know. You might be fine with your 50, but be aware of it.

[Talon Karde]

On 4/10/2020 at 7:06 PM, Rudel_chw said:

 

Not a regular shortcut, you should use the windows command: mklink /J to create a hardlink between one file path and another path located on another drive. The hardlinks are invisible to DCS and it allows the program to still see the terrains like if they were on the original path.

 

Here is a sample case:

 

https://forums.eagle.ru/showpost.php?p=4131524&postcount=2

 

On your case, I would copy the whole dcs/mods/terrains/ folder to the larger drive, then I would delete the terrains folder on the original drive and finally run the command:

 

Mklink /J terrains new path/terrains

 

Here is more info about hardlinks:

 

https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

 

Test it with some small folders first, to gain experience with the process.

 

Sorry for digging deep into the forum. I tried this method, it doesn't work with terrain. The game crashes and before crashing several visual bugs like clipping. So idea is great but it is not an answer to the space problem on a SSD.

[Rudel_chw]

25 minutes ago, Talon Karde said:

Sorry for digging deep into the forum. I tried this method, it doesn't work with terrain. 

 

Yes it works .. here I moved my Nevada Map to the C drive, while the rest of DCs is on my G drive:

 

 

On the command window you can check the commands that I used to create the folder junction. And tried a nevada mission and it does work, with no crash or error:

 

 

Here is the DCS.Log of this trial mission .. the mission uses Moose for background air traffic, so the log can be hard to read.

Best regards,

 

Eduardo

 

 

dcs.zip

[Talon Karde]

Hi,

 

When you do this, where are your Nevada files? Still on G and the command move them. Or your Nevada directory on G is empty and all the files already in C ?

 

Thx !
 

[Rudel_chw]

33 minutes ago, Talon Karde said:

When you do this, where are your Nevada files? Still on G and the command move them. Or your Nevada directory on G is empty and all the files already in C ?

 

Nevada files on drive C

 

 

Remaining DCS files on drive G:

 

 

The small arrow on Nevada, denotes that this is actually a link to another part of the filesystem, it is not a folder.

 

Edited May 14, 2021 by Rudel_chw

[Talon Karde]

14 hours ago, Rudel_chw said:

 

Nevada files on drive C

 

 

Remaining DCS files on drive G:

 

 

The small arrow on Nevada, denotes that this is actually a link to another part of the filesystem, it is not a folder.

 

 

 

I followed step by step with your screens, all is working! I officially call you God from today

 

Muchas gracias por el tutorial.

[Rudel_chw]

1 hour ago, Talon Karde said:

 

I followed step by step with your screens, all is working! I officially call you God from today

 

Glad you got it working .. 

[ppokit]

Apologies for resurrecting this thread, but I can't seem to get the mklink /J command to work for both the Syria & Persian Gulf maps.
The cmd prompt returns that all is well and junctions are created, win10 explorer also shows the junctions are there.
Fire up DCS open beta and Syria is no longer authorized, and the Persian Gulf theatre has just disappeared.

It works fine for Caucasus & Nevada....

Any ideas anyone?
Thanks!

[Rudel_chw]

2 hours ago, ppokit said:

Any ideas anyone?

 

Sorry, I know that the above procedure works for me .. can't say much about yours, since you don't show how is your folder structure currently.

[ppokit]

Just a standard installation on an NVMe "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\terrains" and on my spare SSD I have "D:\DCS Modules\Terrains" where the Caucasus & Nevada maps were successfully linked to. Nothing fancy.

Thanks!

[Rudel_chw]

30 minutes ago, ppokit said:

Just a standard installation on an NVMe "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\terrains" and on my spare SSD I have "D:\DCS Modules\Terrains" where the Caucasus & Nevada maps were successfully linked to.

 

Sorry, I don't understand .. I tought that your problem was with the  Syria & Persian Gulf maps, not Caucasus & Nevada.

Can you show screenshots of the folders  C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\terrains and D:\DCS Modules\Terrains ?

[ppokit]

Yes that is correct, problem is with the Syria & PG maps. Caucasus & Nevada are linked without issues. Very strange.

C:, where DCS is installed showing junctions to Nevada & Caucasus, and where Syria & PG still remain....

D:, where I have successfully moved Caucasus & Nevada.....

[MAXsenna]

Any reason you didn't just move the whole terrain folder?

Sent from my MAR-LX1A using Tapatalk

[Rudel_chw]

22 hours ago, ppokit said:

problem is with the Syria & PG maps. Caucasus & Nevada are linked without issues. Very strange.

 

Hello,

I really don't know what may be causing your issue .. I've just moved my Syria terrain as a test. First I moved the Syria folder to my G drive, and then executed these commands:

 

 

Then ran DCS and got no error messages, and the terrain looks properly installed:

 

 

... and on the Sim it seems to work well, with a bit longer load times as my G drive is much slower than my C one.

 

 

So, I would discard a DCS issue ... check your install carefully and hopefully you will find the root cause.

Best regards,

 

Eduardo

Edited November 5, 2021 by Rudel_chw

[ppokit]

Ran repairs on my DCS install last night….still no joy. 
Really strange considering works for 2 maps and not the other 2. 
Oh well, just another quirk of DCS I guess.