Reviewed, reproducible library and add-on catalogs for RenderPilot.
RenderPilot Libraries tracks exact upstream releases, verifies installable artifacts, generates deterministic public contracts, and publishes immutable assets for the RenderPilot application.
Application code lives in the main RenderPilot repository.
This repository is the catalog producer for RenderPilot. It keeps reviewed source data, immutable provider locks, public schemas, generated manifests, and the tooling that connects them.
- Tracks exact upstream identities. Provider records bind releases to reviewed package, tag, commit, archive, and source-tree evidence instead of mutable download pages alone.
- Verifies installable artifacts. Validation covers hashes, PE metadata, architecture, exports, Authenticode policy, legal documents, and provider-specific layout rules.
- Generates deterministic catalogs. Library vendor snapshots, the shared index, and add-on manifests are rebuilt from declared authoring sources and checked into the repository for review.
- Publishes in dependency order. Content-addressed assets and immutable vendor snapshots are uploaded and verified before
libraries/v1/index.jsonbecomes the new catalog commit point. - Separates discovery from publication. Refresh, materialization, generation, review, and R2 publication remain explicit operations with different authority and failure modes.
Current RenderPilot builds consume the versioned libraries/v1 and addons/v1 contracts.
| Group | Cataloged components |
|---|---|
| NVIDIA | DLSS Super Resolution, Frame Generation, Ray Reconstruction, and related runtime packages |
| AMD | FidelityFX packages imported from reviewed GitHub release trees and historical overlays |
| Intel | XeSS packages imported from reviewed GitHub release trees and historical overlays |
| Microsoft | DirectStorage, DXC, and D3D12 Agility SDK packages imported from NuGet |
| Valve | OpenVR runtime packages with export-surface metadata |
| Xiph | Reproducible Windows builds of reviewed Ogg and Vorbis source pairs |
| Add-ons | RenoDX, Luma Framework, ReShade, and OptiScaler source manifests |
| Settings | NVIDIA DLSS preset and settings contracts |
Every installable file and legal document is content-addressed. A published vendor snapshot is immutable; the index references it by object key, SHA-256, and size. RenderPilot therefore observes either the previous complete library catalog or the next complete catalog, never a partially published generation.
The repository pins the latest Node.js LTS release in .node-version and pnpm in package.json. Install the pinned pnpm version explicitly on a fresh machine. PowerShell 7 and Windows are additionally required for PE inspection, Authenticode verification, and reproducible Xiph builds.
npm install --global pnpm@12.8.1
pnpm install --frozen-lockfile
pnpm run checkpnpm run check is the complete repository gate. It validates formatting and documentation, schemas, provider locks, generated output, unit tests, upstream Wiki synchronization, slugs, and add-on payload layouts. Use pnpm run check:offline for the deterministic network-free subset.
Refresh and publication commands can write reviewed catalog state or remote objects. Read the operations and publishing guide before running them.
| Path | Responsibility |
|---|---|
catalogs/libraries/ |
Reviewed provider configuration, immutable locks, curated sources, and overlays |
catalogs/addons/ |
RenoDX, Luma, ReShade, and OptiScaler authoring data, generators, schemas, and tests |
libraries/v1/ |
Generated library index and local vendor snapshot projections |
addons/v1/ |
Generated add-on manifests consumed by RenderPilot |
cdn/ |
Local content-addressed DLL transports and legal documents |
| Root JSON files | DLSS preset and settings contracts |
schemas/ |
Public and authoring JSON Schemas |
scripts/ |
Validation, generation, import, inspection, refresh, and publication tooling |
.github/workflows/ |
Validation, scheduled refresh, withdrawal, and R2 publication automation |
- Documentation hub — setup, architecture, catalog contracts, curation, and production operations.
- Contributing — the shortest path from a local checkout to a reviewable change.
- Library catalog model — identities, provenance, signatures, legal documents, transport, and generation invariants.
- Add-on catalogs — published contracts, authoring boundaries, curation, and Wiki synchronization.
- Operations and publishing — quality gates, refresh modes, automation, withdrawal, pruning, and R2 safety.
- RenderPilot — the desktop application and source-only CLI that consume these contracts.
- Public library index — the current production commit point.
Catalog data does not transfer ownership of third-party components. Upstream projects retain their own licenses, support policies, compatibility requirements, and distribution terms.