Jump to content

Forcing game to load from DefaultGameCore.ini


Amineri

Recommended Posts

Bertilsson, my changelist is 356266 :smile:

Checked D:\Users\Drakouš\Documents\My Games\XCOM - Enemy Unknown\XComGame\Config\XComEngine.ini

 

Blast, there are more occurences of Package=Zhang_ANIM now :sad: I have both DLC packs installed and enabled phone home.

[0003.06] DevConfig: (System) 'Default__System' loading configuration from ..\..\XComGame\Config\XComEngine.ini
[0012.58] DevDlc: Caching file: XComEngine/../../XComGame/DLC/PCConsole/DLC_Day060\Config\XComEngine.ini
[0012.60] DevDlc: Merged DLC config file (../../XComGame/DLC/PCConsole/DLC_Day060\Config\XComEngine.ini) into existing config file (..\..\XComGame\Config\XComEn
gine.ini)
[0012.60] Log: ------------- AddPackagesToFullyLoad: fullyloadtype 2 for LoadForAllGameTypes: Zhang_ANIM
[0012.68] DevDlc: Caching file: XComEngine/../../XComGame/DLC/PCConsole/DLC_PackIn\Config\XComEngine.ini
[0012.68] DevDlc: Merged DLC config file (../../XComGame/DLC/PCConsole/DLC_PackIn\Config\XComEngine.ini) into existing config file (..\..\XComGame\Config\XComEn
gine.ini)
[0012.70] Log: ------------- AddPackagesToFullyLoad: fullyloadtype 2 for LoadForAllGameTypes: Zhang_ANIM

 

Interesting fact is, that [Engine.PackagesToFullyLoadForDLC] extra entries are added when exiting the game (native function within Engine.upk) and not logged.

 

Oh, there! UE3 Special Characters - dot sign is responsible for duplicated lines.

 

Increased load times can be fixed by replacing the dot with a plus sign for all entries in [Engine.PackagesToFullyLoadForDLC] section of DLC's XComEngine.ini

  • ..\XCom-Enemy-Unknown\XComGame\DLC\PCConsole\DLC_PackIn\Config\XComEngine.ini
  • ..\XCom-Enemy-Unknown\XComGame\DLC\PCConsole\DLC_Day060\Config\XComEngine.ini
[Engine.PackagesToFullyLoadForDLC]

change
.Package=Zhang_ANIM

to
+Package=Zhang_ANIM

Only downside seems to be, the change will be undone by verifying game's cache with Steam.

 

Is it working for you guys?

Edited by Drakous79
Link to comment
Share on other sites

  • Replies 71
  • Created
  • Last Reply

Top Posters In This Topic

Only downside seems to be, the change will be undone by verifying game's cache with Steam.

Is it working for you guys?

YES, it works perfect! Great find!

 

I will look into creating an updated version of the cleanup script which will cleanup the existing redundant sets AND prevent them from re-appearing.

 

That way it would only need to be run once every re-install instead of every now and then.

Link to comment
Share on other sites

The offset for 1.0.1 for Mac (Mac App Store version) has moved to 0x1D86B50. If you edited version 1.0, the App Store will not update the game and you will need to delete it and redownload. After editing, the app will need to be code-signed, again (as usual...).

 

If searching in a hexeditor, look for "44 00 00 00 65 00 00 00 66 00 00 00 61 00 00 00 75 00 00 00 6C 00 00 00 74 00 00 00 47 00 00 00 61 00 00 00 6D 00 00 00 65 00 00 00 43 00 00 00 6F 00 00 00 72 00 00 00 65 00 00 00 2E 00 00 00 69 00 00 00 6E 00 00 00 69 00 00 00". This is "DefaultGameCore.ini" in UTF32LE. I used "Hex Fiend" hexeditor, which is free.

Thanks very much for the update.

 

@Drakous79: Also kudos on catching the cause of that pesky file growth.

 

Edit: Wiki 'Recent Discoveries' updated on both items.

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

  • 3 weeks later...

Dubious intent did find a very simple to use command line tool which can be used to patch any file by comparing file A and B and storing only the differences. The differences can then be applied to any copy of A via command line.

 

That would work as long as you require a completely untouched XComGame.exe before installing Long War.

AND if the XComGame.exe-file is not personalized in any way by steam which yzaxitol came to suspect when he ran into problems with his merciless installer.

 

Edit: You would probably want to make the installer in first hand try to patch a backup file made by the installer itself to make it possible to install again and again without giving user problem if he after installing long war did some changes to the .exe (such as developer console).

Edited by Bertilsson
Link to comment
Share on other sites

Also using the DIFF to install changes to a backup exe would be useful when installing a new Long War version over the top of a previous Long War install. Plus I'd suppose you'd want to be keeping the original exe for uninstall purposes anyhow :)

Link to comment
Share on other sites

You want to use my EXEDiff package for creating your own DIFF files, and probably at least look at the script wrapper I put together in EXE Patcher for applying them. Both are based upon the open source 'bsdiff' package (see either download page for the link) which you have to download from elsewhere but is free to redistribute as long as you include the BSD License.

 

I put my scripts into the public domain, so feel free to mangle any way that suits you.

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...