Closed IssueSyncBot closed 1 year ago
IssueSyncBot
commented
1 year ago 
Hmm, what are your build settings in Visual Studio? Debug/Release/Master and ARM/ARM64? We recommend Release or Master and ARM64. I've also heard that we're tracking some URP issues on UWP in Unity 2021 (more info at https://docs.microsoft.com/windows/mixed-reality/develop/unity/known-issues#active-blocking-issues), but I didn't think they were quite as severe as this!
IssueSyncBot
commented
1 year ago 
Hi
I just tested Build-In pipeline,and it's fine, frame rate is 50 when published on Hololens2.
Other settings are the same，so the reason is the problem of rendering pipeline.
This is really exaggerated，frame rate is than 10 in URP.
Li
------------------ 原始邮件 ------------------ 发件人: "microsoft/MixedRealityToolkit-Unity" @.>; 发送时间: 2022年6月11日(星期六) 凌晨1:34 @.>; @.**@.>; 主题: Re: [microsoft/MixedRealityToolkit-Unity] Very low performance after publishing with MRTK3 default configuration (Issue #10635)
Hmm, what are your build settings in Visual Studio? Debug/Release/Master and ARM/ARM64? I've also heard that we're tracking some URP issues on UWP in Unity 2021 (more info at https://docs.microsoft.com/windows/mixed-reality/develop/unity/known-issues#active-blocking-issues), but I didn't think they were quite as severe as this!
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
IssueSyncBot
commented
1 year ago 
I will be sure to follow up with Unity.
IssueSyncBot
commented
1 year ago 
@qiaofuwenlu , can you confirm you are on URP? I've not been able to reproduce perf issues this bad on URP.
IssueSyncBot
commented
1 year ago
Hi, we're closing this as can't-repro for now. If you have more detailed repro information (such as a zip of the project + project settings + etc) please reopen!
IssueSyncBot
commented
1 year ago
Hi
My settings in VS is Release and ARM64.
Do you think it may be caused by URP? I will try Build-in today.
This problem is in Mrtk v2.x has a similar problem.But there is a clear contrast. When I use MRTK v2.x, the settings in MixedRealityTookit in Hierarchy. if select "OpenXRConfigurationProfile "the frame rate is low than 10 after publish on Hololens2. But if select "DefaultHololens2ConfigurationProfile "the frame rate is hgih than 50 after publish on Hololens2.
There is only one Default ConfigurationProfile in Mrtk3,Without comparison, I don't know whether it is caused by the configuration file or some errors.
We look forward to your reply.
Thanks~
Li
------------------ 原始邮件 ------------------ 发件人: "microsoft/MixedRealityToolkit-Unity" @.>; 发送时间: 2022年6月11日(星期六) 凌晨1:34 @.>; @.**@.>; 主题: Re: [microsoft/MixedRealityToolkit-Unity] Very low performance after publishing with MRTK3 default configuration (Issue #10635)
Hmm, what are your build settings in Visual Studio? Debug/Release/Master and ARM/ARM64? I've also heard that we're tracking some URP issues on UWP in Unity 2021 (more info at https://docs.microsoft.com/windows/mixed-reality/develop/unity/known-issues#active-blocking-issues), but I didn't think they were quite as severe as this!
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Original issue opened by:
Describe the bug
Very low performance after publishing with MRTK3 default configuration.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Just a simple scene, the frame rate should be 50 or higher.
Screenshots
If applicable, add screenshots to help explain your problem.
Your setup (please complete the following information)
Target platform (please complete the following information)
Additional context
All my configurations are based on demonstrated in Mixed Reality Dev Days 2022. Theoretically, a simple scene should have a high frame rate，But a frame rate of 10 is unacceptable. Is this a performance problem of mrtk3 or a problem in the default configuration？
ISSUE MIGRATION
Issue migrated from: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/10635