Search Issue Tracker
Fixed
Fixed in 2021.3.26f1, 2022.2.16f1
Votes
0
Found in
2021.3.22f1
2022.2.14f1
Issue ID
UUM-32667
Regression
No
"program_source:9:8: error: unknown type name 'Mtl_VertexOut'" is logged into the "Editor.log" when reimporting a Shader with empty vprog
How to reproduce:
1. Open the user-attached project “metaLerror”
2. In the Project window, right-click on “VolumetricLightBeamSRP” Shader to open the context menu
3. Click “Reimport”
4. Observe the “Editor.log” file
Expected result: There are no errors in the “Editor.log”
Actual result: There is a “program_source:4:8: error: unknown type name 'Mtl_VertexOut'“ error in the “Editor.log”
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.14f1, 2023.1.0b10, 2023.2.0a6
Fixed in: 2023.1.0b11, 2023.2.0a7
Reproducible on: macOS Ventura 13.1.2 (M1)
Not reproducible on: Windows 11 Pro
Notes:
- Not reproducible on build
- The error is not logged into the Console of the Unity Editor
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment