Search Issue Tracker
Third Party Issue
Third Party Issue in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.4f1
6000.4.0b4
6000.5.0a4
Issue ID
UUM-132086
Regression
No
Realtime GI behaves differently when using Unlit (Amplify) and Lit (Shader Graph) shaders in URP
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/Yulele/BakingTest.unity” Scene
3. Enter the Play Mode
Expected result: Both sides are lit similar
Actual result: Right side is more lit
Reproducible with: 6000.0.65f1, 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Amplify Shader (Unlit template) is present on the left, and on the right the Shader Graph – Lit shader is present
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
- [Linux] Cannot reorder GameObjects in the Hierarchy when the AI Assistant package is installed
- [iOS] Text Input field stops receiving changes when the "Cancel" button is used on the soft keyboard
- [WebGPU] URP RenderGraph RenderPass doesn't clear textures
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
Resolution Note:
Thank you for reporting a bug to Unity.
Our investigation indicates the issue originates from a third-party asset, plugin, or service, rather than Unity itself. Because the problem lies outside our codebase, we're unable to address it directly.
We will close this case as a third-party issue. We recommend contacting the vendor or maintainer for support. You may also reach out to our community in the discussion forums. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
Our investigation indicates the issue originates from a third-party asset, plugin, or service, rather than Unity itself. Because the problem lies outside our codebase, we're unable to address it directly.
We will close this case as a third-party issue. We recommend contacting the vendor or maintainer for support. You may also reach out to our community in the discussion forums. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation.