Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0f1
Issue ID
1028364
Regression
No
[PLM] UX issues with baking terrain on Auto Mode
When editing level geometry, be it via Terrian sculpting or ProBuilder, having Progressive Lighmapper on Autogenerate by default yields a really bad user experience because of bad perfoemance and the annoying blue texture that appears all the time.
While I understand that Progressive Lightmapper is actually a great feature, I don’t think that having it on by default, from the very start of the project is something an advanced Unity user would do, and I’m even more concerned that a new user won’t understand what it is, what is happening and will just flag this behaviour as a bug!
Some other solution is needed for the default 3D template settings.
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
- Audio Mixer does not change volume when lowering volume on an Audio Mixer loaded from AssetBundles
- Error “Value cannot be null. Parameter name: key UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” thrown and Addressables build fails when "Include in Build" is disabled and using Addressables For Android package
- “error CS0433: The type 'CodeBinaryOperatorType' exists in both 'System.CodeDom and 'System" compilation errors are thrown when opening a specific project
- Metal Vertex Shader warning is being thrown when creating a VR Template Project
- Asset database warning is thrown when declaring font variable in the USS text file
Resolution Note:
Auto is not on by default anymore. So most users will not be affected by this.