Devil May Cry 3 HD Collection · Evidence-first C++20 research
DMC Native Reader for Android — DMC3 Model & Texture Inspection
DMC Native Reader is the Android-facing inspection application in the DMC Rengine ecosystem. Its current main branch intentionally promotes MOD, SCM, DDS and PTX only, using canonical DMC Rengine readers and a capability-driven UI. This page targets DMC3 Android viewer searches without claiming an all-platform release or unsupported editor capabilities.
Current Android application surface
- MOD uses the canonical DMC Rengine structural reader and Architecture v2 adapter for model/inspection output; SCM follows the corresponding canonical scene reader path.
- DDS provides bounded DMC3 texture validation and image preview, while PTX provides bounded texture-bundle reading with DDS child resources and parent navigation.
- Unknown or unpromoted formats fail closed in the Android application's main module registry instead of being exposed through a wildcard parser.
DMC Native Reader app is not the same as the wider C++ integration registry
- DMC Rengine contains a broader Native Reader integration registry for canonical C++20 parser modules, but registry presence does not automatically mean the Android application has promoted the same user-facing capability.
- Archive traversal and provenance remain GDSpaces/PocketGDS responsibilities; the Android reader receives typed materialized resources when its current app module set supports them.
- This separation keeps product claims tied to the application build while allowing the C++ core to evolve independently as reverse evidence is promoted.
Platform and authoring boundary
- The current product evidence supports Android. Windows, Web and iOS are not advertised here as shipped Native Reader platforms until their own implementation and build evidence are promoted.
- MOD/SCM reading does not imply unrestricted model or scene editing, and DDS/PTX inspection does not imply arbitrary production texture replacement or original-game acceptance.
- Use the format and status pages for the canonical technical maturity of each underlying reader or writer capability.
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.