Dressmaker Controls After Build 443: Zoom, Pan and Orbit, Mapped

At a glance

The mannequin camera is the part of Dressmaker that changed most in the October patch, and it is the part most existing guides still describe the old way. Three bindings matter, and all three arrived with Build 443 on October 14, 2026.

What Build 443 changed, in the developer's words

The camera section of the October patch notes is one paragraph, and it is worth reading in full because it explains both the new bindings and why they will not be the last ones:

Two phrases in that paragraph carry more weight than the rest. The first is "WIP" — work in progress. The developer is telling you the current camera is an interim state, not a finished design. The second is "a more drastic rework", which is a warning that the bindings on this page may be replaced again rather than refined.

The notes also acknowledge the cost of the change directly, in the section above the camera paragraph, and it is unusually candid about why it happened:

That is the developer describing a specific problem: players had already adapted to the old camera, and the patch invalidated that adaptation on purpose. If the controls feel worse to you than they did before the patch, that is not a misremembering — the developer expected exactly that reaction and accepted it.

The mannequin scene: zoom, pan and orbit

Three separate actions now, where the old camera folded zoom and tilt together. Take them one at a time.

Zoom

Hold Ctrl and scroll the wheel. The distinguishing word in the notes is smooth: zoom is continuous rather than stepping through fixed distances, so small wheel movements produce small changes. If you are used to tapping a key and arriving at a preset distance, the new behaviour will feel imprecise until you adjust — a single wheel notch no longer moves you a whole step.

Pan

Hold the right mouse button and drag. This is a held gesture rather than a toggle, and it is the binding most likely to collide with something else you do with the right button, such as cancelling an action. Player posts on the Steam forum describe using right-click to interrupt a trim placement and then continuing from the last stitch, which is worth knowing before you decide the right button is "just" the camera — see the trim placement page for that workflow.

Orbit

The notes say keyboard orbiting was added and stop there. They do not name a key, and the store screenshots do not show the mannequin scene's control strip, so there is no first-party source for which keys orbit. Player threads on the Steam forum describe orbiting with the keyboard while the mouse is elsewhere, and third-party control pages list A and D. Neither is developer documentation, and this page does not present either as confirmed.

On a Mac

Dressmaker ships for macOS as well as Windows, and the notes say "holding control" without saying which modifier that means on a Mac keyboard. This page cannot resolve that from the developer's text. If the zoom gesture appears to do nothing on a Mac, try the other modifier before assuming the binding is broken — the ambiguity is in the source, not in your keyboard.

The cutting room

The cutting room got a smaller change and two fixes that matter more than the camera did:

That second half is the useful one. Panning with the wheel is only available while the scissors are selected, so a wheel that does nothing in the cutting room usually means nothing is selected rather than that panning is broken.

The wheel's job in this scene has now been redefined twice. A week before the big patch, Build 410 removed an unwanted behaviour: "Mouse wheel should no longer rotate panels in cutting room when mouse is over inventory." Read the two changes together and the wheel went from accidentally rotating a panel to deliberately panning the view — which is a reasonable design, but it does mean advice written in the first weeks after launch describes a wheel that did something else entirely.

The two fixes in the same scene are worth knowing because they describe problems players were actually hitting. The scissors could previously discard fabric on a stray click, and the notes apologise to a specific person for it:

Separately, leaving the cutting scene mid-animation could leave the tool unusable — "Fix being able to leave cutting scene during scissor animation, which can leave the scissors in a broken state". If you lost fabric or had a stuck tool before October 14, both of those are documented as fixed rather than as things you did wrong.

The same patch also added tooltips to the cutting room buttons, moved several buttons for clarity, added a button that grabs every panel piece at once, and fixed a white-out effect the notes call a "'flashbang' glitch". The full-panel button is the one people search for — it has its own section on the commission page, because a panel left behind in the cutting room is one of the reasons a dress will not submit.

The sewing scene

The sewing scene is the one place where the developer's own screenshot shows the bindings, so this is the most firmly sourced part of the page. The store screenshot of the machine has a strip along the bottom reading Space Sew, A D Rotate, W S Change Speed, and a circular percentage counter next to the needle.

Thread colour is the one binding on this page with a dated origin of its own. It was added in Build 410, a week before the big patch: "You can now change the thread colour in the sewing scene (by clicking on the spools)". Before that build the spools were decoration. If a guide tells you thread colour is fixed once you start, it is describing the build from before September 24.

Build 443 lists a "minor change to sewing scene animation for UX" without describing the change, so this page does not describe it either. What the notes do spell out is the accessibility route out: the "Less Animation" option disables the scrolling textures and the zoom in both the sewing scene and the cutting room, which is the closest thing to an official answer for anyone who finds the motion uncomfortable.

The sizing room

One line, and it is the least ambiguous in the whole notes:

Two input methods for the same control, which is rare in this game's current state — most actions have one. The same patch also fixed an animation bug in the measuring scene that appeared at low frame rates ("Fix animation bug in measuring scene at low framerates"), so if sizing felt unreliable on weaker hardware before October, that is a documented cause rather than your imagination.

Trackpads and laptops: no official answer

This is the largest gap on this page, and it deserves to be stated plainly rather than filled in. The patch notes describe a mouse wheel, a right mouse button and keyboard orbiting. They contain no mention of a trackpad, no mention of a touchscreen, and no alternate scheme for hardware without a scroll wheel.

What the notes do provide is a workaround that does not depend on a mouse: keyboard orbiting. Since orbiting was added as a keyboard control, a player who cannot right-click-drag can still change the viewing angle — but not pan, because pan is right-button only, and not zoom, because zoom requires a wheel. Those are the two actions with no published alternative.

Gamepad and Steam Deck

Neither is supported yet, and both are on the record as a sequencing decision rather than a rejection. The October patch bundles three separate things into one sentence — rebinding every control, gamepad support, and Deck support — calls all three a high priority, and schedules none of them:

The full sentence and what it separates are set out on the platforms page, which is where the controller question belongs. What matters here is narrower: the bindings on this page are the only scheme the game ships with, and they do not change on Deck because there is no Deck layout to change. Steam rates the game Playable rather than Verified, so it runs with a working default configuration while carrying known interface problems.

Why this page carries a version stamp

Every binding above is scoped to Build 443, published October 14, 2026, and the developer has already said the camera will change again. Two sentences from the patch notes make that explicit: "We are still not happy with the controls here and will be making more improvements in the future", and "We are considering a more drastic rework of camera controls".

The practical consequence is that this page can go stale in a way most guides do not. A guide to a finished game's controls stays correct; a guide to this game's controls is correct until the next patch. Two triggers would make the current text wrong: any change to the camera paragraph in a future patch note, and the arrival of controller rebinding, which the developer has said is planned but not scheduled. The review date at the top of the page is the date the sources were read, not a date on which the bindings were tested in a running build.

If a binding is not working

Before treating anything as a bug, three checks resolve most of the confusion reported on the Steam discussions:

1. Read the on-screen strip. Build 443 added control hints to the bottom of the screen specifically because features were going unnoticed. If the strip shows nothing, you are in a scene with no active hints rather than in a build that lacks them.
2. Check which scene you are in. The wheel does three different things depending on where you are: it zooms in the mannequin scene with Ctrl held, pans in the cutting room only while the scissors are selected, and adjusts gears in the sizing room. A wheel that "does not work" is usually a wheel in the wrong scene.
3. Confirm your build. Every binding on this page post-dates Build 443. The developer's patch announcements name each build; if yours is older, the camera behaves the old way and no guide can make the new bindings appear.

Past that point the honest answer is that the controls are a work in progress by the developer's own description, and the published route for reporting an input problem is the support address rather than a forum thread:

• [email protected] — the support address listed in the game's own support field on Steam.
• Steam Discussions — Dressmaker — where players compare bindings. Useful for finding out whether others see the same thing; not a source of official answers.

One reason to expect slow movement on input issues: the developer has publicly described the team's size. In an announcement on October 1, 2026, it referred to having "only about 1.5 programmers". That is not an excuse offered on the developer's behalf here — it is the stated context for why a high-priority item can stay unimplemented across two patches.