Search Issue Tracker
In Progress
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X
Fix In Review for 6000.3.0a2
Votes
1
Found in
6000.0.50f1
6000.1.6f1
6000.2.0b4
Issue ID
UUM-108240
Regression
No
HDRP 6-way VFX Shader is lit incorrectly when World coordinates are used
Reproduction steps:
1. Open the attached “IN-103590.zip” project
2. Open the “SampleScene”
3. Open the Lighting Window (Ctrl+9)
4. Click “Generate Lighting”
5. Observe the Game view
Expected result: Both smokes are lit the same, accordingly to the lighting
Actual result: Smoke to the right (who uses World coordinates) is lit too brightly
Reproducible with: 6000.0.50f1, 6000.1.6f1, 6000.2.0b4
Couldn’t test with: 2022.3.62f1 (Could not downgrade)
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: no other environment tested
Notes:
- Also reported in discussions: [https://discussions.unity.com/t/6-way-vfx-lit-uncorrect/1648259|https://discussions.unity.com/t/6-way-vfx-lit-uncorrect/1648259]
- Smoke with Local coordinates is lit correctly
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
- Main Camera rendering is being overwritten by a UI Camera when using multiple cameras with URP and the second camera's background type is set to "Uninitialized"
- VisualTreeAsset has significantly increased memory allocation size at runtime when the project is built with IL2CPP scripting backend
- NullReferenceException is logged when cancelling Shader Graph recovery of an already deleted Shader Graph
- White Edges appear during Camera movement in runtime when using FSR2 with Motion Vectors and Exposure enabled
- Lens Flare renders without occlusion when the light source is obstructed by solid objects when running on Android using OpenGL
Resolution Note:
Forward-ports for this version need to be handled at a later time.