Dressmaker crashes, saves and lag
Problems with the game itself rather than with a dress. Find your symptom, try the first fix, and read on only if it does not help.
- Opening the cutting table freezes or closes the gameKeep the error and save before trying the table again
- Progress missing on a second computerCheck the original machine before choosing a cloud copy
- Won't start, or crashes on launchUpdate Windows and the graphics driver
- Error box, then pink fabricsSend your Player.log on the Steam discussion board
- Whole PC shuts down or bluescreensNote your hardware and report it
- Old save will not load, or progress vanishedPreserve local files before trying a reset
- New progress does not saveCheck Windows folder protection
- Laptop runs hot, fans loudCap the frame rate in the GPU panel
- Lag since Build 410Report it on the Steam discussion board
- Motion sickness while sewingCheck what Sewing Assist changes
The game crashes when opening the cutting table
If choosing a pattern and fabric works but opening the table freezes or closes the game, stop repeating that action. There is no confirmed fix for this specific trigger. Keep the dress and save; discarding either is not a proven repair.
| What happens | What to keep | Next step |
|---|---|---|
| The game closes, with or without a Unity error | Exact error text, last action, pattern and fabric, installed game version | Copy the log and back up the save before another launch. |
| The game stays open but stops responding | Whether sound or the pointer still moves; the last screen reached | Describe the freeze separately from a crash that exits the game. |
| The game runs, but materials are missing | Whether this followed installing, removing or updating a mod | Use the missing-content checks instead of assuming a cutting-table crash. |
- Preserve the files first. After closing the game, follow the save backup steps. On Windows, copy
Player.logfrom%USERPROFILE%\AppData\LocalLow\Cozy Lives\Dressmakerbefore launching again. - Record the platform. On Windows, include the graphics card and driver. On Steam Deck, include the SteamOS version and selected compatibility setting. Include installed mods and any recent changes without assuming they caused the crash.
- Use one check at a time. Install available game updates and, if you have not already, verify the game files. A successful file check does not establish that the crash is fixed.
- Keep a repeatable failure for support. If the same action still fails, use the report checklist with the saved log and exact steps. Avoid repeatedly reinstalling, deleting saves or switching compatibility versions without a specific reason.
It will not start, or crashes on launch
Bring Windows and the graphics driver up to date: on an outdated operating system the game can flash a loading screen and close. To read the crash log on Windows, open %LocalAppData%Low\Cozy Lives\Dressmaker and read Player.log in Notepad.
If it still will not start or save:
- Close Dressmaker, exit Steam completely rather than closing its window, and start the game from the Steam Library.
- Verify the game files: Library, right-click Dressmaker, Properties, Installed Files, Verify integrity of game files.
- Check Windows security, which comes up next.
If none of that works, try renaming the D3D12 folder inside steam\steamapps\common\Dressmaker (to D3D12_old, say) and starting the game again. Rename it back if it makes no difference.
An error box, then pink or missing fabrics
If the game shows a Unity error box on start and closes, Alt+Enter while the box is up may reach the menu, but the fabrics then show bright pink or no texture at all, so it is not a way to play. Send your Player.log (the path is above) to the developer through the Steam discussion board, with your graphics card and driver version.
The whole PC shuts down or bluescreens
On a few machines the game takes the whole computer down after 20 to 35 minutes, sometimes in the middle of sewing and sometimes as a bluescreen. Capping the frame rate is worth a try, though it has not always helped. If it happens more than once, stop playing and report it on the Steam discussion board with your graphics card, driver version and Player.log.
Old save will not load: preserve it before trying a reset
If a new shop opens but your old run will not load, treat that separately from Windows blocking every save. Keep the old files, even when the game calls them corrupted. There is no verified universal repair for this symptom.
- Close the game and make a separate copy. On Windows, paste
%USERPROFILE%\AppData\LocalLow\Cozy Lives\Dressmakerinto File Explorer. Copy the entire folder to another location, keeping its original names. Do this before deleting a slot, resetting, replacing a file or testing a fresh run. - Look for another copy, without overwriting this one. Open Steam Cloud remote storage in your Steam account. If Dressmaker files are listed, compare their timestamps and download them into a separate folder. A synced copy may already contain the same problem; its presence does not prove it can restore your progress.
- Keep the error and log with the save. Note the affected slot, installed build, last successful load and whether the failure followed a crash, update or mod change. Preserve
Player.logbefore more launches replace useful context. Use the bug-report checklist with the saved copy; do not edit JSON values just to make an error disappear.
Which files are worth keeping?
The following names and behaviours are verified in the older Build 410 code. Keep these files if present; they are clues for recovery, not a promise that a newer build can load them.
| File | What the inspected code does | What to do |
|---|---|---|
player.json / playerN.json | Uses a separate filename for the selected save slot. | Copy every slot, not only the unnumbered file. |
.lastgood | Copies the slot after a successful normal load. | Keep its original timestamp; the name alone does not prove it predates the problem. |
.bak | Copies the existing slot when resetting it. | Preserve it before another reset can replace it. |
.corrupt | Keeps a copy when loading returns no usable save. | Retain it for diagnosis rather than deleting it. |
Only one dress missing while the rest of the shop loads? First check its sketchbook page. That is a different problem from a whole save that will not open. Mac save locations can differ from log locations; do not overwrite a folder based only on a matching name.
It will not save, or starts over
Does ModLoader show a saving-disabled or save-protection warning? Follow the mod-specific warning checks first.
Windows can block a game from writing its save data. The setting to check is Controlled Folder Access, a Windows security feature that stops apps writing to protected folders: make sure it is not blocking Dressmaker.
Progress missing after switching computers
First preserve both local save folders and any cloud copies. Do not start a new run over the affected slot while checking which copy holds your progress.
| What you see | Next check |
|---|---|
| The original computer still has the latest progress | Check Steam on that computer for a completed cloud sync before launching on the second machine. Offline play does not sync until Steam is online again. |
| Steam says it cannot sync | Resolve the sync error before continuing. Launching despite the warning can create a conflict or lose progress. |
| A cloud conflict asks which files to keep | Compare the timestamps with your last successful session. Keep backups first; do not pick a copy merely because it is labelled cloud. |
| Moving between Windows, Mac or Steam Deck | Cross-platform sync depends on the game. A Steam Cloud badge alone does not establish that these platforms share compatible saves. |
A cloud copy may already contain the same missing progress. If neither copy works, keep the files for diagnosis; syncing again is not a guaranteed recovery. Platform details · Steam Deck guide.
The save files look to be in C:\Users\<you>\AppData\LocalLow\Cozy Lives\Dressmaker. Copying that folder to another Windows PC is untested, so if you try it, back up the folder on both PCs first and keep the game closed.
A laptop running hot
On recent gaming laptops the GPU can run as hot as in much heavier games, up to 70°C even with a lower resolution and the frame rate capped at 30 in the game. Try forcing a 60 FPS limit in the NVIDIA control panel rather than in the game.
Lag since Build 410
If the game started lagging after the Build 410 update, while decorating or with the sewing machine jumping ahead and back off the line, report it on the Steam discussion board with your hardware. What Build 410 did change is on patch notes.
Motion sickness while sewing
Enable Less Animation in Build 443 to disable scrolling textures and zoom in the sewing and cutting scenes. You no longer need to rely on Sewing Assist to try to reduce camera movement.
| Option | What it changes |
|---|---|
| Less Animation | Disables scrolling textures and zoom in sewing and cutting. |
| Sewing Assist | Helps steer fabric along the seam; this is a separate setting. |
| Ctrl + mousewheel | Manually zooms the mannequin view, not an automatic-sewing-camera toggle. |
The patch also reduces the photo flash and fixes a cutting-room flash glitch. It does not claim to eliminate every crash or every source of discomfort. Open the current camera controls.
Problems inside a dress or a commission, from a missing Finish Dress button to a commission that vanished, are on known bugs and fixes and commission disappeared.