Devil May Cry 3 HD Collection · Evidence-first C++20 research

DMC3 SHW Format — DMC Rengine

Entry point for SHW structural research. Current payload coverage, reader scope and unresolved semantics remain bounded by the canonical status and evidence records.

What SHW research covers

SHW is approached first as a binary structure: record boundaries, payload organization and preserved unknown data are established before stronger semantic labels are promoted.
The filename or surrounding game context is not considered enough evidence to assign every record a shadow or rendering meaning without corroborating runtime or corpus proof.
Structural reader coverage and semantic completeness are deliberately separate concepts so downstream tools can expose known data without hiding unresolved regions.

Questions this entry point helps answer

What can the project safely say about SHW structure today without turning filename-based expectations into format facts?
Which boundaries matter when exposing SHW records in a native reader while some payload semantics remain unresolved?
Where are current SHW promotion status and unresolved evidence recorded for contributors or tool authors?

SHW at a glance

Identifiers: SHW
Domain: Geometry

Identity: EXE_CONFIRMEDPurpose: EXE_CONFIRMEDSchema: PARTIALProduct: runtime-only

Canonical source

This page is a public discovery and readability layer. It does not replace the repository's current implementation, status, evidence or format-specific documentation.

Open canonical GitHub source

Evidence boundary

A parser is not automatically a writer. A successful writer is not automatically equivalent to Capcom's offline tools. Synthetic validation does not establish original-game behavioral equivalence.

Use the current status for promoted capabilities and open proof gates.