Search Issue Tracker
Fixed in 2018.3.X
[UI] Progressive CPU Lightmapper is named as 'Progressive' in the Lighting window
Steps to repro:
1. Create new project in Unity 2018.3;
2. Open Lighting window (Window>Rendering>Lighting Settings);
3. Expand the Lightmapper dropdown in the Lightmapping Settings foldout;
4. Observe the items in the dropdown list.
Progressive CPU and Progressive GPU lightmapper are named as 'Progressive CPU' and 'Progressive GPU (Preview)'.
Progressive CPU Lightmapper is named as 'Progressive'. See attached screesnhot.
Regression introduced in 2018.3.0b4.
- Reproducible in 2019.1.0a3 ( lighting/re-expose-GPU-lightmapper) and 2018.3.0b4 (2018.3/staging);
- Not reproducible in 2019.1.0b3 and 2018.3.0b3;
- From the user perspective it would be more convenient to clearly distinguish between Progressive CPU and Progressive GPU lightmappers. Otherwise, it might create confusion;
- Progressive CPU Lightmapped was previously named as 'Progressive' in 2018.2 and earlier before the introduction of the Progressive GPU Lightmapper. This made sense, however now with the introduction of GPU Lightmapper the context has changed.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset