Unrealscript Debugging: Difference between revisions
From Unreal Tournament 2004 MiA Wiki
No edit summary |
mNo edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
*Console command <code>Utrace</code> - simple on/off | *Console command <code>Utrace</code> - simple on/off toggle. When on it floods the log, so be careful. When on can easy flood log with GB of output! | ||
*:[[File:Utrace.png]] | *:[[File:Utrace.png]] | ||
*Console command <code>UTrack ObjectName PropertyName</code> - | *Console command <code>UTrack ObjectName PropertyName</code> - It works only when UTrace is enabled. You can pass class name or object name as the first argument, and property name as the second value. | ||
*:[[File:Utrack.png]] | *:[[File:Utrack.png]] | ||
*:Changes will appear in UTrace log as on screens above. | *:Changes will appear in UTrace log as on screens above. | ||
*Console command <code>UProfile</code> - | *Console command <code>UProfile</code> - collects all uscript usage and when turned off dumps in format which almost json and can be parsed by js if needed. | ||
*:[[File:Uprofile.png]] | *:[[File:Uprofile.png]] | ||
*:It is good for finding slow functions or functions that are called a lot, to allow you to optimise code. | *:It is good for finding slow functions or functions that are called a lot, to allow you to optimise code. | ||
*Console command <code>DEBUGBREAK</code> - when called in code emits a break for the C++ debugger (not UDebugger). It's for engine developers where they have code & pdb files, and need stop in an exact place. They can modify code and emit that console command and the engine will | *Console command <code>DEBUGBREAK</code> - when called in code emits a break for the C++ debugger (not UDebugger). It's for engine developers where they have code & pdb files, and need stop in an exact place. They can modify code and emit that console command and the engine will stop at the desired place. | ||
<code>UProfile</code> ends automatically when game exits. | <code>UProfile</code> ends automatically when game exits. | ||
<code> | <code>UTRACE</code> and <code>UPROFILE</code> commands can be passed as command line arguments for the game. That turns them on in an early stage to get info about engine startup. | ||
Latest revision as of 23:12, 25 February 2026
New (to UT2004) debugging console commands
- Console command
Utrace- simple on/off toggle. When on it floods the log, so be careful. When on can easy flood log with GB of output! - Console command
UTrack ObjectName PropertyName- It works only when UTrace is enabled. You can pass class name or object name as the first argument, and property name as the second value.
- Changes will appear in UTrace log as on screens above.
- Console command
UProfile- collects all uscript usage and when turned off dumps in format which almost json and can be parsed by js if needed.
- It is good for finding slow functions or functions that are called a lot, to allow you to optimise code.
- Console command
DEBUGBREAK- when called in code emits a break for the C++ debugger (not UDebugger). It's for engine developers where they have code & pdb files, and need stop in an exact place. They can modify code and emit that console command and the engine will stop at the desired place.
UProfile ends automatically when game exits.
UTRACE and UPROFILE commands can be passed as command line arguments for the game. That turns them on in an early stage to get info about engine startup.
