Frutiger Home Fatal Error and crashes
Record the exact Fatal Error and last action, update, and compare a small test property. A stuck gizmo, tiny object, export failure and connection failure have different checks; one old Intel Arc report does not diagnose every crash.
Separate a crash from a building or connection bug
A Fatal Error dialog means the application failed. It does not identify the cause by itself. Two demo reports described an Intel Arc startup failure and a crash during construction; they were different sessions, and neither establishes that every Arc card or every large property fails.
| What happens | First useful check |
|---|---|
| Fatal Error before reaching the house | Record GPU model, driver, Windows version and the exact dialog |
| Crash during one building action | Record the item, property and last action; compare with a small test property if possible |
| Tiny decor cannot be removed | Update to 1.0.8; it fixes collisions on some scaled-down decor |
| A gizmo is hidden or pixelated | Check the 1.0.6–1.0.8 selection and rendering fixes |
| A friend cannot join | Use the separate 1.0.2 networking checks |
| Export or property-mod selection fails | Check the 1.0.4–1.0.5 export fixes |
Start with the current version
Update through Steam and retry the smallest action that reproduces the failure. Record whether the process closes, returns to a menu or stays open with an unresponsive tool. A blocked transform handle is not the same failure as an application crash.
If one property triggers the issue, preserve that save before trying edits. Note whether a new small property behaves differently. That comparison can make a support report more specific; it is not a promise that the save is repairable.
Compare the actual requirements
Steam lists 64-bit Windows 10, DirectX 11, a GTX 1060 / Radeon RX 6600 class minimum and 15 GB available storage. Compare your hardware and available disk space with those requirements.
A PC supporting DirectX 12 can also support the required DirectX 11 features. The presence of DirectX 12 is not, by itself, a reason the game cannot run. Likewise, the install-space requirement does not establish that a particular mid-build crash was caused by disk streaming.
Send a useful report
Include the game version, GPU and driver, Windows version, exact error and the last action before it happened. For a property-specific failure, describe the object and whether the same action works in a small test property. Share a save or private log only through the developer's requested support method.
The old Arc report says reinstalling did not help that player. Do not repeatedly reinstall as though it were a published Arc fix. The Steam discussions are the developer's public bug-report route.
Sources
- Patch v1.0.8
- Patch v1.0.7
- Patch v1.0.6
- More Export Properties & Steam Workshop Fixes - Patch v1.0.5
- Networking Fix - Patch v1.0.2
Return to all guides.
