will merging 2 versions save hdd space?

[ebabil]

can we assume what the title says?

[Art-J]

Maybe a couple of gigabytes, after all the aircraft and ground/naval units files will not be duplicated. On the other hand, revamped Caucasus map is most likely going to be much bigger. Nevada will gain some weight with all these new airbases as well....

[Drag0nWIng]

i think we should waiting the merging file by ed boyz and official update, the 2.5 patch released.

or we have to re-instill 2 version game again.

[BIGNEWY]

If you are thinking of merging 2 version now, do not. Only bad things will happen.

[Phantom453]

I guess it will also depend upon whether you run (if ED have) both a release and open beta version for of DCSW 2.5 (onward). Fully installed that would require two versions of DCS 2.5xx + both with a copy of each map going forward.

 

DCS 2.xx + Caucasus + NTTR + SOH + N44 + ??

DCS 2.xx (Open Beta) + Caucasus + NTTR + SOH + N44 + ??

[98abaile]

Probably not. To give you an idea, I have both versions installed and every module and most campaigns. 1.5 is 31.3GB and 2.0 is 65.1GB. 2.0 already contains the Caucasus map, so the only difference between both my installations is Nevada at 33.8GB, if we imagine that the updated Caucasus will be roughly the same size as Nevada, the final installation of 2.5 will probably be the same as if you had both 1.5 and 2.0 both with all modules installed. If you don't own all modules then it will probably take up more space.

[ebabil]

so gotta get a 1tb to replace my 500gb

[Art-J]

98abaile's numbers and conclusions are somewhat off, because 2.0 certainly doesn't contain Caucasus map, but if You're running out of space on Your 500, an upgrade is a good idea. After all, DCS will always increase in size with every update.

[BitMaster]

You can quite save some space when you clean out the DCS folders on a regular basis by hand.

 

Gigabytes of MP tracks....Pics...._backup folder.

 

It's not seldom for me to clean 5-10GB out of 3 DCS's ( stabe beta alpha ).

 

But true, with N44 and SOH coming even my dedicated 250GB SSD seems to be fairly small, at least if I wanna keep all 3 versions.

[98abaile]

98abaile's numbers and conclusions are somewhat off, because 2.0 certainly doesn't contain Caucasus map, but if You're running out of space on Your 500, an upgrade is a good idea. After all, DCS will always increase in size with every update.

I literally just loaded it up to prove that the Caucasus are in 2.0. If you don't believe me, open the mission editor, click on file and select new, you can pick the map on the left hand side of the window, place a player controlled aircraft and start the mission.

[cichlidfan]

I literally just loaded it up to prove that the Caucasus are in 2.0. If you don't believe me, open the mission editor, click on file and select new, you can pick the map on the left hand side of the window, place a player controlled aircraft and start the mission.

 

Screen shots please. If the Caucasus were in 2.0 then there would be no need for ED to continue with 1.5.x.

[Art-J]

I literally just loaded it up to prove that the Caucasus are in 2.0. If you don't believe me, open the mission editor, click on file and select new, you can pick the map on the left hand side of the window, place a player controlled aircraft and start the mission.

 

Not sure what game version You literally loaded up, but it sure ain't standard 2.0.x, as the procedure You've listed above gives a result as on screenshot below (note maps to choose from). There cannot be different outcome, with only one map located in DCS World 2 OpenAlpha\Mods\Terrains\ folder, and it's the Nevada one. Unless You've managed to manually mix two versions somehow, but I don't quite see how that would work with two different terrain rendering engines.

[JetwasH]

Think hes been drinking lol

[cichlidfan]

Unless You've managed to manually mix two versions somehow, but I don't quite see how that would work with two different terrain rendering engines.

 

Indeed.

 

A long time, many patches, ago I had the old Nevada beta, mostly, working alongside the Georgia map. However, that quit working after a few more updates. That still required pasting things, beyond what ED installed, into the appropriate folder.

 

I would guess that even ED would be interested in how 98abaile accomplished this feat.

Edited October 5, 2016 by cichlidfan

[98abaile]

[BIGNEWY]

It is not recommended to do this, and is not supported by ED

 

The old Caucasus terrain will create issues, which is why we are waiting for it to be updated.

[SkateZilla]

Caucasus is not Part of the 2.0 Install, You Modded your Install, and there are several issues with Caucasus from 1.5 (T3) running in the 2.0 (T4) Terrain Engine, which is why Caucasus is being Re-Done for T4.

 

 

 

As for File Size and Space saving from Merging 1.5/2.0 into 2.5

 

It's likely even with updates to Caucasus T4/2.5/HD/+ Whatever you wanna call it,

 

As you will not have 2 main Install folders, of Which you will not have 2 Copies of 3 Specific Heavy Folders:

5.95 GB: /CoreMods/ (Core Elements, External Models, and Textures for Modules for AI and Network Play)

14.00 GB: /Mods/ (Installed Modules, Cockpit Objects/Textures etc)

11.50 GB: /Bazar/ (Objects, Textures, Shaders etc)

 

If you're like me, those 3 Folders alone for 1.5 Come out at about 31.6 GB (Size on Disk), 31.5GB (without the FC3 Training Mission Videos)

 

So that's at least 31.6GB you Wont have duplicated.

Edited October 6, 2016 by SkateZilla

[cichlidfan]

Caucasus is not Part of the 2.0 Install, You Modded your Install,

 

Intentionally modded, or screwed up by not taking defaults. Either way it isn't a stock 2.0 install.

[98abaile]

I haven't modded anything.

[cichlidfan]

I haven't modded anything.

 

Perhaps not on purpose, but you somehow have mixed two different installation into the same folder.

[frodrigues2016]

Maybe a solution

 

I think ED version 2.5 with all the maps could be a software program that works only with links to the already used maps......and with updates and file corruption.

[lazduc]

Confusion personified, is it any wonder folks mix up things. 1.5,2.0, 2.5, T-3, T-4, a bizarre number of updates which I think need the proper updater software to update correctly and which do it automatically sometimes...and introduction of new modules which sometimes are not compatible with the current build which sometimes needs to be backed up to the previous build....and which build is alpha, beta and it goes on.

 

 

I assume a lot of members have kept up with all this. I have not. I also have not installed anything since Flaming cliffs. I have purchased most modules waiting for a half- way stable release.(Not an alpha/beta).

 

I continue to wait for and look forward to 2.5 or whatever ED calls it. Hopefully it will be stable.....I would think that a stable foundation will enable third party developers easier paths to build modules/maps for DCS. Just my humble opinion.

[BIGNEWY]

yes this can create confusion and it is best to wait for ED and the release of 2.5

 

Just to be clear

 

Merging installs will create problems

[cichlidfan]

Merging installs will create problems

 

Also remind people that regardless what 98abaile is seeing in his installation. This is not the result of a stock, including default path, installation of the v2.x Open Alpha version of the sim.

Edited October 6, 2016 by cichlidfan

[SkateZilla]

Perhaps not on purpose, but you somehow have mixed two different installation into the same folder.

 

You simply can't copy / paste caucasus to 2.0, it requires editing the LUA

 

So even accidentally installing 2.0 over 1.5 will not work,

 

As the LUA has a parameter line to stop Caucasus Entry.LUA from Loading in the T4 Environment, and NTTR has one to Prevent loading of the Entry.LUA in the T3 Environment.

 

There is no Accidental Merging, There was a Thread that gave instructions on how to move Caucasus to 2.0, but as Stated, there will be SEVERAL Bugs that will render any use problematic.