Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0b4
Issue ID
1086524
Regression
Yes
[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.
Expected result:
Progressive CPU and Progressive GPU lightmapper are named as 'Progressive CPU' and 'Progressive GPU (Preview)'.
Actual result:
Progressive CPU Lightmapper is named as 'Progressive'. See attached screesnhot.
Regression introduced in 2018.3.0b4.
Notes:
- 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.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment