Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
6000.0.0b11
Issue ID
UUM-52205
Regression
No
ShaderGUI.ValidateMaterial is called inconsistently
Reproduction steps:
1. Open the attached "repro_IN-55375.zip" project
2. Open the "Test" Scene
3. Build the project ("File > Build And Run")
4. Once the build completes, observe a red sphere in the Player - this means that "ValidateMaterial" was not called during the build process
5. Exit the Player
6. Open either the Scene or the Game view and notice (in the Console) that "ValidateMaterial" is called
7. Build the project
8. Notice that, while the project is building, "ValidateMaterial" is called again
9. Once the build completes, observe a green sphere in the Player
Expected result: "ValidateMaterial" is always called for every Material before being written to a build
Actual result: "ValidateMaterial" is only called if Material is visible at the time of a build
Reproduced with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproduced on: Windows 10 (22H2)
Not reproduced on: No other environments tested
Notes:
* Reproducible in the Player
* If you invert the changes done to the "MaleBody_Test" material, open the "Instantiated" Scene, and enter the Play Mode, the "ValidateMaterial" is not called and the red sphere is shown
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
- [HDRP] Assertion printed when Maximum Reflection Probe count is higher than 64 due to k_MaxCubeReflectionsOnScreen when Raytracing is enabled
- Seams are visible on the Water System when multiple tiles are used and their Surface type is set to River
- Matching Game View creates unsaved changes even though nothing to save
- AudioClips do not have path or GUID in Build Report and incorrect size is reported
- The rendered color of the preset differs from the preview color when adding a new swatch in the HDR Color Picker
Resolution Note:
After much internal deliberation and investigation, we have decided not to fix this issue, since the fix would break a lot of existing projects.
As a compromise, a custom fix has been provided to the customer. We will properly address this issue in future versions of the engine.