The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
What is the Device.Present in Unity Profiler and why does it take so long?
Hello,
I am trying to understand how the processing time in my Hololens application is being spent.
It normally runs at 30FPS, but when I consult the Unity Profiler, it says that only around 8 ms is being spent on the actual rendering.
To run at 60FPS, it is my understanding that the GPU processing tasks should stand bellow the total time of 16.67 ms. However, the Device.Present is taking around 25ms, eating up the reminder time of a frame (~8 ms) + a full frame.
Does anyone knows how this time is being spent? I would expect that some of it is on time synchronization with the display, but 8ms sounds like enough spare time.
Here is a figure of the profiler
Thanks a lot!
Henrique
P.S. I know that the GPU profiler consumes resources in the device, but the software was running at 30 FPS even before connecting the profiler. Thus, the added profiler time did not altered the final behavior in any meaningful way.