Skip to content

fix: use project-local inputs throughout renderer tooling - #22

Merged
omggga merged 1 commit into
mainfrom
fix/local-render-input-paths
Sep 9, 2026
Merged

omggga merged 1 commit into
mainfrom
fix/local-render-input-paths

Conversation

@omggga

@omggga omggga commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Summary

After removing the old sibling game-input directory, internal renderer/catalog commands and two local GOTY tests still looked there. Use local-data/inputs throughout those entry points and align the embedded OpenMW profile and TR release profile with the documented tamriel-data and tamriel-rebuilt/00 Core/Data Files layout.

The LAND diagnostic now uses the same five core plugins and no longer requires the unused Factions or Firemoth modules. Update profile/config/mount assertions and point the existing local GOTY checks at their actual input files. No game inputs, prepared map metadata or Release packages are added or changed.

Validation

  • Existing generated OpenMW configuration regression test failed with the old paths before the implementation fix.
  • Focused profile, mount, LAND and Original renderer tests: 55 passed and one filesystem-specific skip; both local GOTY tests ran with real inputs.
  • pnpm render:check all passed for all five maps using the default input root.
  • Direct LAND/OpenMW/catalog checks validated 8 input files, 10 pinned inputs and 5 catalog plugins respectively.
  • python3 -m tools.tr_release.cli check --profile local-data/render/tamriel-rebuilt/profile.json passed without a source-root override. The active production profile remains intentionally rejected for a new render.
  • pnpm verify and git diff --check passed.
  • Independent diff review found no blocking issues.

Existing local locks or renderer caches tied to the old paths/fingerprints may need regeneration. Existing rendered/publication evidence is not rewritten, and the fingerprint checks continue to reject incompatible resume state.

The TR configuration change requires Dataset review (trusted) for the exact PR head/base before merge. Public-opening follow-up checks are outside this PR.

@omggga
omggga merged commit ee7b31a into main Sep 9, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant