Search Issue Tracker
Fixed
Fixed in 6000.5.0a7
Votes
0
Found in
2021.3.47f1
2022.3.55f1
6000.0.33f1
6000.1.0b1
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-92181
Regression
No
Incorrect precision when Vertex data is missing
Reproduction steps:
1. Open the attached “repro_IN-91640“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Select the “Assets/CompilationTest.shadergraph“ Shader
4. In the Inspector, press “View Generated Shader“
5. In the opened “GeneratedFromGraph-CompilationTest.shader“, search for “struct VertexDescription“
6. Once found, notice what it consists of
Expected result: “VertexDescription” method consists of three “half3” values
Actual result: “VertexDescription” method consists of two “half3” and one “float3” value
Reproducible with: 2021.3.47f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0b1
Reproducible on: Windows 10 (22H2), Windows 11 (23H2)
Not reproducible on: No other environments tested
Comments (1)
-
DevDunk
Jan 24, 2025 05:25
Isn't the expected results 3 half3 values?
It seems like expected and actual are flipped. If the shader graph is set to half, I expect non exposed values will be half
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Resolution Note:
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7