Auto Updates.. please provide some info!

[MadTommy]

Please please give us a dedicated thread where devs can post info regarding autoupdates. We don't need extensive change logs, even it that would be ideal, but some pertinent info is required.

 

I know this has been asked for before and i have seen posts saying it will happen.. but can we get this now or very soon!

 

This is VERY important for people who have modded the game.. we need to know what has changed so we can evaluate how it might affect our mods.

 

Thanks.

 

Update today: version 1.2.2.7204.4

 

List of files changed.

Cockpit_P51Common.dll

ka50_protect.x64

ka50_protect.dll

fc3_protect.exe

FC3.dll

CombinedArms_protect.dll

CombinedArms.dll

Cockpit_A10C.dll

a10_protect.dll

a10_protect.exe

A10.dll

ka50_protect.exe

MissionResourcesDialog.dlg

MissionResourcesDialog.lua

Cockpit_P51D.dll

me_toolbar.lua

me_coalitions.lua

me_vehicle.lua

p51_protect.dll

p51_protect.exe

simulator.mo

Cockpit_A10Common.dll

ZweiBlau.dll

World.dll

WeaponBlocksNL.dll

WeaponBlocks.dll

Visualizer.dll

UserInterface.dll

Transport.dll

SpaceRenderer.dll

Space.dll

ParticleSystem.dll

nvttwrapper.dll

NGModel.dll

ModelViewer.exe

luarun.exe

lua-ziplua.dll

lua-gui_video_player.dll

lua-gui_axes_tune.dll

Legacy_AFM_Su25.dll

Legacy_AFM_Base.dll

i_18n.dll

FFTest.exe

fetchEffects.exe

Effects.dll

edMath.dll

Flight.dll

edCore.dll

ed_sound.dll

dcs_protect.exe

dcs_protect.dll

editor.exe

CockpitBase.dll

lua-gui_nodes_map.dll

AVIMaker.dll

lua-dxguiWin.dll

DCS.exe

Inter.dll

AsyncNet.dll

FMBase.dll

fc3_protect.dll

lua-gui_map.dll

blocksim.dll

lua-sound.dll

DCS_updater.exe

WeaponsBase.dll

InputTest.exe

Launcher.exe

offshore.dll

edterraingraphics3.dll

EDMMegaOptimizer.exe

lua-direct_output.dll

NewInput.dll

dxgui_edge_render.dll

Terrain.dll

AsmShadersCompiler.exe

dxgui.dll

Legacy_AFM_Su39.dll

AIFM.dll

Pathfinder.dll

lua-textutil.dll

GroundCockpitBase.dll

DXRenderer.dll

LandVehicle.dll

lua-minizip.dll

Weather.dll

Ka50.dll

CockpitKa50.dll

edObjects.dll

DCS_update_apply.exe

lua-guid.dll

dxgui_win_adapter.dll

CombinedArms_protect.exe

P51B.dll

edTerrain.dll

lua-dxgui.dll

optionsData.lua

ViewportHandling.lua

blocksimtest.exe

Weapons.dll

wRadio.dll

GraphicsXP.dll

WorldGeneral.dll

lua-MissionGenerator.dll

autoupdate.db

autoupdate.cfg

unins000.dat

unins000.exe

[MadTommy]

Unless this is it.

 

http://forums.eagle.ru/showthread.php?t=97186

 

But with no update number who knows. Cheers.

[GregP]

Agreed, just having a list of exactly which files have changed would be incredibly useful to those who run mods.

[Megagoth1702]

+1 on this.

[EtherealN]

Regarding mods: for the long term I would suggest using the facility towards executing mods through the SavedGames folder, thereby immune to being overwritten by the autoupdater, as long as the mod in question is able to operate in this manner.

[Megagoth1702]

Hold on, do you mean I can create my own view configs , graphics configs etc. in the saved games folder and it will override what's in the main game folder?

[PhoenixBvo]

Parallel to EtherealN's suggestion, if you do have mods which only function in the main game folder, use the following method to keep track of changes.

 

1. Download and install TortoiseHg. This is a distributed revision control system, which sounds more complicated than it is. It directly integrates its interface in the rightclick menu of windows explorer and is very easy to use.
   
2. Using the rightclick menu create a repository in your DCS World folder.
   
3. Now add all files you want to keep track of to the repository (using the rightclick context menu).
   
4. Select the commit option from the rightclick menu.
   
5. The icons overlaying the tracked files in windows explorer turn green.
   
6. Whenever the autoupdater has done its thing, you'll see any changes to the tracked files when the respective icon turns red. It also checks any subfolders and shows a red icon on the respective folder.
   
7. Now you can compare the changes with the original version which is still safely stored in the repository and merge the versions line by line if you wish.
   
8. After you're done checking the changes, you make another commit and you're ready to go.
   
9. If you ever want to go back to a previous state of a tracked file, you can do so as all versions are stored incrementally in the repository.
   

 

This type of tool is actually meant for software development and I use it at work on a daily basis. But for DCS it works like charm as well. You'll find it's quick and easy after you get the hang of it and never have to worry about your mods with the autoupdater anymore.

Edited December 12, 2012 by PhoenixBvo