Jump to content
IGNORED

Altirra Profiler


Recommended Posts

Can someone advice me how I can figure out exactly

 

1) what routines consumes how much cycles per 1 VBL

2) consumtation per defined time frame

 

right now I am doing a stop "jmp *" and then look into the profiler (function graph fex) but devide the cycles by the calls

 

the simple "INC FPS" per VBL is not granular enough when doing highend optimisations of core routines which take several VBLs.

 

or more simple... cycle counting per 1 run of a subroutine :D is needed... but not manually.

 

 

Link to comment
Share on other sites

ok... piece of cake:

 

break point 1 prior entering the routine, break point 2 at the end of the routine... now start once... stopped into debugger... setting cursor the breakpoint in the history window. right click and set to cycle counting, reset time stamp to 0. continue code... altirra stops at breakpoint 2... and hopefully history shows sum of cycles spend.

 

break points of course set in WUDSN ide directly in source code ;)

Edited by Heaven/TQA
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...