Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.2.X, 2022.1.X
Votes
2
Found in
2021.2.0a17
2021.2.5f1
2022.1
Issue ID
1387200
Regression
Yes
Multiple 'Assertion failed' errors are logged into the Console when copying properties from Material
Reproduction steps:
1. Open the 'Unity Bug Report 2021.2' project
2. Open the 'SampleScene'
3. Hit Play and observe the Console
Expected result: no errors are displayed in the Console
Actual result: multiple 'Assertion failed on expression: 'material.sharedMaterialData->smallMaterialIndex != 0'' errors are logged into the Console
Reproducible with: 2021.2.0a17, 2021.2.5f1, 2022.1.0b1
Not reproducible with: 2019.4.32f1, 2020.3.24f1, 2021.1.28f1, 2021.2.0a16
Note: commenting the 16th line out '_materialToRender.CopyPropertiesFromMaterial( _material );' in the 'RenderWithMaterial.cs' script will make errors gone
Comments (1)
-
dayflygirl
Dec 15, 2021 09:51
+ Found in 2021.2.6f1
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a3
No errors should happen when using `CopyPropertiesFromMaterial` now.
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b13
Resolution Note (fix version 2021.2):
Fixed in 2021.2.18f1