Debugging

Debugging levels

Is it me, or the debug level options within Prefs.ini have no effect? No matter what I set, the amount of log rows in debug.err are the same. Values I've tried: High, Low, All, None, 0

By default, they are all set to "Default". A patch changelog mentioned something about showing less debug information, but that hasn't changed these settings. Perhaps this just simply hasn't been implemented?

Sometimes the last error log gives no impression of what is wrong with the mod that makes the game crash.

[edit] The dump(.dmp) files under "C:\ProgramData\Stardock\Galactic Civilizations III" are binary (C is the drive that Windows is installed on).

[edit2] Three years later got an answer from Stardock:

The values are:

  • Default 
  • DebugOnly
  • VerboseDebug
  • Spam

I hope that this helps, but it really depends on how much debug messages we've added to a various system. Also, FYI, the debug messages slow down the game, so a higher volume will cause your game to run slower, so make sure to set them back to default when you're done. You will probably want to set the Data, Inititalization, and Engine categories to Spam if your problem occurs during load.

- Stardock Programmer Cari

9,175 views 3 replies
Reply #1 Top

I wouldnt be surprised if there was a special command line variable needed to enhance the amount of debug data, or better, it only works on special debug builds during their internal testing.  They need to keep some things proprietary.

Reply #2 Top

Well great I found I have the wrong planet name for a star system. Now I have to find several other invisible problems. Sure I guess Stardock would like us to make tiny changes and then test them. I am doing small changes with multiple elements, which require more elements.

I wish the XML Schema files were even more strict. For example InternalName element is not set as unique* and there is nothing that would check the reference values in other files.

[edit]* - Which I achieved with this:

Code: xml
  1. <xs:element name="StarSystemList" type="StarSystemListDef">
  2. <xs:unique name="InternalNameUnique">
  3. <xs:selector xpath="StarSystemGroup/StarSystem"/>
  4. <xs:field xpath="InternalName"/>
  5. </xs:unique>
  6. </xs:element>
 

Reply #3 Top

It seems like any of the options I had tried then gave the minimum amount of debug messages. Unless others in the community have found valid values, I'll have to send a ticket to @Stardock.