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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
Auto is not on by default anymore. So most users will not be affected by this.