Search Issue Tracker
Fixed in 2020.2
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
- LineRenderer points lists suffers from performance issues when list is large
- Shaders take a lot of memory at runtime even when only one variant is used
- Lego Microgame crashes the Linux Editor at "ScanFilter::Merge" when selecting a WebGL build location
- GameObject reference is null when creating it inside Reset() function and assigning Script as component
- GameObject/Prefab inspector preview is slow for complex hierarchies
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