ATS Visual Toolkit Phase 3.3.2 database directory

Generated runtime mapping files:

  shader_reference_manifest.csv
  effect_shader_runtime_catalog.csv
  effect_pass_runtime_catalog.csv
  effect_catalog_metadata.json

Personal runtime files:

  user_shader_aliases.csv
  shader_editor_catalog_<ATS-FNV64>.csv
  shader_editor_catalog_<ATS-FNV64>_presets.csv

The effect catalogs map captured shader identities to official effect candidates and exact VS/PS pass pairs. The user alias file stores personal names, categories, and notes separately so generated catalog updates do not overwrite them.

The editor catalog stores shader/range/register labels, display modes, and slider ranges. Presets store per-register override values and enabled channels.

Compiled replacement shaders belong in the sibling folder:

  ATSVisualToolkit\replacements\

Selected shader exports belong in:

  ATSVisualToolkit\decompiled\

Bulk export sessions belong in:

  ATSVisualToolkit\decompiled\export_sessions\shader_export_YYYYMMDD_HHMMSS\

Optional command-line shader tools belong in:

  ATSVisualToolkit\tools\

Phase 3.3.2 retains the Phase 3.2.7 replacement policy and accepts compatible compiled DXBC/CSO replacements for a selected live vertex or pixel shader without requiring Commit Shader. Commit remains part of targeted constant-buffer discovery. It also retains original bytecode and can reconstruct low-level HLSL directly from supported DXBC assembly, compile it with D3DCompile, and validate the rebuilt interface before replacement loading.

Do not copy ATS-build-specific editor catalogs or effect catalogs to a different ATS build without revalidating shader hashes and ranges.

The retained Phase 3.2.7 faithful pipeline also reconstructs supported integer, bitwise, shift, and typed Texture2D.Load instructions while preserving exact resource bindings recovered from reflection or authoritative executable DXBC declarations. Constant buffers are validated by type, slot, count, and byte size so reflection-only placeholder metadata cannot cause a false rejection.

Phase 3.3.2 bulk sessions export every runtime registry identity present when the session starts and create a continuously flushed per-session log plus CSV manifest.
