Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
946907
Regression
No
Areas missed by Progressive Lightmapper when using Mesh compression
How to reproduce:
1. Download attached project file
2. Open "Test" Scene
3. Go to Windows -> Lighting -> Settings, select Progressive in Lightmapper and press Bake
4. Look for black areas when viewing the UV Charts
Expected result: There should be no black areas when using the progressive lightnapper.
Actual result: Setting meshes to be compressed resulted in black areas when using the progressive lightmapper.
Reproduced with: 5.6.3p2, 2017.1f1, 2017.2.0b10, 2017.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mesh Rendered GameObject using the SpriteLitDefault Material becomes invisible when animating with the URP Sprite-Lit-Default Shader
- Compilation errors occur when using PluginAPI headers in a C environment
- Profiler connects to a different opened Editor project when more than one project is open and building for WebGL with Autoconnect Profiler enabled
- Creating and then deleting the "Integration Update: Rotation" block breaks and makes unusable VFX Graph
- “ArgumentNullException: Value cannot be null.” when deleting a newly created input action
Add comment