Debugging (Civ5): Difference between revisions

From Civilization Modding Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 4: Line 4:


== XML Debugging ==
== XML Debugging ==
 
=== Reading the logs ===
=== Using the snapshots ===
== Lua Debugging ==
== Lua Debugging ==
 
=== Using the Firetuner console ===
== How to quickly reproduce problems? ==
=== Print, assert and error ===
 
=== Coroutines stack traces ===
== Quickly reproduce problems ==
== Configuring your installation ==
== Configuring your installation ==
Look for the following files under <code>My Documents/My Games/Sid Meiers' Civilization V</code> and open them in a text editor like the notepad (not in a word processor).
Look for the following files under <code>My Documents/My Games/Sid Meiers' Civilization V</code> and open them in a text editor like the notepad (not in a word processor).

Revision as of 17:53, 21 September 2012

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

Checklist

XML Debugging

Reading the logs

Using the snapshots

Lua Debugging

Using the Firetuner console

Print, assert and error

Coroutines stack traces

Quickly reproduce problems

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.