Repository navigation
docs(3D): rendering quality, 1.18.27 release notes, and a Demo mode correction - #124
Merged
Merged
Conversation
…f a slow client A Steam user hit 0 FPS on a laptop and concluded there was no video optimization, because the page never said rendering quality could go down or how low it goes (bus #2618, PBI 3220). Preferences page: - The six levels, most to least expensive, and Medium on a fresh install. Nothing is detected from your hardware (the page said the engine picks). - What to do when slow: go straight to Minimum, then Blocks per frame, then filters; the frame-rate prompt and its real thresholds; the only two places the level changes, and contact support when neither is reachable. - Minimum requirements, linked to Supported Configurations. - Reset To Defaults lands on Minimum, not the fresh-install level, resets Demo mode, and cannot be undone; deleting preferences.json does not lower rendering quality. - Window mode and vertical sync defaults stated: Borderless, Every frame. Supported Configurations: the troubleshooting step pointed at the pre-rewrite path (Preferences > General > Rendering Quality). All facts verified against client release 1.18.28. Passed the C2 docs gate at 0.930, no Critical or Major findings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…dacts Release notes: the page stopped at 1.18.8. 1.18.27 is the build live on Steam and the stable installer, so this entry rolls up everything user facing from 1.18.9 to 1.18.27: rebuilt Preferences, Tessa reading and changing them, the frame-rate prompt, demo screens, Shoebox checks, two falling-through-the-ground fixes, and a security update. Nothing from 1.18.28, which is not released. Demo mode: the page told users to turn it on before screen-sharing because it "redacts hosts, URLs and database names everywhere they appear". In 1.18.27 the span and log sanitizer has no callers; the only live use hides the grid name. The tip is now a warning not to rely on it, and the same known issue is in the release notes. Both passed the C2 docs gate (release notes 0.926, Preferences 0.920), no Critical findings. Facts verified against client tag 1.18.27. Co-Authored-By: Claude Opus 5.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.
A Steam user hit 0 FPS on a laptop and concluded there was "no video optimization", because the Preferences page never said rendering quality could go down or how low it goes. Reported by Trout on bus #2618 (PBI 3220).
What changes
Preferences (
DC/3D/Guides/Preferences):preferences.jsondoes not lower rendering quality.Supported Configurations: the troubleshooting step pointed at the pre-rewrite path, Preferences > General > Rendering Quality.
Verification
IF.APM.App.Unity.HDRP), and is unchanged in the upcoming 1.18.28. Files checked:QualitySettings.asset,PreferencesConfigurationDescriptors.cs,EngineSettingsPlan.cs,QualityDegradedDialogModalControl.cs,Avatar.inputactionsandPreferencesModalDialog.prefab. The diff of those files from 1.18.27 to 1.18.28 and to HEAD is empty.mkdocs build --strict,check-meta-descriptionsandcheck-redirect-paritypass locally. All new links resolve.Where this differs from the original report
The report described the pre-rewrite panel, from 1.18.8 and earlier. In 1.18.27:
Also in this PR (second commit)
1.18.27 release notes. The 3D release notes stopped at 1.18.8. 1.18.27 is the build live on Steam and the stable installer, and 1.18.28 is not released. The new entry covers everything user-facing from 1.18.9 to 1.18.27. It was drafted from the 46 merged PRs in that range, with each bullet traced to a PR or commit. It passed the C2 gate at 0.926.
Demo mode: this corrects a false safety claim on the live page. The page told users to turn Demo mode on before screen-sharing, because it "redacts hosts, URLs and database names everywhere they appear". In 1.18.27:
SanitizerControl.Sanitize(Span|Log)has no callers.SanitizeGridon the grid-name label (DiagnosticsLabelControl.cs:100).The tip is now a warning not to rely on Demo mode, and the release notes carry the same known issue. The Preferences page re-passed at 0.920.
🤖 Generated with Claude Code