Repository navigation
Steam release notes for 1.18.20 - #123
Merged
Merged
Conversation
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 <noreply@anthropic.com>
ETWOYA
approved these changes
Oct 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Founder direction via Friday: the Steam 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 worth stating precisely
1.18.8 already claimed "Fixed teleport arrival dropping you through the floor." It had not.
The remaining cause isn't teleporting at all. The idle pruner removes a facility whose service has been quiet for five minutes, and
RemoveFacilityunparented the avatar from it and then destroyed the floor it was standing on — the rescue was written, the landing was not. It only happens when you stop moving, which is why six earlier waves never reproduced it: every test session is someone actively moving.The note says that plainly rather than repeating the earlier claim.
One claim I did not publish
The direction listed "roughly double frame rate on mid-range GPUs". I could not source it:
m_APIs 02000000 → 12000000) with no measurement in itSo the note says Windows renders with Direct3D 12, and that heavy grids cost less per frame. Both true, both sourced. Neither carries a number.
A performance figure in a public release note is exactly the kind of claim a reader measures. Where does the doubling figure come from? If it's your own testing I'll add it with the hardware named.
Also noted, not acted on
Tags run to 1.18.27. If 1.18.21–27 reached Steam they need pages too; if they're internal builds they don't. The existing notes cover some tags and not others, so it isn't derivable from the repo.
🤖 Generated with Claude Code