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
- [MotionVectors][RenderingDebugger][MSAA] Render Graph Execution error and black Game View when enabling MotionVectors overlay in the Rendering Debugger with MSAA
- "[Project Auditor] Could not find any registered modules." warning is thrown when clicking "Start Analysis" and the rules were installed while there are compilation errors in the Editor
- Color Picker window flickers when expanding or collapsing dropdowns
- “ArgumentException: Object that does not belong to a persisted asset cannot be set as the target of a LazyLoadReference" is thrown when changing Unsupported Selector Action and saving in UI Builder
- Cursor image flickers in Viewport preview when unsupported Texture 2D is assigned to element
Resolution Note:
Auto is not on by default anymore. So most users will not be affected by this.