From 084d9a2f692e5842d2d24efb984bcee08f10bb50 Mon Sep 17 00:00:00 2001 From: Dan Kowalski Date: Sat, 3 Oct 2026 12:43:32 -0400 Subject: [PATCH] docs(steam): release notes for 1.18.20 Founder direction via Friday (bus #3478): the notes stop at 1.18.8 and 1.18.20 has no page. Written from the 35 merges between the two tags, read for what they changed rather than from their titles, as asked. The headline fix is the post-teleport fall, and it is worth stating precisely because 1.18.8 already claimed to have fixed it. It had not. The remaining cause is not teleporting at all: the idle pruner removes a facility whose service has been quiet for five minutes, and RemoveFacility unparented the avatar from it and then destroyed the floor it was standing on. It only happens when you stop moving, which is why six waves of fixes never reproduced it -- every test session is someone actively moving. ONE CLAIM I DID NOT PUBLISH. The direction listed "roughly double frame rate on mid-range GPUs". I could not source it. The D3D12 merge is a one-line graphics API switch with no measurement in it, and the SP-064 profiler capture is an Editor baseline that says so itself ("absolute fps here is not the product's fps") and concludes the scene is CPU-bound rather than GPU-bound. There is no before/after pair and no mid-range GPU benchmark anywhere in the repo. So the note says Windows renders with Direct3D 12, and that heavy grids cost less per frame, both of which are true and sourced. It does not put a number on either. A performance figure in a public release note is the kind of claim a reader measures, and one we cannot show is the kind this quarter has been spent removing. Asking the founder for the source rather than dropping the item. Also noted and not acted on: tags run to 1.18.27. If 1.18.21 through 1.18.27 reached Steam they need pages too; if they are internal builds they do not. The existing notes cover some tags and not others, so this is not derivable. Co-Authored-By: Claude Opus 5 --- docs/DC/3D/steam/1-18-20.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 docs/DC/3D/steam/1-18-20.md diff --git a/docs/DC/3D/steam/1-18-20.md b/docs/DC/3D/steam/1-18-20.md new file mode 100644 index 0000000..4d117a4 --- /dev/null +++ b/docs/DC/3D/steam/1-18-20.md @@ -0,0 +1,26 @@ +# DeepCube™ 1.18.20 + +Everything since 1.18.8. The post-teleport fall is fixed at its real cause, which turned out not to be teleporting at all. Preferences become a real screen that Tessa can read and change. A machine that cannot keep up now says so and offers one click out of it, and the heaviest grids do considerably less work per frame. + +## What's New +- Preferences, properly: a settings screen built from the settings themselves, so what the app can do and what the screen offers cannot drift apart. Grid visibility, block behaviour, phantom detection, rendering, chat size, skybox and more. +- Tessa can read and change your preferences. Ask her to keep errored blocks, show the log blocks or make the chat bigger and she does it. A short list stays hers to read but not to change: redaction, sign-in and the frame budget. +- Your rendering choices survive a restart. Quality, window mode, vertical sync and render resolution are remembered rather than re-picked by the engine each run. +- When the frame rate gives out, the app says so and offers one click down. It waits long enough to be sure it is the machine rather than a passing hitch, then offers a single quality level drop, a dismiss, or don't ask again. +- Windows renders with Direct3D 12. +- Heavy grids cost less per frame. Portals now exist only near their own facility instead of all at once, which on a large grid retires well over a hundred idle portals and everything each one kept alive. +- Shoebox tells you when a run did not match the diagram you sent. The trace looks complete either way, so if the sandbox had to change your diagram to run it, she now says so unprompted instead of letting you read the wrong picture. +- Loading a Shoebox diagram is free: she can fire the one already in the conversation without you sending it again, and several times with a delay between them if you want to watch an intermittent failure happen exactly once. +- Tessa can see the images you send her. An image with no caption used to be discarded before the request was built, and she would report that you had never sent one. +- Ask Tessa to clear the service map and she clears it. +- A backend that is still starting now says so, once, in the app's own voice rather than as something Tessa said. If it never wakes, you are told that rather than left with a silence. + +## Fixes +- Fixed the fall through the floor that six earlier waves of teleport fixes never caught, because it is not a teleport bug. Stand on a facility whose service goes quiet for five minutes and the idle pruner removed it from under you: the avatar was rescued from being destroyed with it, and then left suspended over nothing. The floor is no longer deleted out from under whoever is standing on it. +- Fixed the platform you are leaving from continuing to carry you after you step off it. +- Fixed edges lingering on the graph after the thing they connected had gone. +- Fixed the chat browser dying silently. If it goes, you are told. + +## Known Issues +- The chat handles one conversation at a time. The transcript survives reopening the window, but is not saved between sessions. +- macOS support is experimental and may lack full feature parity with Windows.