Skip to content

Conversation

Cameron-Micka
Copy link
Member

@Cameron-Micka Cameron-Micka commented May 15, 2019

Overview

  • The Visual Profiler now supports user defined colors for performance thresholds on the frame info panel. Defaults to green when at 95%+ of the target framerate, yellow when at 75%+ of the target framerate, and red otherwise. (A request from multiple users.)

  • Portions of the profiler can be dynamically toggled on/off, such as the frame info panel and memory stats.

VisualProfilerChange

  • Fixed an issue where required shader permutations for rendering the frame info items using instancing were not included in player builds. This will result in improved rendering performance for the Visual Profiler.

Verification

Verify the Visual Profiler displays in editor and player .

Fixes: #4414

Copy link
Contributor

@keveleigh keveleigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Looks like there's a merge conflict though.

@Cameron-Micka
Copy link
Member Author

Looks good! Looks like there's a merge conflict though.

Thank you Kurtis! Just fixed the merge.

@julenka
Copy link
Contributor

julenka commented May 18, 2019

/azp run mrtk_pr

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

/// </summary>
bool ShowProfiler { get; set; }

/// <summary>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wiwei FYI this is a breaking change technically, since anybody implementing the MRDiagnosticsSystem would now need to implement these two properties. I think it's fine, but we should add it to the release notes.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch, thank you Julia!

@keveleigh keveleigh merged commit 06738fb into microsoft:mrtk_development May 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants