Reference

Settings and Troubleshooting

Tune readability, review integration controls, check shortcuts, and resolve common empty-view or remote issues.

Theme Maker
Settings reference
Stack trace controls
Saved log durability
Troubleshooting

Theme Maker

Theme controls live in Settings > Appearance. Use Appearance for quick theme switching, or open Theme Maker to edit, duplicate, rename, export, or import themes with a live preview.

Improve contrast for long debugging sessions.
Create team-specific visual defaults.
Make severity colors easier to scan.
Export a reusable Azkar Console theme asset.

Theme changes affect presentation only. They do not alter captured log data or exported records.

Settings Reference

Section	What It Controls
Import / Export	Portable profile import/export for settings, themes, and key binds.
Appearance	Theme switching and Theme Maker.
Log Details & Readability	Ordinary log stack capture, Demystify Stack Trace, stack trace syntax highlighting, and source code syntax highlighting.
Unity Integration	Capture Unity Logs and Forward to Unity Console.
Remote Logging	Listen for Development Builds, Unity Player Connection, and manual IP connection.
Workflow	Auto Scroll, Pause on Errors, Collapse, Clear Filters on Play Mode, Message Lines, and Saved Logs.
Shortcuts	Review, rebind, import, export, or reset keyboard bindings.
Diagnostics	Advanced troubleshooting tools.

The full stack capture setting path is Window > Azkar Console > Settings > Log Details & Readability > Stack Traces > Log Stack Trace Capture.

Option	Behavior
`File and line`	Default for ordinary `AzCon.Log`. Captures the callsite without a full stack walk.
`Full stack trace`	Makes ordinary `AzCon.Log` capture a full call stack.

FAQ

Why does AzCon.Log only show file and line by default?

Because file-and-line capture keeps ordinary logs fast. Full stack traces are available through AzCon.Debug, warnings, errors, or by changing Log Stack Trace Capture in Settings.

Does Azkar Console write every log if my game emits thousands of logs per frame?

Not in the default asynchronous modes. Extreme log storms use bounded queues so logging does not freeze the game or editor. If a sink cannot keep up, Azkar reports dropped entries.

If you need the strongest database recovery behavior, enable Crash Forensics durability. That mode can block while writing, so it is best for forensic sessions rather than normal play.

Saved Logs

Saved log behavior is configured at Window > Azkar Console > Settings > Workflow > Saved Logs.

Control	What It Does
`Saved Formats`	Chooses whether Azkar writes `Text (.log)`, `Azkar Database (.azrecdb)`, or `Both`.
`Play Mode Session Files`	Controls how many saved play mode captures Azkar keeps per saved format in the `PlayMode` subfolder. Default is `10`; `0` keeps every play mode capture.
`Editor Session Files`	Controls how many whole-editor-session captures Azkar keeps per saved format in the `Editor` subfolder. Default is `5`; this is on by default so users have a longer support and post-crash review trail.
`Database Durability`	Affects `.azrecdb` recovery behavior only. It does not change which files are written.

Mode	Tradeoff
`Fast`	Lowest overhead; asynchronous `.azrecdb` writes leave recent rows most at risk in a hard crash.
`Balanced`	Default; asynchronous `.azrecdb` writes with periodic page sealing after the configured count or interval.
`Crash Forensics`	Most recoverable; blocks while writing and disk-flushes each log frame/page, which can slow heavy logging.

Log Storms, Backpressure, and Durability

Azkar Console is designed to protect game and editor performance during extreme log storms.

In normal saved-log modes, file and database writing run asynchronously. If a project emits thousands of logs in a frame, Azkar keeps the application responsive by using bounded writer queues. When a queue cannot keep up, the sink may drop older queued entries and record the drop count instead of blocking the game indefinitely.

This is intentional. Most log storms come from runaway loops, exception spam, or overly verbose diagnostics. In those cases, preserving frame time and editor stability is usually more valuable than writing every repeated line.

For forensic runs where database recovery matters more than throughput, use Crash Forensics durability. This mode writes synchronously and performs stronger disk flushing, so it can slow heavy logging but gives the best recovery behavior.

Common Shortcuts

Shortcut	Action
`Action+F`	Focus Search
`Action+,`	Open Settings
`Action+K`	Open Filter Builder
`B`	Toggle Bookmark
`Shift+B`	Toggle Bookmark Shelf
`[` / `]`	Jump to previous or next visible bookmark.
`Action+Up` / `Action+Down`	Jump to oldest or newest visible log.
`Action+Shift+K`	Clear volatile filters.
`Action+Alt+K`	Clear all filters, including persistent filters.
`Action+Shift+Delete`	Clear captured logs.
`F` / `C` / `E`	Toggle Follow, Collapse, or Error Pause.
`Esc`	Close current UI.

Action means Command on macOS and Control on Windows/Linux.

Compatibility

Minimum supported editor: Unity 6000.0.
Primary verified editor: Unity 6000.4.3f1.
Additional Unity 6 smoke verification: 6000.0.73f1, 6000.2.13f1, and 6000.3.14f1.
Unity 2021.3.45f2 and 2022.3.62f3 are not supported by this release.

Troubleshooting

The Console Is Empty

Confirm the window is open from Window > Azkar Console.
Use Generate demo logs to confirm the UI is working.
Check filters and choose Clear Everything.
If you expect Unity logs, confirm Settings > Unity Integration > Capture Unity Logs is enabled.
Confirm your scripts call AzCon or Unity logging APIs that are being captured.

Logs Exist, But You Cannot See Them

Clear search text.
Disable regex mode if a regex is too narrow.
Use Clear Volatile first, then Clear Everything if needed.
Check severity controls.
Check whether a saved preset or persistent filter is active.

Remote Build Does Not Connect

Confirm the build is a Development Build.
Confirm Settings > Remote Logging > Listen for Development Builds is enabled.
Try Open Unity Player Connection... first, then Connect by IP... if discovery is unreliable.
Make sure the editor and device can reach each other on the local network.
Reconnect after relaunching the build if the player was already running before the listener started.

Exported Logs Are Missing Rows

Check whether you exported Filtered instead of All. Use Filtered when the visible view is intentional. Use All when you need the full session.

Bookmarks Are Visible But Live Rows Are Gone

Bookmarks can survive play mode transitions and clearing live logs. Use them as saved evidence, or export/import bookmarks separately from .azrecdb databases.