Search Issue Tracker
Fixed
Fixed in 2022.3.7f1, 2023.1.6f1, 2023.2.0b2, 2023.3.0a1
Votes
0
Found in
2022.2.10f1
2023.1.0b6
2023.2.0a5
2023.3.0a1
Issue ID
UUM-29499
Regression
Yes
"Type mismatch" is assigned to the Mesh Filter Component instead of the Mesh when there is a "Mesh" Script in the project
How to reproduce:
1. Open the user-attached project “T2”
2. Open the “SampleScene” scene
3. Select the “Cube” GameObject in the Hierarchy
4. Observe the “Cube (Mesh Filter)” Component
Expected result: There is a “Cube Mesh” assigned to the “Mesh” field
Actual result: There is a “Type mismatch” assigned to the “Mesh” field
Reproducible with: 2022.2.0a17, 2022.2.10f1, 2023.1.0b6, 2023.2.0a5
Not reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.0a16
Reproducible on: Windows 11 Pro
Note: It doesn’t affect the Mesh rendering
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Resources.UnloadUnusedAssets() freezes the Editor when releasing Mesh objects
- 16-bit Sprite Textures have a banding effect and loss of data when packing into Variant Sprite Atlas
- HDRP Cluster artifacts when having more than 100 lights
- ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
- Custom attributes are not properly converted to subgraphs
Add comment