Update HDR output manual page based on the 4.7 dev cycle#11920
Merged
mhilbrunner merged 1 commit intoApr 11, 2026
Conversation
allenwp
added
enhancement
topic:rendering
area:manual
34 tasks
Contributor
Author
|
Whoops, I forgot to add the note that HDR output is not currently supported on Android. I’ll add that to this PR sometime next week (I’m back in the office on Tuesday). Adding this note won’t affect the rest of this PR, so it’s still ready for review. |
mhilbrunner
approved these changes
Apr 11, 2026
Member
|
Thank you! Merged. |
This was referenced Apr 15, 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
3 participants
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.
What problem(s) does this PR solve?
What is the rationale for the approach used in this PR?
This PR addresses the some of the same points as #11903 (removes trailing whitespace, adds requirement for mobile or forward+ renderer), but intentionally does not add the "On Linux/*BSD, HDR output is not supported on X11 due to display server limitations" comment to these instructions. My opinion is that these initial setup instructions have a lot of text, so adding more explanation to them makes for a more difficult user experience when configuring a project to use HDR output. In short, I take the stance that "less is more" for this list.
This PR also removes the comment about macOS needing the metal driver, as this is no longer the case.
This PR adds instruction relating to new changes to the editor introduced in godotengine/godot#118079 and updates the example GDScript to use the signals added by godotengine/godot#115666 and godotengine/godot#118076
Most importantly, I have reworked the guidance for when to use
Window.get_output_max_linear_value()to address #11913.I have not yet included any comments about how to adjust system reference/max luminance. Of specific importance is how Windows laptops behave, which is bonkers. I'll add this information in a followup PR sometime before 4.7 stable, but it is not necessary for beta 1.
Was AI used to create a portion of this PR?
No.
Are there any parts of this PR that you are uncertain of or require special attention from reviewers?
Much of these changes are required before godotengine/godot-website#1302 goes live.
Depends on: