Typo in legacyTransluceny

kzhsw · June 24, 2025, 8:47am

In breaking changes docs, there is a mat.subSurface.legacyTranslucency

content/breaking-changes.md?plain=1

993d6fd66


      
          

          ### Fix target camera orientation issues when using right-handed scenes

          

          When using right-handed scenes, setting and getting the `rotation` or `rotationQuaternion` properties of a target camera was 180-rotated on the Y-axis when compared to the view or world matrix of the camera. This is confusing and caused problems when exporting glTF. Any code that previously set the `rotation` or `rotationQuaternion` properties of a camera derived from `TargetCamera` (`FreeCamera` or `ArcRotateCamera` for example) when using right-handed scenes will now be wrong. The default orientation of a target camera still faces +Z as before to maintain backwards compatibility. Left-handed scenes are also unaffected. See [PR](https://github.com/BabylonJS/Babylon.js/pull/16691) for more information.

          

          ## 8.2.0

          

          ### PBR: Add flag to calculate legacy translucency

          

          In previous PRs (https://github.com/BabylonJS/Babylon.js/pull/16337, https://github.com/BabylonJS/Babylon.js/pull/16214), we corrected the way translucency/transmission is calculated.

          However, we failed to add a flag to allow you to render your scene exactly as it was before these changes. We have therefore added a property `mat.subSurface.legacyTranslucency` (default: false), in case your scene does not render as expected with the new code and you want an easy way to do it. You can also set `PBRSubSurfaceConfiguration.DEFAULT_LEGACY_TRANSLUCENCY` to true to automatically apply the back compat behavior to all materials.

          

          PR: https://github.com/BabylonJS/Babylon.js/pull/16446

          

          ## 7.54.0

          

          ### PBR: Fix calculation of diffuse transmission in PBR materials

          

          This is a bug fix, but it may have an impact on the rendering of your scene. Previously, we incorrectly applied the albedo color when outputting the subsurface block calculation.

          However, if you need to restore the old behavior for some reason, you can do `mat.subSurface.applyAlbedoAfterSubSurface = true`. Note that from 8.0.2 and forward you can also set `PBRSubSurfaceConfiguration.DEFAULT_APPLY_ALBEDO_AFTERSUBSURFACE` to true to automatically apply the back compat behavior to all materials.

          Note that you can probably make your assets compatible with the new code without needing to set `applyAlbedoAfterSubSurface = true` by setting the correct texture in the `translucencyColorTexture` property.

But in code of PBRSubSurfaceConfiguration, it is legacyTransluceny.

github.com/BabylonJS/Babylon.js

packages/dev/core/src/Materials/PBR/pbrSubSurfaceConfiguration.ts

13cbef67c


      
           * Note however that the PBR calculation is wrong when this property is set to true, so only use it if you want to mimic the 7.0 behavior.

           */

          @serialize()

          public applyAlbedoAfterSubSurface = PBRSubSurfaceConfiguration.DEFAULT_APPLY_ALBEDO_AFTERSUBSURFACE;

          

          /**

           * This property only exists for backward compatibility reasons.

           * Set it to true if your rendering in 8.0+ is different from that in 7 when you use sub-surface transluceny. Default is false.

           */

          @serialize()

          public legacyTransluceny = PBRSubSurfaceConfiguration.DEFAULT_LEGACY_TRANSLUCENCY;

          

          private _scene: Scene;

          

          /** @internal */

          private _internalMarkAllSubMeshesAsTexturesDirty: () => void;

          private _internalMarkScenePrePassDirty: () => void;

          

          /** @internal */

          public _markAllSubMeshesAsTexturesDirty(): void {

              this._enable(this._isRefractionEnabled || this._isTranslucencyEnabled || this._isScatteringEnabled);

Deltakosh · June 24, 2025, 1:57pm

Cc @sebavan

sebavan · June 24, 2025, 3:26pm

… totally my fault !!!

sebavan · June 24, 2025, 3:31pm

Topic		Replies	Views
Breaking change in target camera rotations when using right-handed system Breaking Changes	7	176	June 13, 2025
NME PBRMetallicRoughnessBlock reflections are incorrect with right handed coordinate system Bugs	6	394	March 27, 2022
Face ordering problems when replacing material on GLTF-imported mesh Questions	8	1205	March 12, 2019
GltfExport - flipped camera Bugs exporter , camera , gltf2export	27	716	June 5, 2025
New Update for Babylon's glTF Exporter 🚀 Announcements	8	136	December 7, 2024

Typo in legacyTransluceny

Related topics