How do we identify events with the API Calls window?
There’s only numbers in the arguments for the calls.
I don’t think that’s possible, but that would be handy…
Navigation of the API log is not super easy, you might need to navigate into the [project]\Metadata\ProfilerSession folder and look at the .txt capture in a text editor.
The first argument to the EventInstance functions is its ID, to match that ID back to the EventDescription GUID look for the first instance of that ID in the log, it should be a EventDescription::createInstance call, where the ID is the second argument. The first argument to that call is the EventDescription ID. Same process, find the first instance of that ID, it should be a Bank::getEventListItem call with the ID as the last argument. The first argument is the Event guid which you can copy and paste into the event browser to find the event in question.
I hadn’t considered it before, but having the IDs as hyperlinks that jump to their respective editor, i.e. EventInstance IDs jump to the event browser, BusInstances jump to the mixer could be a pretty nice feature.
2 Likes
Hello,
I had to use recently the API log and it would be great if, next to the ids, the name of the event or bus could be added and also it would be a good information to add, the call origin: if the call was made internaly (from an event command or virtualization manager) or with the API from game code.
We do have plans for making the API view richer but nothing immediately scheduled.
As for your comment about command instruments and the like, the API capture only includes commands issued by the game, not internal commands such as command instruments. It’s our public API that does the capturing and all internal operations do not use that, hence they aren’t recorded.