Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2021.3.47f1
2022.3.55f1
6000.0.33f1
6000.1.0b1
6000.2.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)
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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
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