Search Issue Tracker
Fixed in 7.2.X
Votes
0
Found in [Package]
5.3.1 - 7.1.7
Issue ID
1210058
Regression
Yes
Scene view Turns Solid Black when it contains a SpeedTree with specific materials and Bloom is enabled
How to reproduce:
1. Import the attached package named "Package_1210058"
2. Drag the SpeedTree into the scene
3. Zoom away from the tree until it reaches LOD1 state
4. Click the Middle mouse button, move the cursor in and out from the scene or slightly move the camera
Expected behavior: Scene view behaves normally, displaying the SpeedTree and its surroundings
Actual behavior: Scene view turns solid black or constantly flickers
Reproducible with: 2019.1.0b8, 2019.2.18f1, 2019.3.0f5, 2020.1.0a19
Not reproducible with: 2018.4.15f1
Could not test with: 2017.4.36f1(No HDRP)
Reproducible with package versions: 5.3.1, 7.1.7
Not reproducible with package versions: 4.1.0, 5.2.3
Notes:
1. In some versions just entering the Tree's LOD1 state causes the issue to occur and step 4 becomes unnecessary
2. Disabling Scene Bloom in older HDRP versions solves the issue(Track_1210058_V2). In newer versions disabling Scene's post-processing layer also helps
3. Tested Graphics APIs - D3D11, D3D12, Vulkan, Metal. All reproduce the issue
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
- GameObjects change Hierarchy order when undoing adding Component to multiple GameObjectsGameObjects change Hierarchy order when undoing adding Component to multiple GameObjects
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
Resolution Note (fix version 7.2):
Fixed in package version 7.2.0 which should become available in 2019.3.1f1 and above