Current version 0.9.10 · Last verified 2026-10-24

Fix Azimuth lag and stutter

After an update, Azimuth rebuilds its shader cache. The developer says this can hitch for 15 to 60 minutes and that Default is the reference preset. Devlog.

The developer says caches warm as you play, not simply while the launcher sits idle. Compare the same route and settings after warm-up on Default. The 15-60 minute range is a reference, not a deadline after which every hitch proves a hardware fault.

Diagnostic order

Confirm version 0.9.10. Pipeline prep grew across 0.9.7 (2,344) and 0.9.10 (3,239).
Play on Default while caches warm. The developer gives about 15-60 minutes after an update; idling at the launcher is not the documented process.
If it continues, leave Ultra. Ultra is about 6.5 GB of VRAM and more than 16 GB of RAM.
Try a separate clean stock installation with a fresh save before reporting performance. Preserve your existing data first; simply deleting a mod may leave damaged caches.
If it persists, record route, resolution, preset, duration, CPU/GPU and LOG. Background applications, drivers and temperatures are general PC checks, not established Azimuth-specific causes.

City stutter is still a known issue

The 0.9.10 known-issues list explicitly says city-driving stutter is unchanged. A hitch beyond the cache window does not prove a broken PC. High/Ultra also change between versions; compare Default and do not submit Ultra performance reports.

Generated illustration: coastal road suggesting a long drive while shaders compile — Generated illustration. The compile window is from the developer's performance devlog. Illustration only; not a game capture, launcher screenshot or hardware test.

Generated illustration: handheld PC, a reminder of the Steam Deck performance reference — Generated illustration. Deck reference remains 720p60 or 1080p30, not 4K60. Illustration only; not a game capture, launcher screenshot or hardware test.

High resource usage is not a malware diagnosis or a safety guarantee. Use the safety guide for suspicious files. For a reproducible stock-build performance problem, send the LOG using the official reporting rules.

Questions

Is the shader hitch a bug?

The developer describes 15 to 60 minutes of compile time after an update as expected. Default is the baseline preset. Ultra is called out as heavy.

Does high CPU use prove a shader rebuild?

No. The developer describes cache warm-up after updates, but does not publish a CPU-usage threshold that diagnoses it. Check version, settings, duration and whether the problem persists after warm-up.