Don't be hasty to start your own mod; all our FFT modding projects are greatly understaffed. Find out how you can help in the Recruitment section.
Started by nitwit, September 11, 2014, 01:30:22 am
Quote from: pSX_AuthorBreakpoints also support condition expressions (eg. r2==0x123456), these also support a few functions like read_long(..addr...) but I haven't documented them anywhere.
Right-click in Breakpoints -> Add -> Breakpoint pop-up menuBreakpoint Address (enter a number, use 0x prefix to denote hex) Execute (checkbox) Memory (checkbox) Read (checkbox) Write (checkbox) Size Condition (Definitely need some examples on this, only one I see is r2==0x123456. I need examples of the syntax as well as known commands it supports) Count
Right-click in Breakpoints -> Add -> DMA pop-up menuDMA Type (MDEC in, MDEC out, GPU in, GPU out, CDROM, SPU in, SPU out, ClearOTagr) Address range (checkbox, no name) Address (enter number) Size (enter number) Condition Count
Quote from: ChotoAn Execute breakpoint will freeze the game if code execution reaches a certain command. So if I set a breakpoint on 0x18b43c, code will stop at the first command of the pre-formula routine.
QuoteI added my condition read_long(0x1C7138)==0x0
QuoteBreakpoints: ok in debugging, breakpoints are specific "rules" where when the rules are met, the CPU stops what it's doing (otherwise known as breaking, hence the term "breakpoint"). For example, I could have it to where whenever a certain value in memory is read by the code in the game (which will be explained in a bit), it'll stop it whenever it does. Also, I can add extra rules, called "conditions" to further refine the breakpoint. So lets say I want it to break when a certain place in memory is read but ONLY when another memory location equals x value, I can do that too. I can also alter the count which is how many times should the rules be "triggered" before actually breaking. Breakpoints are essential for finding algorithms in the game.
Page created in 0.044 seconds with 26 queries.