User Tools

Site Tools


debugging:debugconfig

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
debugging:debugconfig [2023/04/24 03:20] – created mitdebugging:debugconfig [2023/04/24 03:54] (current) mit
Line 5: Line 5:
 === To activate debug config on the client === === To activate debug config on the client ===
  
-Create a file called  ''debugconfig.txt'' in the same location as ''TheUniversal.exe'' Inside the .txt file you add lines of the form ''LogTest=[mode]''+Create a file called  ''debugconfig.txt'' in the same location as ''TheUniversal.exe'' Inside the .txt file you add lines of the form ''[LogName]=[mode]'', each on a new line.
  
-e.g+e.g\\
 ''LogTest=2'' ''LogTest=2''
  
-Each config mode should appear on a new line.+The name on the left indicates the config system to be activated. The mode determines how it is used.\\
  
-The name on the left indicates the config system to be activated. The mode determines how it is used.+**Mode 0** = Debug off\\ 
 +**Mode 1** (and above) = Print to the system debug output stream \\ 
 +**Mode 2** = Print to a file called 'DevLog.txt'\\ 
 +**Mode 3** = Print to the game chat window\\
  
-Mode 0 = Debug off +To see the output for log mode 1 you will need to access the debug output stream.. if you have Visual Studio or other IDE and can attach it to the game process, the logged text should appear in the output debug channel).
-Mode 1 (and above) = Print to the system debug output stream  +
-Mode 2 = Print to a file called 'DevLog.txt' +
-Mode 3 = Print to the game chat window +
- +
-To see the output for log mode 1 you will need to have access to the debug ouput stream.. if you have access to Visual Studio or other IDE and can attach it to the game process, the logged text should appear in the output debug channel).+
  
 Activating mode 2 can affect game performance so its probably not wise to leave that set all the time.  Activating mode 2 can affect game performance so its probably not wise to leave that set all the time. 
    
 As well as ''LogTest'', there are a few different logging categories which may be useful.. As well as ''LogTest'', there are a few different logging categories which may be useful..
- +\\ 
-''LogScriptTrace+<code>LogScriptTrace
 LogLogin LogLogin
 LogCurlVerbose LogCurlVerbose
 LogDownloadableAssets LogDownloadableAssets
-LogVehicleAssets''+LogVehicleAssets 
 +</code>
  
 so, if your client's debugconfig.txt included so, if your client's debugconfig.txt included
 +\\
 +<code>LogTest=1
 +LogScriptTrace=2
 +</code>
  
-''LogTest=1 +.. you would get LogTest messages output to the debug console and ScriptTrace message written to the DevLog.txt file. (See [[scripting:reference:debugging|Debugging Scripts]] for more info on the ScripTrace functionality).
-LogScriptTrace=2'' +
- +
-.. you would get LogTest messages output to the debug console and ScriptTrace message written to the DevLog.txt file.+
  
 === DebugConfig on server === === DebugConfig on server ===
debugging/debugconfig.1682324451.txt.gz · Last modified: 2023/04/24 03:20 by mit

Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki