Forums | NoesisGUI

Hi,

I'm profiling a NoesisGUI UI in a game targeting 60 FPS (16.67 ms/frame).

With a simple UI, CPU frame time is around 8–10 ms. When I enable about 100–120 property updates per frame, several bindings, and a few Storyboards, frame time increases to around 13–15 ms.

I'm trying to determine whether the extra cost mainly comes from:

Binding updates
Layout/Measure/Arrange
Animations
Rendering

Is there a recommended NoesisGUI profiling method or diagnostic tool to identify which UI element or operation is responsible for the additional frame time?

Any practical profiling tips would be appreciated. Thanks!

Is this in the C++ SDK? Have you connected the Inspector to first see the View performance numbers (update and render)? The View also provides these numbers via API.

What performance are you getting with our samples?