Search Issue Tracker
By Design
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.45f1
6000.1.0b13
6000.2.0a8
6000.3.0a1
6000.4.0a1
Issue ID
UUM-102119
Regression
No
Lights on Renderer Features break when rendering at lower resolution with "Forward+" Rendering Path
Reproduction steps:
1. Open the attached “IN-98447.zip” project
2. Open the “SampleScene”
3. Select the “PC_Renderer.asset” from the Project Window (Assets > Settings)
4. In the Inspector, change the Rendering Path to “Forward+”
5. Observe the Game view
Expected result: The light is visible on the buildings (rendered as Renderer Feature)
Actual result: Some of the lights are not visible on the buildings, only on the Cube behind
Reproducible with: 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Couldn’t test with: 2022.3.61f1 (Render Graph not supported)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- On the same asset (PC_Renderer), in the “Draw Low Res Feature” Renderer Feature, turning down the Resolution Divider property to “1”, shows the expected result
- Does not reproduce with “Forward” or “Deferred” Rendering Paths
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
- WebGPU errors when CoreCopy shader is used to copy an MSAA texture
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
Resolution Note:
Hi there!
In order for F+ to work correctly with a non-screen resolution render target, you must set the global float4 shader constant `_ScaledScreenParams` accordingly.