Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1.0b2
2019.2.0a3
2019.2.0a4
Issue ID
1126959
Regression
Yes
[nouveau] Package Manager window isn't rendered
To reproduce:
1) Create new project
2) Open Window -> Package Manager
It is not rendered. You can see that it still functions by clicking where "All packages" context menu is - it will open up as expected
Not reproduced - Reproduced
2019.2.0a2 - 2019.2.0a3, 2019.2.0a4
2019.1.0a10, 2019.1.0b1 - 2019.1.0b2, 2019.1.0b3
2018.3.5f1 - x
If you install proprietary Nvidia drivers, the issue is also not reproducible
Workaround: Launching unity with the options "-force-glcore33 --force-clamped" will allow the package manager to render properly by disable advanced rendering features.
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
This is a duplicate of issue #1146281