Search Issue Tracker
By Design
Votes
0
Found in [Package]
3.0.3
Issue ID
1309290
Regression
No
TextMeshPro Material Properties set at runtime are ineffective in Build
Reproduction steps:
1. Download and open the attached project 'TextMeshProMaterial.zip'
2. Open Scene 'SampleScene'
3. Build and Run the Game
4. Observe the Game
Expected result: Material Properties are changed
Actual result: Material Properties aren't changed
Reproducible with: 1.5.3 (2018.4.30f1), 2.1.3 (2019.4.19f1), 3.0.3 (2020.2.3f1, 2021.1.0b4, 2021.2.0a3)
Notes: The issue is not reproducible in Editor's Play Mode. The issue was reproducible both in macOS and Windows Builds.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Although this is by design as a result of the shaders using #pragma shader_feature, I will revise the shaders in the future to use #pragma multi_compile_local which will result in the shader variants being included by default instead of requiring the user to include them manually which is often overlooked.