Search Issue Tracker
By Design
Votes
0
Found in
2022.3.49f1
6000.0.23f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-83748
Regression
No
Shadow artifacts appear when using a merged mesh with a specific Near Plane value in the Play Mode in URP
How to reproduce:
1. Download Blender and make it a default application for “.blend“ files (Reason for this in the comments)
2. Open the “ReproProject“ project
3. Open the “ReproScene“
4. Enter the Play Mode
5. Wait for a bit for the meshes to load
6. Observe the Game view
Expected result: No light artifact
Actual result: Light artifact appears around “StandLampLightson” GameObject
Reproducible with: 2022.3.49f1, 6000.0.23f1
Could not test with: 2021.3.44f1 (Some scripting properties not present that are required for reproduction)
Reproducible on: macOS 14.6.1 (Intel), Windows 10 Pro (Reporters)
Not reproducible on: No other environments tested
Notes:
- Seems to depend on the light elements in the merged mesh has different pivot points in the world
- According to the reporter did not reproduce on a new project, even after migrating the merged mesh
- If you navigate to the “StandLampLightson“ after entering the Play Mode and change the Near Plane value to be “<0.34” the artifact will appear, if it “>0.34“ artifact will not be visible anymore
- Lights that are not merged perform as expected
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
As we have already communicated to the user, the issue in question is not a bug.
When merging the meshes, the positions of the vertices shift slightly, which in turn affects the results of the Point Light shadow calculations.
Since the vertex positions are only altered minimally, the mesh appears visually identical before and after the merge.
However, because the Point Light is positioned very close to the mesh, even a tiny difference can result in significant variations in shadow calculations.