Control Rig Doesn't Output Named Events to Insights

Development Character & Animation
, ,
1

I’ve been trying to get performance metrics from Control Rig in cooked builds, but the rig units don’t show up in insights captures regardless of capture channel. I’ve also done diligence to adjust the ControlRigDefines.h to:

//#define DECLARE_SCOPE_HIERARCHICAL_COUNTER_RIGUNIT()

#define DECLARE_SCOPE_HIERARCHICAL_COUNTER_RIGUNIT() \

DECLARE_SCOPE_HIERARCHICAL_COUNTER_FUNC()

That way there’s something emitted on the counter side, but I’m still seeing a lot of untracked time. [Image Removed]

Am I missing a silly step somewhere so I can see an on-kit breakdown of what’s going down in control rig?

Best,

Tyler

[Attachment Removed]

2

Steps to Reproduce

  • Overlay and run against cooked content -basedir and -statnamedevents
  • Load up a scene with a character using a control rig
  • Open unrealinsights.exe, establish conection with the channels: default, animation
  • Stop capture from the game with the console command Trace.Stop
  • Inspect worker threads for control rig usage
    [Attachment Removed]
3

Hi, unfortunately control rig doesn’t have any hooks into regular insights profiling. Adding support for this has been discussed by the team a few times in the past, but it hasn’t been implemented so far. Instead, control rig has its own profiling system that’s available within the control rig editor. You should be able to connect to a running instance of the control rig as you would normally to debug the pose, then in Class Settings, enable “Enable Profiling”. At that point, the graph should display extra debug data, including a rough execution time for tracked rig units, along with a colour-coding system for the graph to show you the most expensive nodes.

[Image Removed]The DECLARE_SCOPE_HIERARCHICAL_COUNTER_RIGUNIT macro that you noticed was used previously as part of the old stat profiling system (there was/still is a ‘stat controlrig’ cvar), but that system was removed back when the in-editor profiling system was added, so I don’t think re-enabling the macro as you mentioned will actually give you any extra data.

[Attachment Removed]

4

No problem, I’ll close out this thread

[Attachment Removed]

5

Thanks for the info, Euan!

[Attachment Removed]