Hollow Knight: Silksong on PC: official version and experiment
An official PC route is linked separately below. The records on this page concern the PS5 executable or named homebrew build.
What is established for Hollow Knight: Silksong on PC? A Windows follow-up reaches opening gameplay on unmodified main 18c438b10, mostly at 60 FPS. The older PR-stack result is separate historical context.
Hollow Knight: Silksong on PC: compatibility evidence
The October 13 Windows follow-up names main 18c438b10 with no local source patches and no APS5/ANYPS5 environment variables. It reaches intro, menus and a new game using a DualSense, with working rendering, text and audio reported. Source ↗
The older main d70b8998 integration required a set of PRs and APS5_STORE_AT_FLIP=1. Do not copy those requirements into the newer record without checking its source. The documented scope is opening gameplay, not a finished campaign. Source ↗
Compare builds and reported hardware
| Hardware / platform | Build / reported result | Evidence |
|---|---|---|
| PPSA12544 Core i9-10850K RTX 3080 32 GB RAM · Windows | main 18c438b10 · no extra PRs or local patches Gameplay reported Intro, menus and opening gameplay; above 50 FPS and mostly 60 FPS reported with DualSense. Main snapshot · Test date unknown | Details ↓ Report ↗ |
Test reports
Hollow Knight: Silksong on PC · Windows · Main snapshot
Gameplay reportedIntro, menus and opening gameplay; above 50 FPS and mostly 60 FPS reported with DualSense.
- Title ID
- PPSA12544
- Test date
- Unknown — not stated in source
- Post date
- 2026-10-13
- System
- Windows 11 · NVIDIA 610.74
- Tested build
- main 18c438b10 · no extra PRs or local patches
- Reported CPU
- Core i9-10850K
- Reported GPU
- RTX 3080
- Reported RAM
- 32 GB
- Evidence
- ps54all ↗
Game 01.000.010; guest-module layout is described in the source. No full-game test or minimum specification is established.
Known limitations
- Game 01.000.010; guest-module layout is described in the source. No full-game test or minimum specification is established. Evidence ↗
Reported milestones
Intro, menus and opening gameplay; above 50 FPS and mostly 60 FPS reported with DualSense.
Source ↗
Common questions
Does this result apply to every build?
No. The source records apply to their named platform, revision and patches. A higher stage on a contributor branch is not a result for every release.
Is this a full-game completion report?
No complete playthrough is established by these selected records. Read the specific scenes, test duration and limitations before extending the result.
Hollow Knight: Silksong on PC: is this a complete playthrough?
The selected reports establish only their recorded scenes and stopping points. None of these entries establishes full-game completion. Read the original report before extending its scope.
Hollow Knight: Silksong on PC: are these minimum requirements?
No. The hardware belongs to a particular reported build and test. It is not a minimum specification, a recommendation for the official PC edition or a prediction for another machine.
Hollow Knight: Silksong on PC: which game edition is tested?
Hollow Knight: Silksong reports here concern the PS5 edition identified by each title ID. Results from another console generation or the official PC edition must be kept separate.
Has Port Record reproduced this test?
No. These are reviewed community reports. Follow the original source for its complete environment; our review date is not a test date.
Hollow Knight: Silksong on PC: prepare the same build
Use the title’s build and patches as your reference. These tools prepare input and compare records; they do not reproduce a test.
Relinker command builder ↗
Choose a platform, check module folders and generate a quoted v0.1.2 command.
ELF header checker ↗
Read the first 64 bytes of a local file. Inspect the format before conversion.
Compare my PC ↗
Find hardware components in sourced reports. See the exact build and limitations.
To investigate Hollow Knight: Silksong on PC, start from the source attached to the exact platform and build record. Preserve the local patches, game version and observed scene before comparing a new result. A source update can change the context after this review.