NephilimNexus Posted October 9, 2012 Share Posted October 9, 2012 Now we've all see how in the demo one could simply open up DefaultGameCore.ini and start changing things around, but in the release version changing that file does nothing. In fact, just out of curiosity, I made a backup of it in another directory and then deleted DefaultGameCore.ini entirely and it had no effect on the game at all. So obviously the game is either no longer referencing it (and it's just a leftover junk file, now) or there is something elsewhere in the game that is telling it to ignore it (and pulling unmodified information from someplace else in it's place). Which brings me to the first and obvious question: How can we get the game to actually reference the DefaultGameCore.ini file again? Link to comment Share on other sites More sharing options...
Beknatok Posted October 9, 2012 Share Posted October 9, 2012 Now we've all see how in the demo one could simply open up DefaultGameCore.ini and start changing things around, but in the release version changing that file does nothing. In fact, just out of curiosity, I made a backup of it in another directory and then deleted DefaultGameCore.ini entirely and it had no effect on the game at all. So obviously the game is either no longer referencing it (and it's just a leftover junk file, now) or there is something elsewhere in the game that is telling it to ignore it (and pulling unmodified information from someplace else in it's place). Which brings me to the first and obvious question: How can we get the game to actually reference the DefaultGameCore.ini file again? Can someone confirm if changing this value affects anything? I'm at work, else I'd try myself. And/or anyone who still has the demo installed, what was the value there? Actually, it would be useful to have someone who still has the demo installed, to do a comparison between the demo & release Engine/Config files. \Engine\Config\BaseEngine.ini SaveLocalizedCookedPackagesInSubdirectories=FALSE Link to comment Share on other sites More sharing options...
Beknatok Posted October 9, 2012 Share Posted October 9, 2012 Building on my last comment... First, we should confirm that all of the \XComGame\Config\*.ini files do not get loaded/referenced (as opposed to just DefaultGameCore.ini). Pretty easy to just rename a few of them and fire up XCOM and see if it bombs. Second, we should confirm whether the files in \Engine\Config\*.ini get loaded/referenced or not. The XCom ones inherit the Engine ones, so that's where everything starts. At this point, I'm going to guess that both sets of ini files have been packaged/cooked. So the next step would be to start unpacking everything and trying to locate the base files. I only packaged up the .ini directories and sent those to myself, so I could study them at work today. So until I get home, someone else will have to step up and do some legwork. Link to comment Share on other sites More sharing options...
sage2 Posted October 9, 2012 Share Posted October 9, 2012 Changing that value to TRUE in either \engine or in the my documents version didn't seem to work. Is there a specific unpacker I should use? The one I have claims XComGame (4 mb) is empty. Link to comment Share on other sites More sharing options...
Beknatok Posted October 10, 2012 Share Posted October 10, 2012 I found these tools and tried them out. http://www.gildor.org/downloads I found that I had to use a combination of the Package Decompressor and the Package Extactor. When decompressing, I needed to use then -lzo flag for it to work properly. Been spending some time here, getting a bit of insight into how these .ini files work and the concept of cooking these files: http://udn.epicgames.com/Three/ContentCooking.html That being said, I've unpacked a handful of files in the XComGame\CookedPCConsole folder and skimmed their contents. But some of them have thousands of files. Anyone with experience with UT3, I'd love some help? Link to comment Share on other sites More sharing options...
NephilimNexus Posted October 10, 2012 Author Share Posted October 10, 2012 (edited) First, we should confirm that all of the \XComGame\Config\*.ini files do not get loaded/referenced (as opposed to just DefaultGameCore.ini). Pretty easy to just rename a few of them and fire up XCOM and see if it bombs. Tested this and the only file from the Xcom/XcomGame/Config directory that the game actually needs to properly load is DefaultEngine.ini You can literally delete the entire contents of the directory except for this one file and the game still starts up just fine. So at least that much is actually being used... Edited October 10, 2012 by NephilimNexus Link to comment Share on other sites More sharing options...
KristmasKthulhu Posted October 10, 2012 Share Posted October 10, 2012 First, we should confirm that all of the \XComGame\Config\*.ini files do not get loaded/referenced (as opposed to just DefaultGameCore.ini). Pretty easy to just rename a few of them and fire up XCOM and see if it bombs. Tested this and the only file from the Xcom/XcomGame/Config directory that the game actually needs to properly load is DefaultEngine.ini You can literally delete the entire contents of the directory except for this one file and the game still starts up just fine. So at least that much is actually being used... Earlier today I messed around with DefaultNameList.ini, commented out every American name except Bob, started a new game, and both males from the USA were named Bob, so the game does reference the files whether or not they're necessary to load. Looking around in other directories, I found another config folder for XCOM. It's under My Documents\My Games\XCOM - Enemy Unknown\XComGame\Config. It's possible that when the files are missing from the main directory, it can just grab them from here (except DefaultEngine) and run normally. Here's a comparison of the files in the separate config directories. steamapps directory DefaultCamera DefaultCompat DefaultContent DefaultDLCDefaultEditorDefaultEditorKeyBindingsDefaultEditorUserSettingsDefaultEngineDefaultGameDefaultGameCoreDefaultGameDataDefaultInputDefaultLightmassDefaultLoadoutsDefaultMapsDefaultMetaDataDefaultMPGameDefaultNameListDefaultNarrativeDefaultUI My Games directoryXComCameraXComCompatXComContentXComDLCXComEngineXComGameXComGameDataXComInputXComLightmassXComMapsXComMetaDataXComNameListXComNarrativeXComUI The contents of the same-named files are similar, though not identical, but I have no idea what that actually means. Link to comment Share on other sites More sharing options...
NephilimNexus Posted October 10, 2012 Author Share Posted October 10, 2012 Yes, which files the game reads, which it does not, where it reads them from and why is a giant mystery to me. People have reported success with some files but not others, and I can't imagine what the catalyst is to make the game go from actually using a modified file and simply pulling one from some invisible archive buried in all the Unreal junk. Link to comment Share on other sites More sharing options...
BluePaint Posted October 10, 2012 Share Posted October 10, 2012 (edited) Maybe use some file monitor tool to see which files are actually accessed. Edited October 10, 2012 by BluePaint Link to comment Share on other sites More sharing options...
sage2 Posted October 10, 2012 Share Posted October 10, 2012 I wonder if there's an executable switch to force the exe to preferentially load from plain text .ini files? I wouldn't know how to start figuring that out though. Link to comment Share on other sites More sharing options...
Recommended Posts