Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0f2
Issue ID
1059756
Regression
Yes
[LWRP] Shadows are not updated relative to the camera position when updating to 2.0.5
How to reproduce:
1. Create a new LWRP project
2. Open "PackageManager" window
3. Select LightWeight Render Pipeline and update it from 2.0.3 to 2.0.5 (also reproducible with 2.0.4)
4. In Scene View, move away from 0;0;0 and observe objects' shadows
Expected result: shadows update relative to camera position
Actual result: shadows are not updated as if the camera is in 0;0;0 coordinates
Reproducible with Unity versions: 2018.1, 2018.3
Reproducible with LWRP package versions: 2.0.4, 2.0.5
Not reproducible with LWRP package versions: 2.0.3
Workaround: in "Package Manager" window, update LWRP package to 2.0.3
Comments (1)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Pr0x1d
Aug 09, 2018 18:12
I would like to talk about it being fixed, when. I have waited long time trying to fix this, found this finally, even spoke on forum and everyone said it will be fixed soon. Here I found out it should be fixed in future release, its now on version 2018.2.2f1, the LWRP in on 3 and its still there. Its still only works on 2.0.3 LWRP. Thanks