Azimuth DLAA

4. Set anti-aliasing to Off in Azimuth.

5. Launch a supported game.

The mod automatically selects the correct game profile. azimuth_dlaa.log records which profile was detected.

Controls

•F11 - toggle DLAA on/off.

F11 works during gameplay and photo mode. If a photo-mode frame is completely stationary, the visible result may not update until the game redraws; moving the photo camera slightly forces a redraw.

Optional NVIDIA Profile Inspector tweaks

These settings are not required for Azimuth-DLAA to work.

DLAA presets can be forced by adding azimuth.exe to NVIDIA Profile Inspector and changing the DLSS preset there.

At 4K, I found preset E (CNN) and K (Transformer Gen 1) are good choice while preset M (Transformer Gen 2) is too heavy with close to no difference.

Results may vary depending on resolution.

I also saw a substantial performance improvement on my system (RTX 4070 Ti Super + Ryzen 5600) by forcing Resizable BAR / ReBAR for the Azimuth.exe profile.

Architecture

The source is deliberately split so adding another game does not require another fork of the mod:

A game profile owns only the things that are genuinely game-specific: exact motion-vector/resolve shader hashes, the motion-vector reconstruction shader, expected resolve formats, jitter depth formats, resolution scale, and any small compatibility flags.

The shared core does not identify games by executable filename. It locks onto the first exact known game shader it sees and will not switch profiles later in the process. This keeps unrelated profiles isolated.

For FM5/FM6, the intended workflow is to discover their render passes in a separate diagnostic branch and then add src/games/fm5.c / fm6.c plus one registry entry. The stable FH2/FH3 profile files should not need to be modified.

How it works

For supported games Azimuth-DLAA:

•identifies the exact scene color/depth resolve,

•replays the game's velocity pass into full-resolution R16G16_FLOAT motion vectors,

•injects temporal camera jitter using the game profile's scene-depth rules,

•evaluates NVIDIA DLAA on the HDR scene image,

•restores the game's D3D12 state,

•and falls back to zero motion vectors with a history reset when the normal velocity pass stops in pause/photo states.

FH2 and FH3 intentionally keep separate profile details. For example, their motion-vector constant-buffer row layouts differ, and FH3 requires additional D32 depth handling.

Logging and reports

The mod writes azimuth_dlaa.log next to the DLLs. When reporting an issue, include the log, Azimuth version, GPU, NVIDIA driver, resolution, game/DLC, and where the problem occurred.

Building from source

The build produces two project DLLs:

•dxgi.dll - shared Azimuth/D3D12 hook and per-game integration

•azimuth_ngx.dll - shared NVIDIA NGX/DLSS bridge

The NGX bridge is built with MSVC, while the DXGI proxy is built with Zig/MinGW.

1. Obtain the NVIDIA DLSS SDK separately and place it in third_party/DLSS, or set DLSS_SDK.

2. From an x64 Visual Studio tools prompt, run bridge\build_bridge.bat.

3. Run ./build.sh to build dxgi.dll.

4. Run ./build.sh release to create a release ZIP after both project DLLs have been built.

The release target intentionally does not bundle nvngx_dlss.dll.

Credits

Azimuth-DLAA is based on FH2-FSR4 by aranhoso / Guilherme Fernandes Medeiros. That project provided the original founda