Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Evaluate performance of PressableButtonUnityUI #318

Closed
IssueSyncBot opened this issue Aug 21, 2023 · 5 comments
Closed

Evaluate performance of PressableButtonUnityUI #318

IssueSyncBot opened this issue Aug 21, 2023 · 5 comments
Labels
Package: UX Components The Project ux components package is impacted by this issue. Status: Duplicate The issue is a duplicate of another issue. The duplicate issue must be referenced in the comments. Type: Feature Request A request for a new feature that can be included with the next minor version release.

Comments

@IssueSyncBot
Copy link

IssueSyncBot commented Aug 21, 2023 •
edited
Loading

Original issue opened by:

@ritijain ritijain

Describe the Issue

Creating 3D content using UnityUI can be fairly tricky, and can cause performance issues. There have been some concerns raised by partners that when a button which is a very core components of any app is not performant, it can cause some serious perf issues.

I realized that the Unity UI pressable button is using 2 Image components rendered at different Z depths. While it looks great and is fully functional, how does it impact perf?

ISSUE MIGRATION

Issue migrated from: microsoft/MixedRealityToolkit-Unity#6180
@IssueSyncBot IssueSyncBot added MRTK3 Package: UX Components The Project ux components package is impacted by this issue. Status: Duplicate The issue is a duplicate of another issue. The duplicate issue must be referenced in the comments. Type: Feature Request A request for a new feature that can be included with the next minor version release. labels Aug 21, 2023
@IssueSyncBot
Copy link
Author

Original comment by:

@ritijain ritijain

@AdamMitchell-ms , @julenka -

I am not sure if a discussion about performance happened when this work was done. If this seems like a legit concern, then there should be a perf evaluation of this (and similar unity ui) components.

If there are no concerns, i think it would be great to capture the discussion on Github so that we can point it to folks who express concerns.

@IssueSyncBot
Copy link
Author

Original comment by:

@Zee2 Zee2

This is an ongoing concern for Canvas-based elements in MRTK3. Already having an ongoing discussion with @Cameron-Micka for how best to mitigate drawcalls here.

@IssueSyncBot
Copy link
Author

Original comment by:

@Zee2 Zee2

Investigation is ongoing and promising developments are in order :)

@IssueSyncBot
Copy link
Author

Original comment by:

@AMollis AMollis

@marlenaklein-msft Can you follow-up with @Cameron-Micka on his ideas here

@IssueSyncBot
Copy link
Author

Original comment by:

@AMollis AMollis

We're now tracking this issue with the following investigation task

@IssueSyncBot IssueSyncBot mentioned this issue Aug 21, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Package: UX Components The Project ux components package is impacted by this issue. Status: Duplicate The issue is a duplicate of another issue. The duplicate issue must be referenced in the comments. Type: Feature Request A request for a new feature that can be included with the next minor version release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@IssueSyncBot