Search Issue Tracker
By Design
Votes
0
Found in
2020.3.42f1
2021.3.15f1
2022.1.24f1
2022.2.0f1
2023.1.0a22
Issue ID
UUM-21412
Regression
No
Data type compiles to uint when declaring a struct in a shader
Steps to reproduce:
1. Open the “NMShader” project
2. Open the “KeepItReal” shader in Assets/Shaders
3. Observe the code where the struct “MyStruct” is
4. Select the “KeepItReal” shader
5. In the Inspector menu press the arrow on the right side of “Compile and show code” and select both Metal and GLES3x
6. In the Inspector menu press “Compile and show code”
7. Observe the compiled code where the “MyBuffer_Type” struct is
Expected result: The data type stays the same as in the not compiled shader
Actual result: A shader with declared struct compiles data types to uint
Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.0f1, 2023.1.0a22
Reproduced on: macOS Monterey 12.2 (Intel)
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Works as intended.