log

The primary debugging tool for monitoring script behavior and identifying errors in real-time.

Log File Location

Physical log entries are saved to %Documents%\Assetto Corsa\logs\custom_shaders_patch.log. This is useful for reviewing logs after a session has ended or a crash has occurred.

Usage Patterns

Standard Log

The explicit namespace call. Recommended for clarity in larger projects.

ac.log("Script initialized")

Print Alias

For convenience, the standard Lua print() is globally aliased to ac.log().

print("Application started")

Description

ac.log outputs text to both the physical log file on your drive and the in-game Lua Debug app’s console. It accepts a variable number of arguments and automatically joins them with spaces. Primitive values and CSP-specific types such as vec3, rgb, and rgbm are converted into readable string representations.

Silent Logging

Frequent logging to a physical file can affect performance and contribute to storage wear. For this type of logging, consider using ac.setLogSilent to keep messages visible in the UI while disabling disk writes.

Parameters

Parameter	Type	Required	Description
...	any	Yes	One or more values to be stringified and logged.

Examples

Status Tracking

Passing multiple mixed-type variables to track state.

local gear = 4
local speed = 120.5

ac.log("Vehicle Status:", "Gear", gear, "Speed", speed)
-- output: Vehicle Status: Gear 4 Speed 120.5

Logging Structs

Debugging vector positions and colors without manual conversion.

local pos = vec3(10, 0, 50)
local tint = rgbm(1, 0, 0, 0.5)

ac.log("Checking coordinates...")
ac.log(pos)
ac.log(tint)