Search Issue Tracker
Fixed in 6.7.0
Votes
3
Found in [Package]
6.5.3
Issue ID
1148764
Regression
Yes
[LWRP] Texture gets unassigned on updating Lightweight RP package
The texture gets unassigned on updating Lightweight RP package.
Steps to reproduce:
1. Create a new project with Lightweight RP template.
2. Go to Window > Package manager > Lightweight RP.
3. Update package version from 5.2.3 to any higher version (ex. 6.5.3)
Note:
1. By default, package version is set to 5.2.3 which is marked as 2019.2. verified.
2. Editor crashes on updating Lightweight RP package in 2019.3.0a1, so unable to reproduce it in 2019.3.
3. Video is attached for the reference. (LWRP.rar file)
Actual result:
The texture gets unassigned on updating Lightweight RP package.
Expected result:
The texture is assigned and rendering as expected even when the package is updated.
Reproducible in: 2019.2.0a13, 2019.2.0a1
Not reproducible in: 2019.1.0f2, 2018.3.0f2
Environment: Mac and Windows.
-
phil_lira
May 14, 2019 07:41
This was caused because the upgrader was not kicking off in some cases. A fix in the upgrader will be available soon. Meanwhile, in order to make it work you just need to reimport all materials.
-
GCat
May 03, 2019 04:54
god bless you SmartCarrion
-
SmartCarrion
May 03, 2019 00:34
For anyone needing it, here is my workaround:
***Backup first***
From working 2018.3 project
open windows command prompt (with admin privileges)
ROBOCOPY "source\Assets" "tempdestination\Assets" *.mat /S /IS /ITload up destination project in 2019.1 (or your new version of LWRP)
Wait for unity to process everything and have it come up with all materials greyback to windows cmd:
CD /D "destination\Assets"
DEL /S /Q *.matcheck back on unity, all materials should be gone and everything turns pink.
back to windows cmd:
xcopy ""tempdestination\Assets" "destination\Assets" /k/r/e/i/s/c/h/f/o/x/ycheck back on unity, it should process everything and you are ok.
(make sure you have a backup project in case this messes up)
-
SmartCarrion
May 02, 2019 14:02
This is only partially a duplicate of https://issuetracker.unity3d.com/issues/lwrp-upgrading-lwrp-5-dot-2-3-to-5-dot-3-1-causes-all-materials-to-lose-their-albedo-texture it is reproducible in the production releases when following the steps in that bug
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
- SpeedTree does not move when using WindZone
- "Undeclared identifier 'LinearToSRGB'" error is thrown when creating a color variable with HDR color mode and assigning a Custom Render Texture target in Shader Graph
- Input System package is missing when creating a new HDRP project
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
Resolution Note (fix version 6.7.0):
This was caused by the upgrader not being kicked off automatically in some cases. We fixed the upgrader to kick off always in 6.7.0 version. For the ones that can't upgrade to 6.7.0 the solution is simple. Just reimport all materials and the upgrader willl run.