The official Steam listing gives a useful Windows baseline for DragonSword : Awakening: Windows 10, 8 GB RAM, GTX 1660, DirectX 12, 25 GB available space and an SSD at minimum. The recommended listing raises the CPU to an i7-9700F, memory to 16 GB and graphics to an RTX 3060. This guide explains how to compare a PC with those fields and how to report Steam Deck or Proton observations without turning them into unsupported product claims.
Minimum and recommended are different questions
Minimum asks whether a machine matches the published floor. Recommended asks whether it matches the higher configuration the publisher chose to list. Neither line says what frame rate you will receive in every area. Compare CPU, GPU, RAM, Windows, DirectX and storage separately. If one field is below the minimum, report that field rather than hiding it behind an overall “almost recommended” label.
The SSD requirement deserves its own check. A player may have enough free space but install on a slower drive. The Store page lists 25 GB available and an SSD, while Steam may need temporary room for an update. Keep spare capacity and record whether a loading issue appears during first launch, a story scene, a Dungeon or a co-op session.
A reproducible Windows test
Write down the CPU, GPU, RAM, Windows build, GPU driver, resolution and storage type. Start from a known preset, load the same scene and observe for a fixed short period. Record the issue category: crash, hitch, low frame rate, blurry image, input delay, audio fault or network disconnect. Do not compare two machines if the resolution, driver and scene differ.
Change one setting and repeat the same test. If the result improves, say which setting changed and whether the improvement was visual, input-related or performance-related. If it does not, restore the previous setting and try another hypothesis. This method produces a troubleshooting note that can be checked by another player.
Driver and update notes
The public Steam page did not show a stable version label in this audit. Include the test date and installed build information when available. If an issue starts after a Steam update or driver update, say which change happened first and avoid claiming causation without a comparison. Check the official Steam News index for publisher context.
Do not recommend downloading a driver from an unofficial mirror or replacing game files from a guide page. Use Steam file verification for a missing or corrupt file, preserve an error message, and refer to official support channels for account or purchase problems. A fan guide can explain a test without asking for credentials.
Steam Deck and Proton reporting
Steam’s official product copy reviewed here scopes the product to Windows PC and does not confirm Steam Deck or Proton support. If you test it, use a clear label such as “community observation on SteamOS and Proton version X, checked on date Y.” That label protects readers from mistaking a single device result for a publisher promise.
Record boot, menu, story, combat, save, sleep/wake and co-op behavior separately. A game can launch and still fail in a later scene or lose input after waking. Write the display resolution, frame cap, graphics preset, upscaler, TDP or battery profile if relevant, controller layout and session length. Repeat the most important test after a patch.
Common compatibility mistakes
Matching the GTX 1660 name is not enough when a laptop power limit or driver changes behavior. Matching 8 GB RAM is not enough if other programs consume memory. Having 25 GB free is not enough if Steam cannot reserve update space. A successful menu boot is not enough to call the game stable. Each claim needs its environment.
Another mistake is copying a Deck preset from an unrelated Unreal Engine game. The visual workload, shader behavior, input and world streaming can differ. Use a preset as a starting experiment, then publish only what the test supports. If there is no repeatable improvement, remove the recommendation rather than padding the page.
Requirements checklist
- Confirm AppID 4570720 and the official Store page.
- Compare every minimum field, not just the GPU.
- Leave space beyond the published 25 GB and install on an SSD.
- Record Windows, driver, resolution, scene and storage type.
- Change one setting per test.
- Mark Deck/Proton findings as community observations.
- Recheck after Steam or driver updates.
Does the minimum spec promise 60 FPS?
No. It is a compatibility baseline, not a frame-rate guarantee.
Is a Steam Deck preset official?
Not from the reviewed Store copy. It must be reported as a dated device and Proton observation.
What should I do after a crash?
Preserve the error, confirm the build and environment, verify files through Steam, and check official update/support channels.