Search Issue Tracker
By Design
By Design in 2023.1.X
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Works as intended.
Resolution Note (2023.1.X):
Works as intended.