Search Issue Tracker
Fixed in 7.2.0
Votes
0
Found in [Package]
7.1.1 - 8.0.0
Issue ID
1210710
Regression
Yes
"Output value 'vert' is not completely initialized" error is thrown when PBR graph is created using URP
How to reproduce:
1. Create a new URP project
2. Create a new PBR graph
3. View the PBR graph's details in the Inspector window
Expected result: No errors are thrown
Actual result: Output value 'vert' is not completely initialized
Reproducible with: 2019.3.0b3, 2019.3.0f5, 2020.1.0a20
Not reproducible with: 2019.3.0a10, 2019.3.0b2
Could not test with: 2017.4.36f1, 2018.4.15f1, 2019.2.18f1, 2019.3.0a9(URP was not yet available)
Reproducible with package versions: 7.1.1, 8.0.0
Not reproducible with package versions: 7.0.0, 7.0.1
Notes:
1. Only reproducible with URP. Does not reproduce when using HDRP(tested 7.1.7)
2. Did not reproduce on Mac/Metal(7.1.7) and on Vulkan
3. Reproduces on D3D11 and D3D12
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
- Duplicate External Textures start appearing when a Texture created with "CreateExternalTexture" is modified causing Memory Usage spikes on VisionOS
- Silent crash when using a "Blend Shape" in a "Skinned Mesh Renderer" to move vertices to Vector3.positiveInfinity, and "Occlusion Culling" is baked
- Some Prefab Source and Override content bounds are misaligned
- The Package Manager's "install packages by..." panels break when Domain Reload is triggered, and the panel is open
- Crash with multiple stack traces when leaving a docked VFX Graph open
vdci
Feb 04, 2020 12:42
How to reproduce:
1. Create a new URP project
2. Create a new PBR graph
3. View the PBR graph's details in the Inspector window
Expected result: No errors are thrown
Actual result: Output value 'vert' is not completely initialized
Reproducible with: 2019.3.0f5, 2019.3.0f6