You may limit, or filter, the log messages that are displayed as the Cafe system runs.
One way to control the messages is by using the
-v option of the
Much finer control is available by configuring the desired logging areas in the Other Setting submenu of the System Config Tool. Filtering can be controlled by a log message's severity, or by the process or module that produces it.
A given log message is filtered (not printed) if any of its associated filter settings are disabled. For example, if a log message results from a graphics operation in the game, and Game is set to Disabled, then the message is not printed, even if Graphics is set to Enabled.
By default, the filtering settings are honored when writing the crash log following a system crash, potentially reducing the information that you have for debugging the crash. To get a complete crash log that ignores the filtering options, set Detail Crash Log to Enable.
By default, the System Config Tool is configured to use the setting from the
-v option of the
caferun command to determine the logging severity, or debug print level.
If you select a specific logging severity in the Override Debug Print Level setting of the Debug Flags Setting submenu of the System Config Tool, then that setting takes precedence over any specified
To restore the ability for the
-v option to specify the logging severity, change the Override Debug Print Level setting back to LV -1: No Override.
The log message severity settings are:
|LV -1: No Override||The
|LV 0: Errors||Log messages of the selected severity, or higher, are displayed.|
|LV 1: Warnings|
|LV 2: Informational|
|LV 7: Verbose|
The log message process sources are:
|Game||Filter log messages that come from the corresponding process.|
The log message module sources are:
|Operating System||Filter log messages that come from the corresponding module.|
|Other||Used for log messages that do not apply to any of the other modules.|
2014/02/12 Initial version.