Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

fix(forge-studio): lift the Avatar and Lab tabs' dim grey text over the AA contrast floor

nirholasab79c88ee6bb
diff --git a/CHANGELOG.md b/CHANGELOG.md
index d722fd7d5..bd2c34760 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -35,7 +35,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Selfie to Avatar tells you your library is full before it spends ninety seconds building**: Five fixes to Selfie to Avatar. If your avatar library was already at the limit for your plan, nothing noticed until the very end: you waited out the full reconstruction, and then the page said the 3D engine had hit a snag and told you to try again. It was not an engine problem, trying again could never work, and every attempt spent another ninety seconds of generation to land in the same place. Your library is now checked the moment you press the button, so a full one is refused immediately with the actual reason and what to do about it, and a build that fills the last slot while it is running ends with that same plain explanation instead of the engine message. The page also stopped losing its own error messages: the Build button floats above the page, so tapping it from higher up left the explanation somewhere below the fold while the button quietly reset itself, which read as nothing having happened. Errors now scroll into view. On the finished-avatar screen, Learn how to embed pointed at a page that did not exist and answered 404; it now opens the embedding guide. And on a narrow phone the Photoreal and Stylized choices were squeezed into two columns barely wide enough for one word per line, so they now stack and can be read. (`/create/selfie`) `[fix, improvement]`
- **Skill tags now actually filter, a failed skills load says so instead of claiming the catalog is empty, and a shared skills link brings its filters with it**: The /skills path was driven end to end in a real browser. It forwards into the Marketplace Skills tab, and it was forwarding a search that the tab then threw away: a link like /skills?q=whale landed on the full unfiltered list with an empty search box. The Skills tab now reads its search, category, tag, and sort straight off the address bar, and writes them back as you change them, so the view you are looking at is the view you can bookmark, share, reload, and step back through. The tag chips on a skill were the clearest casualty of that gap: clicking one navigated to a list that looked exactly the same as before, because nothing was filtering by tag at all. Tags now filter for real in the catalog itself, the tab shows which tag it is filtering by, and one click clears it. When the catalog cannot be reached, the grid used to show the words No skills found with an invitation to publish one, which is the same screen an empty catalog would give you and offers no way to try again: the error state and its Retry button were being overwritten a fraction of a second after they rendered. A failed load now says it could not load skills and hands you the retry. The count under the heading was also being reverted to its placeholder by the translation pass a moment after it was written, so it never showed how many skills you were looking at; it does now, and it names your active category or tag. The empty state names the filters that emptied the list instead of guessing. For anyone arriving without JavaScript, including crawlers, /skills was a completely blank page with no link out of it; it now carries a real heading, an explanation, and a link into the Marketplace. The search box has a proper label, the free and paid chips announce which one is selected, and the page holds up from 320px to 1440px. (`/marketplace?tab=skills`) `[fix, improvement]`
- **Smart Money Radar stops shearing coin cards on a phone, and a lost connection no longer masquerades as a coin nobody is buying**: The /smart-money page was driven end to end in a real browser at 320, 768 and 1440 pixels. On a narrow phone the coin grid insisted on a column wider than the screen, so the right edge of every card was silently cut away by the page: the pedigree score badge and the star that adds a coin to your watchlist were both off-screen, with no sideways scroll to reach them. Cards now fit the screen they are on, and the score and the star are back. The bigger problem was that the page could not tell a coin it had never scored apart from a request that never arrived. If your connection dropped, or the radar was briefly down, every coin on your watchlist was relabelled Not on the radar yet, which reads as a verdict on the coin rather than a problem with the connection, and opening any coin or wallet gave you the same flat Not scored yet with no way to try again. The page now separates the two. A genuine miss keeps its explanation and now says why, and adds a link out to pump.fun or Solscan so the trail does not end there. A connection failure says the radar could not be reached and gives you a Retry button, in the drawer, on the watchlist, and on individual watched coins, and your watchlist is explicitly noted as still saved on your device. A first load that fails outright used to leave the Top wallets tab as an empty void; it now carries the same message and its own retry. A proven wallet whose trades predate the detail the radar keeps used to show a bare No recent coins on record, which looked like a wallet that had stopped trading; it now explains that the coin-level detail has aged out while the win record above still counts every verdict. (`/smart-money`) `[fix, improvement]`
-- **Studio stops going quiet when the engine list fails, and a broken preview no longer leaves a wall of broken images**: The Studio at three.ws/forge-studio was driven end to end in a real browser: both text-to-3D pipelines, all three tabs (Object, Avatar and Lab), a real generation from prompt to finished GLB, and the loading, empty, error and populated states at phone, tablet and desktop widths. The finding that mattered was silent. Studio asks the server which generation engines are live before it draws the Quality and Engine pickers, and if that request failed for any reason, the whole row of controls simply vanished with nothing said. You were left on a page that looked complete but had quietly lost the choice between Draft, Standard and High, and every engine behind it, with no hint that anything had gone wrong or any way to get it back short of a reload. A failed engine list now says so where the pickers used to be, explains that generation still works on the free engine, and offers a Retry that brings the full picker back in place. A server that genuinely has no engines to offer stays quiet as before, because that is not a failure. Second, when a thumbnail in the community showcase could not load, the card started rendering a 3D frame from the model file instead, which is the right answer, but it left the broken image sitting on screen for the whole wait. Those renders are queued one at a time behind a twenty second limit, so a bad network turned the showcase into a grid of broken-image boxes for minutes. The card now falls back to its readable gradient-and-prompt tile the instant the image fails, and the 3D render replaces it when it arrives. The rest is the polish an audit turns up: the Avatar tab carried two competing page headings, so a screen reader heard the page rename itself when you switched tabs; the Lab tab's Download button now tells assistive tech it is disabled and why, instead of just looking dim; the photo and sketch file pickers finally have names; and a freshly generated model now actually previews, where before the viewer, the reveal animation and the game-ready poly counter all failed to read the finished file outside production. (`/forge-studio`) `[fix, improvement]`
+- **Studio stops going quiet when the engine list fails, and a broken preview no longer leaves a wall of broken images**: The Studio at three.ws/forge-studio was driven end to end in a real browser: both text-to-3D pipelines, all three tabs (Object, Avatar and Lab), a real generation from prompt to finished GLB, and the loading, empty, error and populated states at phone, tablet and desktop widths. The finding that mattered was silent. Studio asks the server which generation engines are live before it draws the Quality and Engine pickers, and if that request failed for any reason, the whole row of controls simply vanished with nothing said. You were left on a page that looked complete but had quietly lost the choice between Draft, Standard and High, and every engine behind it, with no hint that anything had gone wrong or any way to get it back short of a reload. A failed engine list now says so where the pickers used to be, explains that generation still works on the free engine, and offers a Retry that brings the full picker back in place. A server that genuinely has no engines to offer stays quiet as before, because that is not a failure. Second, when a thumbnail in the community showcase could not load, the card started rendering a 3D frame from the model file instead, which is the right answer, but it left the broken image sitting on screen for the whole wait. Those renders are queued one at a time behind a twenty second limit, so a bad network turned the showcase into a grid of broken-image boxes for minutes. The card now falls back to its readable gradient-and-prompt tile the instant the image fails, and the 3D render replaces it when it arrives. The rest is the polish an audit turns up: the Avatar tab carried two competing page headings, so a screen reader heard the page rename itself when you switched tabs; the Lab tab's Download button now tells assistive tech it is disabled and why, instead of just looking dim; the photo and sketch file pickers finally have names; seven pieces of small grey text across the Avatar and Lab tabs (the character counter, the elapsed timer, the sign-in hint, the slider read-outs and the footnotes) were too dim to read against the near-black background and now use the same secondary colour as the rest of the page, which clears the accessibility contrast floor on all three tabs; and a freshly generated model now actually previews, where before the viewer, the reveal animation and the game-ready poly counter all failed to read the finished file outside production. (`/forge-studio`) `[fix, improvement]`
- **Tabbing into the Forge prompt box now shows you where you are**: The Forge composer (three.ws/forge and the maximum-quality lane at three.ws/forge-max) draws its describe-it box, its photo-guidance box and its sketch-description box without a border, so the card reads as one clean surface. That styling had also switched off the browser focus outline, which meant anyone moving through the page with the Tab key landed in the main prompt field with no visible sign that they were there: the page looked identical whether the box had keyboard focus or not, on the single most important input on the surface. All three boxes now draw a focus ring when you reach them by keyboard, and only by keyboard, so clicking in with a mouse keeps the seamless look it always had. The rest of the lane was driven end to end in a real browser at phone, tablet and desktop widths: High stays pinned when you open /forge-max, the quality switches move between Draft, Standard and High with the holder gate reflected on the Generate button, and a busy or failing generator lands on a designed message with a retry rather than a blank panel. (`/forge-max`) `[fix, improvement]`
- **Talking Avatar Video stops handing the renderer a 3D file where a photo belongs, and says up front when the GPU lane is down**: The /create/video page turns one of your avatars plus an audio clip into a lip-synced video, and it was driven end to end in a real browser: every state, every button, every width. The worst finding was invisible from the page. The reference frame the GPU worker renders from was being taken from whatever the browser had handy, which for an avatar with no thumbnail meant its 3D model file. The worker saved that as the reference photo and then failed on it minutes later, after the wait had already been spent. The page now sends only the avatar, and the server resolves a real image for it: the stored thumbnail, or a fresh portrait render when there is none. Second, the GPU renderer is a separate service, and when it is not running the only signal was a failure after you had already picked a file and uploaded it. The page now asks first and, if the lane is down, says so at the top, keeps Generate switched off, and points at the Avatar Studio and prompt-to-avatar in the meantime. The rest is the ordinary polish an audit turns up: a failed avatar list used to look identical to owning no avatars, so it sent people off to create one they already had, and now it says what broke and offers a retry; having no avatars yet gets a real empty state with a link to make one; the Generate button always explains what it is still waiting for and, once audio is in, how many clips of video that audio is worth; the clip you picked can be played back with its length and size before you spend a generation on it; a render job that goes unreachable now says so after thirty seconds instead of spinning for twenty minutes; and after a spent free trial the button under the error no longer stayed stuck on Upgrade plan for every later error. Avatar thumbnails are real buttons with visible focus rings, the two form fields have proper labels, and the second animated avatar that the site companion used to drop onto this page no longer loads over the one you are working on. (`/create/video`) `[fix, improvement]`
- **Text to 3D gets its footer back, a retry button that knows when to open, and an honest name for the model that refined your prompt**: The /forge-spark page was driven end to end in a real browser. The closing note under the workspace was written as a page footer, and the site's old corner-credit styling for the 3D viewer pages had quietly claimed it: it was pulled out of the layout into a floating monospace strip that sat on top of the viewer on a desktop, and on a 320px phone it landed across the composer with its link to the full studio pushed off the edge of the screen entirely. That note is now ordinary page text, centered under the workspace where it belongs, and the real three.ws footer, with its full set of links, is on the page for the first time. When a generation fails there is now a Try again button inside the error itself, so recovery does not mean scrolling back to the top; when the generator answers that it is busy, the button counts down and opens exactly when a retry can actually get through. A stage that fails is marked in red instead of silently dropping back to grey, the wait now shows real elapsed seconds so a cold reconstruction lane no longer reads as a hang, and the first step is renamed to whatever model actually answered, because the prompt refiner is a chain of engines and Nemotron is only the first one it tries. (`/forge-spark`) `[fix, improvement]`
diff --git a/data/changelog.json b/data/changelog.json
index 8d392c82c..2d6d022d9 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -14,7 +14,7 @@
{
"date": "2026-08-17",
"title": "Studio stops going quiet when the engine list fails, and a broken preview no longer leaves a wall of broken images",
- "summary": "The Studio at three.ws/forge-studio was driven end to end in a real browser: both text-to-3D pipelines, all three tabs (Object, Avatar and Lab), a real generation from prompt to finished GLB, and the loading, empty, error and populated states at phone, tablet and desktop widths. The finding that mattered was silent. Studio asks the server which generation engines are live before it draws the Quality and Engine pickers, and if that request failed for any reason, the whole row of controls simply vanished with nothing said. You were left on a page that looked complete but had quietly lost the choice between Draft, Standard and High, and every engine behind it, with no hint that anything had gone wrong or any way to get it back short of a reload. A failed engine list now says so where the pickers used to be, explains that generation still works on the free engine, and offers a Retry that brings the full picker back in place. A server that genuinely has no engines to offer stays quiet as before, because that is not a failure. Second, when a thumbnail in the community showcase could not load, the card started rendering a 3D frame from the model file instead, which is the right answer, but it left the broken image sitting on screen for the whole wait. Those renders are queued one at a time behind a twenty second limit, so a bad network turned the showcase into a grid of broken-image boxes for minutes. The card now falls back to its readable gradient-and-prompt tile the instant the image fails, and the 3D render replaces it when it arrives. The rest is the polish an audit turns up: the Avatar tab carried two competing page headings, so a screen reader heard the page rename itself when you switched tabs; the Lab tab's Download button now tells assistive tech it is disabled and why, instead of just looking dim; the photo and sketch file pickers finally have names; and a freshly generated model now actually previews, where before the viewer, the reveal animation and the game-ready poly counter all failed to read the finished file outside production.",
+ "summary": "The Studio at three.ws/forge-studio was driven end to end in a real browser: both text-to-3D pipelines, all three tabs (Object, Avatar and Lab), a real generation from prompt to finished GLB, and the loading, empty, error and populated states at phone, tablet and desktop widths. The finding that mattered was silent. Studio asks the server which generation engines are live before it draws the Quality and Engine pickers, and if that request failed for any reason, the whole row of controls simply vanished with nothing said. You were left on a page that looked complete but had quietly lost the choice between Draft, Standard and High, and every engine behind it, with no hint that anything had gone wrong or any way to get it back short of a reload. A failed engine list now says so where the pickers used to be, explains that generation still works on the free engine, and offers a Retry that brings the full picker back in place. A server that genuinely has no engines to offer stays quiet as before, because that is not a failure. Second, when a thumbnail in the community showcase could not load, the card started rendering a 3D frame from the model file instead, which is the right answer, but it left the broken image sitting on screen for the whole wait. Those renders are queued one at a time behind a twenty second limit, so a bad network turned the showcase into a grid of broken-image boxes for minutes. The card now falls back to its readable gradient-and-prompt tile the instant the image fails, and the 3D render replaces it when it arrives. The rest is the polish an audit turns up: the Avatar tab carried two competing page headings, so a screen reader heard the page rename itself when you switched tabs; the Lab tab's Download button now tells assistive tech it is disabled and why, instead of just looking dim; the photo and sketch file pickers finally have names; seven pieces of small grey text across the Avatar and Lab tabs (the character counter, the elapsed timer, the sign-in hint, the slider read-outs and the footnotes) were too dim to read against the near-black background and now use the same secondary colour as the rest of the page, which clears the accessibility contrast floor on all three tabs; and a freshly generated model now actually previews, where before the viewer, the reveal animation and the game-ready poly counter all failed to read the finished file outside production.",
"tags": [
"fix",
"improvement"
diff --git a/pages/forge-studio.html b/pages/forge-studio.html
index be9dd1f55..d80701fb2 100644
--- a/pages/forge-studio.html
+++ b/pages/forge-studio.html
@@ -2903,7 +2903,7 @@
padding: 14px 14px 6px;
outline: none;
}
- #studio-avatar #cp-prompt::placeholder { color: #555; }
+ #studio-avatar #cp-prompt::placeholder { color: var(--muted); }
#studio-avatar .composer-foot {
display: flex;
align-items: center;
@@ -2911,7 +2911,7 @@
gap: 12px;
padding: 0 10px;
}
- #studio-avatar .counter { color: #555; font-size: 12px; font-variant-numeric: tabular-nums; }
+ #studio-avatar .counter { color: var(--muted); font-size: 12px; font-variant-numeric: tabular-nums; }
#studio-avatar .counter.warn { color: var(--danger); }
#studio-avatar .examples { display: flex; flex-wrap: wrap; gap: 8px; margin: 16px 0 4px; }
#studio-avatar .example {
@@ -2946,11 +2946,11 @@
#studio-avatar .btn-primary:active { transform: translateY(1px); }
#studio-avatar .btn-primary:disabled { opacity: 0.4; cursor: not-allowed; }
#studio-avatar .btn-primary:focus-visible { outline: 2px solid #fff; outline-offset: 3px; }
- #studio-avatar .hint { color: #666; font-size: 12.5px; }
- #studio-avatar .hint .chip-auth { color: var(--muted); }
+ #studio-avatar .hint { color: var(--muted); font-size: 12.5px; }
+ #studio-avatar .hint .chip-auth { color: var(--text); }
#studio-avatar .note {
margin-top: 28px;
- color: #666;
+ color: var(--muted);
font-size: 12.5px;
border-top: 1px solid var(--border);
padding-top: 16px;
@@ -3013,7 +3013,7 @@
background: var(--accent);
transition: width 0.8s cubic-bezier(0.4, 0, 0.2, 1);
}
- #studio-avatar .elapsed { color: #555; font-size: 12px; margin-top: 14px; font-variant-numeric: tabular-nums; }
+ #studio-avatar .elapsed { color: var(--muted); font-size: 12px; margin-top: 14px; font-variant-numeric: tabular-nums; }
#studio-avatar .done-wrap { align-items: center; text-align: center; padding-top: 8px; }
#studio-avatar .done-viewer {
width: 100%;
@@ -3131,7 +3131,7 @@
gap: 8px;
align-items: baseline;
}
- #studio-lab .lab-field-out { font-size: 11.5px; color: #666; font-variant-numeric: tabular-nums; }
+ #studio-lab .lab-field-out { font-size: 11.5px; color: var(--muted); font-variant-numeric: tabular-nums; }
#studio-lab .lab-field input[type='range'] { width: 100%; accent-color: var(--accent); }
#studio-lab .lab-field input[type='color'] {
width: 100%;
@@ -3221,7 +3221,7 @@
#studio-lab .lab-status { font-size: 13px; color: var(--muted); }
#studio-lab .lab-status[data-kind='ok'] { color: #6ee7a8; }
#studio-lab .lab-status[data-kind='err'] { color: #f3b4b4; }
- #studio-lab .lab-foot { font-size: 12px; color: #666; margin: 0; max-width: 70ch; }
+ #studio-lab .lab-foot { font-size: 12px; color: var(--muted); margin: 0; max-width: 70ch; }
#studio-lab .lab-foot a { color: #aaa; text-decoration: underline; text-underline-offset: 2px; }
#studio-lab .lab-foot a:hover { color: var(--text); }
@media (max-width: 760px) {
diff --git a/public/changelog.json b/public/changelog.json
index b2a079177..a9886afda 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T07:52:30.838Z",
+ "generated_at": "2026-08-17T08:02:08.331Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -328,7 +328,7 @@
"date": "2026-08-17",
"type": "update",
"title": "Studio stops going quiet when the engine list fails, and a broken preview no longer leaves a wall of broken images",
- "summary": "The Studio at three.ws/forge-studio was driven end to end in a real browser: both text-to-3D pipelines, all three tabs (Object, Avatar and Lab), a real generation from prompt to finished GLB, and the loading, empty, error and populated states at phone, tablet and desktop widths. The finding that mattered was silent. Studio asks the server which generation engines are live before it draws the Quality and Engine pickers, and if that request failed for any reason, the whole row of controls simply vanished with nothing said. You were left on a page that looked complete but had quietly lost the choice between Draft, Standard and High, and every engine behind it, with no hint that anything had gone wrong or any way to get it back short of a reload. A failed engine list now says so where the pickers used to be, explains that generation still works on the free engine, and offers a Retry that brings the full picker back in place. A server that genuinely has no engines to offer stays quiet as before, because that is not a failure. Second, when a thumbnail in the community showcase could not load, the card started rendering a 3D frame from the model file instead, which is the right answer, but it left the broken image sitting on screen for the whole wait. Those renders are queued one at a time behind a twenty second limit, so a bad network turned the showcase into a grid of broken-image boxes for minutes. The card now falls back to its readable gradient-and-prompt tile the instant the image fails, and the 3D render replaces it when it arrives. The rest is the polish an audit turns up: the Avatar tab carried two competing page headings, so a screen reader heard the page rename itself when you switched tabs; the Lab tab's Download button now tells assistive tech it is disabled and why, instead of just looking dim; the photo and sketch file pickers finally have names; and a freshly generated model now actually previews, where before the viewer, the reveal animation and the game-ready poly counter all failed to read the finished file outside production.",
+ "summary": "The Studio at three.ws/forge-studio was driven end to end in a real browser: both text-to-3D pipelines, all three tabs (Object, Avatar and Lab), a real generation from prompt to finished GLB, and the loading, empty, error and populated states at phone, tablet and desktop widths. The finding that mattered was silent. Studio asks the server which generation engines are live before it draws the Quality and Engine pickers, and if that request failed for any reason, the whole row of controls simply vanished with nothing said. You were left on a page that looked complete but had quietly lost the choice between Draft, Standard and High, and every engine behind it, with no hint that anything had gone wrong or any way to get it back short of a reload. A failed engine list now says so where the pickers used to be, explains that generation still works on the free engine, and offers a Retry that brings the full picker back in place. A server that genuinely has no engines to offer stays quiet as before, because that is not a failure. Second, when a thumbnail in the community showcase could not load, the card started rendering a 3D frame from the model file instead, which is the right answer, but it left the broken image sitting on screen for the whole wait. Those renders are queued one at a time behind a twenty second limit, so a bad network turned the showcase into a grid of broken-image boxes for minutes. The card now falls back to its readable gradient-and-prompt tile the instant the image fails, and the 3D render replaces it when it arrives. The rest is the polish an audit turns up: the Avatar tab carried two competing page headings, so a screen reader heard the page rename itself when you switched tabs; the Lab tab's Download button now tells assistive tech it is disabled and why, instead of just looking dim; the photo and sketch file pickers finally have names; seven pieces of small grey text across the Avatar and Lab tabs (the character counter, the elapsed timer, the sign-in hint, the slider read-outs and the footnotes) were too dim to read against the near-black background and now use the same secondary colour as the rest of the page, which clears the accessibility contrast floor on all three tabs; and a freshly generated model now actually previews, where before the viewer, the reveal animation and the game-ready poly counter all failed to read the finished file outside production.",
"link": "/forge-studio",
"tags": [
"fix",
diff --git a/public/changelog.xml b/public/changelog.xml
index 212205fb7..7d8ebf6e8 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -244,7 +244,7 @@
<guid isPermaLink="false">2026-08-17:Studio stops going quiet when the engine list fails, and a broken preview no longer leaves a wall of broken images</guid>
<pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
<category>fix</category>
- <description>The Studio at three.ws/forge-studio was driven end to end in a real browser: both text-to-3D pipelines, all three tabs (Object, Avatar and Lab), a real generation from prompt to finished GLB, and the loading, empty, error and populated states at phone, tablet and desktop widths. The finding that mattered was silent. Studio asks the server which generation engines are live before it draws the Quality and Engine pickers, and if that request failed for any reason, the whole row of controls simply vanished with nothing said. You were left on a page that looked complete but had quietly lost the choice between Draft, Standard and High, and every engine behind it, with no hint that anything had gone wrong or any way to get it back short of a reload. A failed engine list now says so where the pickers used to be, explains that generation still works on the free engine, and offers a Retry that brings the full picker back in place. A server that genuinely has no engines to offer stays quiet as before, because that is not a failure. Second, when a thumbnail in the community showcase could not load, the card started rendering a 3D frame from the model file instead, which is the right answer, but it left the broken image sitting on screen for the whole wait. Those renders are queued one at a time behind a twenty second limit, so a bad network turned the showcase into a grid of broken-image boxes for minutes. The card now falls back to its readable gradient-and-prompt tile the instant the image fails, and the 3D render replaces it when it arrives. The rest is the polish an audit turns up: the Avatar tab carried two competing page headings, so a screen reader heard the page rename itself when you switched tabs; the Lab tab's Download button now tells assistive tech it is disabled and why, instead of just looking dim; the photo and sketch file pickers finally have names; and a freshly generated model now actually previews, where before the viewer, the reveal animation and the game-ready poly counter all failed to read the finished file outside production.</description>
+ <description>The Studio at three.ws/forge-studio was driven end to end in a real browser: both text-to-3D pipelines, all three tabs (Object, Avatar and Lab), a real generation from prompt to finished GLB, and the loading, empty, error and populated states at phone, tablet and desktop widths. The finding that mattered was silent. Studio asks the server which generation engines are live before it draws the Quality and Engine pickers, and if that request failed for any reason, the whole row of controls simply vanished with nothing said. You were left on a page that looked complete but had quietly lost the choice between Draft, Standard and High, and every engine behind it, with no hint that anything had gone wrong or any way to get it back short of a reload. A failed engine list now says so where the pickers used to be, explains that generation still works on the free engine, and offers a Retry that brings the full picker back in place. A server that genuinely has no engines to offer stays quiet as before, because that is not a failure. Second, when a thumbnail in the community showcase could not load, the card started rendering a 3D frame from the model file instead, which is the right answer, but it left the broken image sitting on screen for the whole wait. Those renders are queued one at a time behind a twenty second limit, so a bad network turned the showcase into a grid of broken-image boxes for minutes. The card now falls back to its readable gradient-and-prompt tile the instant the image fails, and the 3D render replaces it when it arrives. The rest is the polish an audit turns up: the Avatar tab carried two competing page headings, so a screen reader heard the page rename itself when you switched tabs; the Lab tab's Download button now tells assistive tech it is disabled and why, instead of just looking dim; the photo and sketch file pickers finally have names; seven pieces of small grey text across the Avatar and Lab tabs (the character counter, the elapsed timer, the sign-in hint, the slider read-outs and the footnotes) were too dim to read against the near-black background and now use the same secondary colour as the rest of the page, which clears the accessibility contrast floor on all three tabs; and a freshly generated model now actually previews, where before the viewer, the reveal animation and the game-ready poly counter all failed to read the finished file outside production.</description>
</item>
<item>
<title>Tabbing into the Forge prompt box now shows you where you are</title>