Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2.0a5
2019.3
2020.1
2020.1.0a11
Issue ID
1194857
Regression
No
[UIElements] "Hidden packages visibility" toggle value should be linked with the project
Reproduction steps:
1. Create a New Project
2. In the Project window expand the "Packages" folder
3. Click on the "Toggle hidden packages visibility" toggle
4. Notice that the expanded packages are no longer visible
5. Re-open the project
6. In the Project window expand the "Packages" folder
7. Notice that the expanded packages are still not visible
Expected Result: "Toggle hidden packages visibility" toggle should be set per project
Actual Result: "Toggle hidden packages visibility" toggle is set globally
Reproduced with: 2020.1.0a11, 2019.3.0b9, 2019.2.11f1, 2019.2.0b1, 2019.2.0a5
Did not reproduce on (Feature was not yet implemented): 2019.2.0a4, 2019.2.0a1, 2019.1.14f1, 2018.4.12f1, 2017.4.34f1
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (2020.1.X):
It has been decided to remove this functionality