OFFICIAL DEMO
What the official demo confirms
Use the official demo to evaluate controls, readability and performance without treating it as proof of every retail-game rule.
01Published demo scope
Capcom describes a demo featuring Musashi, a Spirit Mirror, Photo Mode, Oni Vision and soul absorption. The PlayStation listing names Sasaki Ganryu and Daidara as demo encounters.
02Save-data boundary
The PlayStation demo listing says demo progress does not transfer to the full game. It separately states that users with demo saved data can obtain the Kubi Akari charm in the full game. Keep qualifying demo save data available to the entitlement check and recheck the current listing; the page does not document cross-platform, cross-account or cross-region handling.
03What the demo can and cannot establish
Use the demo as a bounded test rather than a substitute for the current retail build.
| Question | Demo can help answer | Demo cannot prove |
|---|---|---|
| Controls and camera | Whether the available layout and camera feel readable on your device. | That every retail option or balance value is unchanged. |
| Performance | How this demo build behaves on your current hardware and settings. | Guaranteed performance in every retail area or after every update. |
| Progress | Whether demo save data exists on the same account. | Transfer of route, inventory, souls or story progress—the listing says progress does not transfer. |
04A 20-minute evaluation plan
Run the demo as a repeatable purchase test rather than rushing to finish it. Keep the same display, audio device and controller you expect to use for the full game.
- Minutes 0–5: inspect control, camera, subtitle, audio and display options before changing anything.
- Minutes 5–10: use the default settings and note camera readability, input comfort and whether important prompts remain legible.
- Minutes 10–15: change one relevant option at a time. On PC, record resolution, preset and any upscaling choice before judging performance.
- Minutes 15–20: revisit the same encounter or area after the change and compare the same observable issue.
05Keep observations separate from expectations
Use three columns: observed in this demo build, published for the retail game, and still unknown. For example, a frame drop observed in one demo scene belongs in the first column; a full-game feature named on a current store page belongs in the second; late-game variety belongs in the third. This prevents a short demo from being treated as a complete review.
06Save-data and reward checklist
The PlayStation listing ties the Kubi Akari charm to the presence of demo save data and separately states that gameplay progress does not transfer. Keep qualifying save data until the reward is confirmed and recheck the current regional listing. Do not interpret the published condition as cross-platform entitlement, a completion requirement or transferred inventory.
07What useful first-hand evidence would look like
If this guide later publishes demo observations, each note should identify platform, demo version, date, display mode, input device and the exact option tested. A screenshot should document the menu or result it supports, not merely decorate the page. No such hands-on claim is made in the current guide.
OFFICIAL VIDEOS
SOURCES & FURTHER READING