Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3
2019.3.11f1
2020.1
2020.2
Issue ID
1256699
Regression
No
ASTC HDR Lightmaps clamp to 1 when editor is set to Android platform
How to reproduce:
1. Open the "lightmap" Scene in the attached "astchdr-clamped.zip" Project
2. Make sure auto baking is checked in the Light Settings
3. Switch Build Target to Android
4. Observe the scene
Expected: HDR Lightmaps value is not clamped to 1
Actual: HDR Lightmaps value is clamped to 1 resulting in setting not being able to obtain brighter values
Reproducible with: 2019.4.2f1, 2020.1.0b14, 2020.2.0a15
Could not test with 2018.4 as the editor was spitting errors about settings being serialized with a different version
Note: does not occur when editor is on Windows or iOS platform
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a18, backported to 2020.1