Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.1f1
2021.1
2021.2
Issue ID
1332369
Regression
Yes
SpriteMask use GPU inefficiently in Play Mode
Reproduction steps:
1. Open attached project "New Unity Project (2)"
2. Open Scene 'BenchmarkSpriteMask'
3. Play Scene
4. Observe GPU usage in Task Manager or other software
Expected result: Relatively low GPU usage
Actual result: High GPU usage
Reproducible with: 2019.4.24f1, 2020.3.4f1, 2021.1.4f1, 2021.2.0a15
Not reproducible with: 2018.4.33f1
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
The example project doesn't provide a good case of using sprite masks. Sprite masks are tightly integrated with unity's legacy systems. Refactoring the code to be optimized isn't trivial and would require a large amount of engineering effort. Unfortunately since this is one-off case, we don't think it is worth allocating the resources to fix.