Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2019.3.0f5
2019.4
2020.2
Issue ID
1245967
Regression
No
Changes made to Image's pixelsPerUnitMultiplier property are not applied when changing it in Script during Runtime
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. Observe the Panel GameObject's Image
Expected result: Changes made to Panel's Image pixelsPerUnitMultiplier property are applied
Actual result: Changes made to Panel's Image pixelsPerUnitMultiplier property are not applied
Reproducible with: 2019.4.1f1, 2020.1.0b14, 2020.2.0a15
Couldn't test with: 2018.4.24f1 ('Image' does not contain a definition for 'pixelsPerUnitMultiplier')
Note: Issue doesn't happen if Image is set to be "dirty"
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
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
Resolution Note (fix version 2020.2):
Added a setVerticiesDirty call to the API. Couldn't reproduce it but that dirty should be there. Fixed in Unity 2020.2.0b1