-
Notifications
You must be signed in to change notification settings - Fork 35
Add "Flexibility of implementation" section #248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
AdrienHerubel
merged 7 commits into
AcademySoftwareFoundation:dev_1.1.1
from
virtualzavie:real-time
Jun 10, 2025
+24
−6
Merged
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
65418e2
Add page to propose real-time approximations
virtualzavie a26ca21
Mention layering and mixing approximation
virtualzavie d13d2c9
Mantion specular reflection approximation
virtualzavie 54631b0
Mention anisotropic reflection approximations
virtualzavie c621842
Fix typos
virtualzavie a3e56a1
Wording
virtualzavie f40b79a
Reword the section, move it to the main document, remove the annex
virtualzavie File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,55 @@ | ||
| <meta charset="utf-8" emacsmode="-*- markdown -*-"> | ||
| <link rel="stylesheet" href="style/style.css"> | ||
| <meta name="viewport" content="width=device-width,initial-scale=1"> | ||
|
|
||
|
|
||
| Approximations for constrained implementations | ||
| ============================================== | ||
|
|
||
| This specification describes a model which includes a number of features that can be computationally expensive and therefore impractical to support in certain contexts, like real-time applications or mobile devices. | ||
|
|
||
| The Historical background and objectives section explains how the goal of this specification is to provide an ideal, reference appearance. The implementer is, however, free to make decisions and approximations to satisfy their practical constraints. We do not dictate what those approximations should be, as this depends on the use case. We can, however, propose some possible ones and offer guidelines to help the implementer make those decisions. | ||
|
|
||
| As a general rule of thumb, we invite the implementer to think of those approximations in the same way one would think of different levels of detail (LOD) variants of an asset. Just like such an asset would become coarser with distance while retaining as much detail as necessary to remain faithful to the original, an implementation of OpenPBR may decide to make simplifications, as long as the result remains reasonably faithful to the intent given the practical constraints. In the most extreme hypothetical case, the model might even get reduced to as little as a single Lambert BRDF. | ||
|
|
||
| This means the implementer must carefully consider what to do with parameters they do not plan to fully support. A parameter that drastically modifies the appearance of a material should not be discarded just because the corresponding effect is not supported. As an example, in a renderer that doesn't have subsurface scattering, the subsurface color might be used as the albedo of a diffuse BRDF. | ||
|
|
||
| In the following sections we propose possible approximations for the different components of the OpenPBR Surface material. | ||
|
|
||
|
|
||
| Layering and mixing | ||
| ------------------------------------- | ||
|
|
||
| As mentioned in the Reduction to a mixture of lobes section, the mix and layer operations can be approximated as a weighted sum of BSDF lobes. | ||
|
|
||
|
|
||
| Specular lobes | ||
| ------------------------------------- | ||
|
|
||
| The specular BRDF described in the specification is the classic GGX-Smith model, which has been common in both offline and real-time rendering for a decade. The so called "split-sum" approximation introduced by [#Karis2013] allows efficient rendering of the isotropic version of this BRDF with image-based lighting. | ||
|
|
||
|
|
||
| ### Anisotropic case | ||
|
|
||
| Several solutions are possible for the anisotropic case: | ||
|
|
||
| - [#Cocco2024] recently proposed an image-based lighting approximation of anisotropic specular reflection consisting in several samples along the main BRDF axis. | ||
|
|
||
| - [#McAuley15] describes a simpler and cheaper method based on [#Revie2011], consisting in modifying normals and offering a very crude approximation of anisotropic reflection. | ||
|
|
||
| - Finally, the crudest approximation would be to ignore entirely the `specular_roughness_anisotropy` for the base layer specular lobe (respectively `coat_roughness_anisotropy` for the coat specular lobe), as the anisotropy parametrization in designed to preserve the average roughness regardless of the anisotropy (see the Microfacet model section for details). | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. since the |
||
|
|
||
|
|
||
| <!-- Markdeep: --> | ||
| <style class="fallback"> | ||
| body { visibility:hidden } | ||
| </style> | ||
|
|
||
| <script src="style/markdeep-1.04.min.js" charset="utf-8"> | ||
| window.markdeepOptions = {tocStyle: "long", smartQuotes=true} | ||
| </script> | ||
|
|
||
| <script> | ||
| window.alreadyProcessedMarkdeep || (document.body.style.visibility="visible") | ||
| </script> | ||
|
|
||
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
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.
Uh oh!
There was an error while loading. Please reload this page.