Search Issue Tracker
Third Party Issue
Votes
1
Found in
2022.3.12f1
2023.1.19f1
2023.2.0b16
2023.3.0a12
6000.0.0b11
Issue ID
UUM-55802
Regression
No
With Rendering Path set to Forward+ the Spot Light illuminates GameObjects only when the Scene/Game view window is shrinked
How to reproduce:
1. Open the “ForwardPlusCustomShaderBug“ project
2. Open the “Demo“ scene
3. Enable the "Custom Shader" GameObject and disable the "Lit" GameObject in the Inspector window
4. Set the Rendering Path to Forward+
5. Resize the Scene view window
6. Observe the Spot Light behavior in the Scene view window
Expected result: The Spot Light illuminates the “Sphere“ and “Plane“ GameObjects regardless of the Scene view window size
Actual result: The Spot Light illuminates the “Sphere“ and “Plane“ GameObjects only when the Scene view window is shrinked
Reproducible with: 2022.3.12f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a12
Could not test with: 2021.3.32f1 (Forward+ is not an option for Rendering Path)
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Notes:
- The same behavior happens when resizing the Game view window
- The Spot Light also starts illuminating the GameObjects when zoomed closer to them
- The Spot Light also starts illuminating the GameObjects when the Outer Spot Angle is more than 90 depending on the Scene view window size
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:
Hi Ned,
URP Forward+ relies on normalized screen space UVs to select the correct tile for lighting.
In the custom shader, ensuring that the input data is set correctly fixes the corruption. (E.g. Adding l.43 lightingInput.normalizedScreenSpaceUV = GetNormalizedScreenSpaceUV ( input . positionCS ) ; )
Hope this helps !