Debugging (Civ5): Difference between revisions

From Civilization Modding Wiki
Jump to navigationJump to search
mNo edit summary
mNo edit summary
Line 6: Line 6:
** Set <code>LoggingEnabled</code> to 1. Civ5 will write log files under the <code>Logs</code> folder.
** Set <code>LoggingEnabled</code> to 1. Civ5 will write log files under the <code>Logs</code> folder.
** Set <code>EnableLuaDebugLibrary</code> to 1. Civ5 will display stack traces on Lua errors and you will be able to use the [http://www.lua.org/manual/5.1/manual.html#pdf-debug.debug debug] object.
** Set <code>EnableLuaDebugLibrary</code> to 1. Civ5 will display stack traces on Lua errors and you will be able to use the [http://www.lua.org/manual/5.1/manual.html#pdf-debug.debug debug] object.
** Set <code>DebugPanel</code> to 1. By pressing '''²''' (or '''ù''', or something else depending on your computer's language), Civ5 will display a debug panel.
** Set <code>DebugPanel</code> to 1. By pressing the '''²''' key (may be '''ù''' or something else depending on your computer's language) during a game, Civ5 will display a debug panel.
* '''usersettings.ini'''
* '''usersettings.ini'''
** Set <code>DebugMode</code> to 1. Needed to enable other features previously mentioned.
** Set <code>DebugMode</code> to 1. Needed to enable other features previously mentioned.

Revision as of 17:48, 21 September 2012

This article is under construction, come back in a few days.

Configuring your installation

Look for the following files under My Documents/My Games/Sid Meiers' Civilization V and open them in a text editor like the notepad (not in a word processor).

  • config.ini
    • Set LoggingEnabled to 1. Civ5 will write log files under the Logs folder.
    • Set EnableLuaDebugLibrary to 1. Civ5 will display stack traces on Lua errors and you will be able to use the debug object.
    • Set DebugPanel to 1. By pressing the ² key (may be ù or something else depending on your computer's language) during a game, Civ5 will display a debug panel.
  • usersettings.ini
    • Set DebugMode to 1. Needed to enable other features previously mentioned.