USc – Working with .ini Files

By | 03/09/2010

Working with .ini Files in UDK

.ini Files are used to save configuration data for your UDK games. there are two types: those which begin with ‘Default‘ and those which begin with ‘UDK‘. you need to be careful which version you arr your configuration data to. Both are explained below. The * used in the filenames below means ‘any string’ so Default*.ini means any file which begins with ‘Default‘, then has some other text in the name, and then ends in ‘.ini.

 

Base.ini

These are the configuration settings for the Unreal Engine, as defined by Epic. Do not edit these files.

 

Default*.ini Files

These are your default settings for when your game is first installed on a players computer. These settings are used when the game firt starts up and before the player has customised anything. These files are actually based on the contents of the Base*.ini files. Settings in Default*.ini files overwrite Base*.ini

If these files are not present when UDK starts up, they will be automatically generated based on the settings in the appropriate Base*.ini file.

 

UDK*.ini Files

These are the player customisation settings. UDK*.ini files are created by using the similar named Default*.ini file as their stating point, and will be updated with player settings and save information. If a similar named Default*.ini file exists in the folder, then then UDK version will be loaded and overwrite any settings within the Default*.ini file. If these files are not present when UDK starts up, they will be automatically generated based on the settings in the appropriate DEFAULT*.ini file.

 

Working with Default*.ini Files

Only Default*.ini files are included when you package your game for release. For that reason you should edit the Default*.ini files, and then delete the UDK*.ini files so that they are regenerated by UDK on the players PC.

If you make a change to an ini file and the change does not seem to work, then make sure you have added the change to the Default*.ini file and delete all the UDK*.ini or place them in a subfolder as a backup.

 

ini

So, working directly in the UDK*.ini files is not a good idea as their data can be overwritten, while you are workin g on your game, it can also result in Visual Studio constantly asking you to reload UDK*.ini files each time you run UDK. This can then cause you to loose your changes in UDKEngine.ini as the file has been recreated based on the contents of DefaultGame.iniwhich does not contain the changes you made.

 

DELETE THE UDK*.ini FILES

It is good practice to delete all the UDK*.ini files to force them to be rebuilt from the Default*.ini files. If any UDK*.ini files are in the UDKGame\Config folder, these will be loaded instead of the DEFAULT*.ini file, so its worth having the UDK versions rebuilt using your default settings from the DEFAULT*.ini files.

Leave a Reply

Your email address will not be published.