User:CHILLMODEA/Pages/timestamped.log: Difference between revisions
Jump to navigation
Jump to search
CHILLMODEA (talk | contribs) (Create timestamped.log page) |
CHILLMODEA (talk | contribs) m (Rearrange command line arguments) |
||
Line 3: | Line 3: | ||
{{code|timestamped.log}} is a log file internally created and referenced by the {{source|4}} engine. Using the {{code|COM_TimestampedLog}} function, arbitrary log entries can be added to this file, prepended by the current timestamp. | {{code|timestamped.log}} is a log file internally created and referenced by the {{source|4}} engine. Using the {{code|COM_TimestampedLog}} function, arbitrary log entries can be added to this file, prepended by the current timestamp. | ||
The file will only be generated on the {{x360|4}}, or with the {{code|-profile}} | The file will only be generated on the {{x360|4}}, or with the {{code|-profile}} / {{code|-etwprofile}} command line arguments. Alternatively, the assembly of {{code|COM_TimestampedLog}} can be patched to permanently enable the logging. | ||
The log is used extensively throughout the engine, almost two hundred times{{Cite|1}}. At a high level, everything the game does is documented in the log. As such, it is quite good for finding issues / crash points, better than most other logging methods. | The log is used extensively throughout the engine, almost two hundred times{{Cite|1}}. At a high level, everything the game does is documented in the log. As such, it is quite good for finding issues / crash points, better than most other logging methods. |
Revision as of 20:53, 12 July 2025
timestamped.log is a log file internally created and referenced by the Source engine. Using the COM_TimestampedLog function, arbitrary log entries can be added to this file, prepended by the current timestamp.
The file will only be generated on the Xbox 360, or with the -profile / -etwprofile command line arguments. Alternatively, the assembly of COM_TimestampedLog can be patched to permanently enable the logging.
The log is used extensively throughout the engine, almost two hundred times[1]. At a high level, everything the game does is documented in the log. As such, it is quite good for finding issues / crash points, better than most other logging methods.
References
References | ||
---|---|---|
|