Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2
Issue ID
1334521
Regression
No
[URP] [Debug View] [Mobile] Lighting Features - “None” can’t be marked
How to reproduce:
1. Create a new project
2. Switch platform to Android or iOS
3. Enable "Development Build" property in Build Settings
4. Build & run project on the device
5. Double-tap screen with three fingers (to open Rendering Debug view)
6. Go to Lighting settings
7. Unfold "Lighting Features" property
8. Try to enable "None"
Expected result: "None" should be selected by default or user should be able to mark it. After clicking on the checkbox - the mark instantly disappears. The function itself works - all other checkboxes disappear, but it's incorrect from UI/UX perspective. Also, in the Editor the checkbox gets marked (in the debugger window), so the behaviour should be the same on mobile
Actual result: The mark instantly disappears
Reproducible on: 2021.2.0a15
Reproduced on these devices:
VLNQA00340, Samsung Galaxy Note20 Ultra 5G (SM-N986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00287, Motorola moto g(7) power (moto g(7) power), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
Google Pixel 4, Android 10, CPU: Snapdragon 855 (SM8150), GPU: Adreno (TM) 640
iPhone 12
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Decided to postpone this until we make more significant changes to the runtime UI (reimplement using UI Toolkit). The task is logged in JIRA to retain the information: https://jira.unity3d.com/browse/XPIPELINE-261