I've seen the OSG profiler (F3), but it seems to me that it offers very little details about what's happening in the frame, unless I missed something
From what I've seen, it gives only a few categories, no info about threads, no user markers, no calls tack, and it's not possible to pause it to zoom/inspect. If I'm wrong please tell me.
How about integrating something like Tracy?
You can add a marker in the profiler with a simple macro, you can save a capture, see callstacks, and much more. It's great to investigate performance problems.
Everything about development and the OpenMW source code.
2 posts • Page 1 of 1