Search Issue Tracker
Not Reproducible
Votes
0
Found in
2022.3.58f1
6000.0.38f1
6000.1.0b6
6000.2.0a3
6000.3.0a1
Issue ID
UUM-97370
Regression
No
Shadows are rendered differently when Game view resolution settings are changed and certain parameters are used
How to reproduce:
1. Open the “ShadowTest2.zip“ project
2. Open the “Main Scene“ Scene
3. Focus on the Game view
4. Change the resolution to “4K UHD (3840x2160)”
5. Observe the Game view
Expected results: Shadows are rendered like they were before step 4
Actual results: Shadows are rendered on objects they shouldn’t be rendered on
Reproducible in; 2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a3
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- Shadows are rendered differently if the “Far Plane” or the “Fiel Of View“ properties of the “Main Camera“ are changed
- Shadows are rendered differently if the “Splits“ property of the URP asset is changed
- Toggling “LowResolution Aspect Ratios“ also makes the Shadows render differently
- Could not reproduce on a new project (likely because of the difference in the URP settings)
- Player build fails and Game view and Scene view break when trying to build and run
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
No longer reproduces in 6.2 or later unity versions.