Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
6000.4.0a1
Issue ID
UUM-112050
Regression
No
Cutout Shader does not clip pixels completely when they are in a closed, loaded subscene
How to reproduce:
1. Open the “repro.zip“ project
2. Open the “SampleScene“
3. Focus on the Game view
4. Observe the Game view
Expected result: No sphere pixels are clipping
Actual result: Rightern orange sphere pixels are clipping
Reproducible in: 2023.3.0b10, 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3
Could not test in: 2023.1.0a1, 2023.2.0a20 (Entities and Test Framework packages are incompatible)
Reproduced on: MacOS Sequoia 15.3
Not reproduced on: Windows 11 Pro (24H2)
Note: Opening the SubScene will prevent the bug from happening
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
Add comment