@@ -28,6 +28,8 @@ Every panel, sheet, dock, toolbar, menu, toast and the phone layout grows or shr
   have to resize them again.
 - The scale is applied before the app draws its first frame, so a reload never flashes the old size.
 - On a small phone, 150 % leaves less room for the scene; 120–130 % is often the best balance there.
+- *New in 1.63.* The scale also grows the panel tab strips and menus, so a touch screen can have bigger targets
+  everywhere.
 
 ![The Accessibility page at 150 % on a folded phone: bigger type and bigger controls, with nothing pushed off the screen.](img/accessibility/scale-150-phone.webp){ .shot .fade-b width="390" height="640" loading=lazy }
 /// caption
 
@@ -126,6 +126,30 @@ camera's own look instead of the scene's.
 `browser`, `wireframe` or `no effects`, and `how` says where to change it. `screenshot` with `postEffects: true` draws
 the picture through the same effects and answers `postEffects: "applied"`, or `"unavailable"` with the reason.
 
+### bake_light: baked corner shadows and bounced light
+
+*New in 1.63.* `bake_light` bakes [Baked Light](../baked-light.md) for everything that does not move:
+`{"do": "bake", "quality": "normal"}` (`draft`, `normal`, `high`) runs the bake on this device and waits up to `wait`
+seconds (default 60, max 120) for the result; a longer bake answers "still baking" and `{"do": "status"}` reports
+it later. `status` also says whether the bake is `stale` (things moved since), how many objects got corner shadows
+only (`aoOnly`, overlapping UVs) and the panel's notes, such as which objects were left out and why. `cancel` stops
+a running bake (nothing changes), `clear` removes the bake, and `strength` sets `light` (0-3) and `ao` (0-1).
+A bake, a clear and a strength change ask the host first like `set_post`, and each is one Undo step. Through the
+[Claude connector](claude-connector.md) the same thing is `set_look` with `action: "bake"` and the options under `bake`.
+
+### set_look_preset: a pro look in one call
+
+*New in 1.63.* `set_look_preset {"preset": "product"}` (or `cinematic`, `stylised`) applies a [pro preset](../pro-look.md):
+the sky, light, exposure, tone mapping and post effects together, as one Undo step that everyone in the session sees. It
+asks the host first like `set_post`. Through the [Claude connector](claude-connector.md) it is `set_look` with
+`action: "preset"`.
+
+### take_photo: a path-traced still
+
+*New in 1.63.* `take_photo` renders a [photo](../photo-mode.md) of the person's view (`samples`, `seconds`, `denoise`;
+`save: true` files it under Scene shots) and answers with the image like a screenshot. On a headset or a phone a PC in
+the session renders it. Through the connector it is `run` with `action: "photo"`.
+
 ### set_quality: ask for higher quality on the person's own device
 
 *New in 1.61.* When a phone hides the post effects to stay smooth, an agent does **not** change that on its own. It
 
@@ -193,6 +193,12 @@ Worlds ([Worlds with an agent](agent-world.md)):
 - `set_look` `material` takes `pattern` (wood, brick, marble …). `create_shape` `mesh` takes `subdivide: 1-2`, and
   `edit_shape` `update` sends a mesh new vertices.
 
+**New in 1.63** — no new tool names, more in the families:
+
+- `set_look` `preset` applies a [pro look](../pro-look.md) (`product`, `cinematic`, `stylised`) in one Undo step.
+- `set_look` `bake` bakes [corner shadows and bounced light](../baked-light.md) (`bake: {do, quality, wait, light, ao}`).
+- `run` `photo` renders a path-traced [photo](../photo-mode.md) of your view; a PC in the session renders it for a headset.
+
 **New in 1.61** — no new tool names, more in the families:
 
 - `create_shape` `text` writes [3D text](../3d-text.md), flat or solid with a bevel; `edit_shape` `params` changes its
 
@@ -0,0 +1,96 @@
+# Baked Light
+
+**Baked light** works out soft shadows in corners (ambient occlusion) and light bouncing off
+walls once, for everything in the scene that does not move, and saves the result with the
+scene. A red wall tints the floor beside it, and a crate sits in a soft shadow, without any
+cost while you play. It looks the same on a phone, in a headset, and on the desktop next to
+it.
+
+![The Baked light section in Configure Scene ▸ Scene look](img/baked-light/baked-light-dark.png)
+
+## Baking
+
+1. Arrange the scene first. A bake is a snapshot of where things are now.
+2. Open **Configure Scene ▸ Scene look** and find **Baked light**.
+3. Choose a **Quality** (Draft, Normal or High) and press **Bake light**.
+
+A progress bar shows how far it has got, and **Cancel** stops it at once. Nothing in the
+scene changes until a bake has finished. You can keep working while it runs: the bake
+happens in the background and never freezes the editor.
+
+When it finishes, everyone in the session sees the baked light, it is saved with the scene,
+and **Undo** takes the whole bake off in one step.
+
+Two sliders then tune it without baking again:
+
+- **Bounce light** — how strong the bounced light is (1 = as baked).
+- **Corner shadows** — how dark the ambient occlusion is.
+
+**Remove baked light** takes it off again (also one Undo step).
+
+## What gets baked
+
+Everything that **does not move**:
+
+- Left out: objects with a physics body that moves (dynamic or kinematic), objects moved by
+  a node graph or played by an animation clip, animated characters, instanced objects,
+  hidden objects, and anything spawned while a game runs.
+- Everything that is baked also **casts** onto everything else — a pillar's shadow lands on
+  the floor.
+- The panel lists what was left out and why, for example *"2 objects left out: 1 moves with
+  physics, 1 has an animation."*
+- **Big, detailed scenes** (a whole tavern of carved kit pieces) still fit in one lightmap: very detailed
+  objects are laid out by their own texture coordinates. Where those overlap, the object gets the soft
+  corner shadows but no baked light, and the panel says so. Only when even that is too much are the most
+  detailed small props left out. They still cast shadows onto the rest, and keep their normal lighting.
+
+The light that bounces comes from the scene's own lights (the sun, point and spot lights).
+Those lights and the sky still light the scene live as before, so moving objects and baked
+ones match. A scene with no lights bakes the corner shadows only.
+
+## When things move: "Out of date"
+
+If you move, delete or reshape a baked object, or change the lights, an **Out of date** chip
+appears next to the button. The old bake stays until you press **Bake again** — move things
+back and the chip goes away.
+
+## Lightmap UVs
+
+A bake needs a second set of texture coordinates that do not overlap. The app makes them for
+you: it uses the model's own second UV set when it has a clean one, and otherwise unwraps the
+object itself. Your model is never changed — the bake's coordinates live beside it and are
+rebuilt the same way on every device.
+
+If an object's UVs overlap and cannot be unwrapped cleanly, it gets the **corner shadows
+only**, and the panel says so in one line.
+
+## Devices
+
+| Device | Lightmap | Time limit | Download it shows |
+|---|---|---|---|
+| Desktop | up to 2048 px | 2 minutes | up to 16 MB |
+| Phone | up to 1024 px | 1 minute | up to 2 MB |
+| Headset | 512 px | 45 seconds | up to 1 MB |
+
+A bake made on a desktop also stores a small 512 px copy, which phones and headsets show when
+the full map is too big for them. A bake that hits the time limit keeps what it has and says
+so; **Bake again** on a faster device for a cleaner result.
+
+## Asking an AI to bake
+
+The [Claude connector](ai/claude-connector.md) and the in-app assistant can bake too: ask it to
+*"bake the light"* once the layout is done. It uses **set_look** with the **bake** action
+(`do`: bake, status, cancel, clear or strength), asks the host first like any scene-wide look
+change, and can tell you when the bake is out of date.
+
+## Limits worth knowing
+
+- **Moving objects are not baked.** They are still lit live and still receive the live
+  shadows, but they get no baked corner shadows.
+- **A bake is one bounce.** The light bounces once off the surfaces it hits; the sky is not
+  baked (it stays live).
+- **Objects drawn by a [Shader Graph](shader-graph.md)** and materials that cannot take a
+  lightmap are not baked (they still cast onto others).
+- **A GLTF export does not carry the bake.** Save a **Scene (`.tpscene`)** to keep it. The
+  lightmap is saved in the scene and shows in **Scene ▸ textures**.
+- Scenes saved before this version open exactly as they did.
@@ -144,6 +144,7 @@ The **Environment** section sets the scene's lighting and sky. Pick a preset chi
 | **Sunset** | Warm, low sun. |
 | **Night** | Dim and cool. |
 | **Classic** | The pre-lighting look with the rig **off** — bring your own lights. |
+| **Product shot**, **Cinematic**, **Stylised** | *New in 1.63.* Pro presets: they also set the tone mapping and a stack of post effects. See [Pro Look](pro-look.md). |
 
 ![The same scene under four environment presets: Studio (neutral grey), Daylight (bright sky), Sunset (warm, low sun) and Night (dim and cool).](img/camera/env-presets.webp){ .shot width="1292" height="812" loading=lazy }
 /// caption
 
@@ -463,6 +463,16 @@ only).
 The logo menu fits a short screen — a landscape phone, or a docked Connect bar — and scrolls with a finger, with no
 visible scrollbar. On a folding phone it stays right through folding and unfolding with the page open.
 
+### Phones and tablets (1.63)
+
+- **Android Back closes what is on top**: a menu, a dialog, a window, the bottom panel or the Connect drawer closes with
+  the Back button or gesture, one at a time, before Back leaves the app. Play and shared play links keep their own Back.
+- **The keyboard does not cover the dialog**: a dialog with a text field moves up above the on-screen keyboard, and on a
+  touch screen it does not open the keyboard by itself.
+- **Long menus scroll**: the profile menu and other long menus stay on screen and scroll with a finger.
+- **Tablets**: with the Properties column pinned full height, the toolbar centres in the space beside it.
+- The *lowered the scene look* card waits at the bottom on a touch screen and hides while [Film](film.md) is open.
+
 ### Floating windows
 
 The toolboxes, the Explorer, the flow and animation windows and the panels all behave the same way: drag the header (or, since 1.35, any empty part of the window) to move, drag the bottom-right corner to resize. A window can never be sized past the edge of the screen — the resize corner always stays reachable — and **double-clicking** the corner resets it to its default size while leaving it where you parked it. Size and position are remembered per window.