1. Choose by computer and episode
| Your setup | Download to look for | What is confirmed |
|---|---|---|
| Windows, Episode 2 | DX12 · Build37 | Recommended in the Episode 2 instructions |
| Very old Windows computer, Episode 2 | DX11 · Build37 | Alternative named for very old computers |
| Windows, Episode 3 | WINDOWS_DX11 / WINDOWS_DX12 · b105 | Both Windows variants appear in the official post |
| Mac, Episode 3 | MAC · b105 | A Mac archive is visible; detailed requirements are not visible in the public preview |
2. Does DX12 guarantee better performance?
We have no measured frame-rate comparison for these downloads. The Episode 2 DX12 recommendation is a developer instruction, not a benchmark result. Keep it distinct from the Steam requirements, which list hardware for the planned store edition.
When comparing DX11 and DX12, keep the episode and build number the same. Record the GPU, resolution, settings, test scene and whether mods are present. Changing the game build and graphics variant together makes it harder to identify which change affected the result.
3. Which file should a Mac user choose?
The Episode 3 public attachment list includes Family_Time_Ep_3_MAC_b105.zip. Choose the MAC-labelled archive through that official post, rather than either WINDOWS-labelled file. Seeing a Mac filename confirms an offered package; it does not specify the minimum macOS version or Intel/Apple Silicon compatibility.
Before subscribing for a specific Mac, ask the developer to confirm your macOS version and processor. Request Mac installation instructions if they are not provided with your access. We have not run this package. Windows mod instructions do not establish Mac mod compatibility.
4. Keep a useful record when a build will not start
- Record the complete archive filename, operating system, graphics card and exact error message. Include whether the failure happens at startup, new game or loading an existing save.
- Record whether the installation is unmodified or uses a loader and mods. Keep the working version and original save while checking the official post for a replacement build.
- Send the report to the support route identified by the developer. A filename and reproducible startup step are more actionable than saying only that DX12 is broken.