I'll have a look at building the jump comments for omae.BOOSTEDEVERYTHING wrote: ↑2024 Mar 28, 08:47Yes, Very useful.. I wish I could build them as fast as you can. I still have trouble spotting the loops in the code most times. I also still have issues following along with exactly where the code goes and where exactly it comes back to. But I am getting the hang of it. I wish it would have exact addresses (or line numbers) listed for where to go next so it was easier to go back and forth to follow along.Yeah, not so much as a comparison source for OMAE, just asking if it were useful for RZASA alone.
Use the one I just posted. Your old one has too many gemlins introduced. Paste stuff into the new in small blocks, run it too prove it, repeat.I will check out the new DIR file today and compare and see how I can improve upon my other DIR file. Do most of the addresses I found for the SYM commands in the old DIR file still hold true, or do I need to start from scratch with those?
Mostly from the strategy documents. Sometimes from other disasseblies.BOOSTEDEVERYTHING wrote: ↑2024 Mar 28, 08:54Another question I have is, Where exactly are the function names, table names, etc, that everyone uses as standard coming from? Do they come from the eec documents or a specific code that was disassembled in the past?sym 12364 "uuwFn072A_Perload>Row" # Row Scaler
FUN 12364 1237F :UW V32768 :UW V16
East Coast, UTC+10.My other question is a bit off topic, It says Australia in your bio but doesn't say where? I was wondering what time zone you are in? Just curious I guess.
As per the new dir I posted, use it, add to it.Also, I have tried adding a sym for table names or subroutines names but it gives me duplicate command errors at times. Is there a certain format to which I need to stick to when doing separate entries for these? And do I keep the SYM with the Func command or in the SYM list?
Thanks again for all the help.
The examples in the new dir show the required format.
Payload, scalars functions and tables end in different locations in a definition file, so it pays to organise the dir accordingly. I keep the associated sym and fun together.
How about flashing neon lights, lol.BOOSTEDEVERYTHING wrote: ↑2024 Mar 28, 13:30 Also....I added the bank start sym commands to help find the start of the banks easier for me, But is there a way to put something grander ( not even sure that is a word) in the dir file to make the start of banks even easier to see while quickly scrolling through the code? I know the addresses are prefixed with bank numbers, but something the stop at while quickly scrolling would be nice to have. Beginner problems, right?!?!? LOL
Use the comment file to add some ascii art.
Code: Select all
###### ###
# # ## # # # # # #
# # # # ## # # # # #
###### # # # # # #### # #
# # ###### # # # # # # #
# # # # # ## # # # #
###### # # # # # # ###