Thanks to menu found by
@3141card you can easy test it. So if any game black screen, and PS menu is still able to show, then you can try enable Force Flip Field. Easy, but require game for test.
Ok, so it was lottery (no offense), my question was if you imagined this could work based in the kind of crash the game had... but im guessing it was not doing anything special that could be used as a hint... just at black screen when starting it
I was also wodering what means the sentence "force flip field"... the keyword is "field" but is something so generic that i cant imagine it XD
So is flipping a field (that could contain anything) by force... that means nothing for me, lol
But well... we know now that sometimes can be used to fix blackscreen games
Lets jump here:
52E6E4 ???????? <--- same value in CONFIG file ---> offset in game elf file
034144 ???????? <--- converted to 3, wtf ? ---> Offset in gx_emu where TRUE command/function is.
52E868 ???????? <--- same value in CONFIG file ---> offset in game elf file
034068 ???????? <--- converted to 2, wtf ? ---> Offset in gx_emu where TRUE command/function is.
Problem with "Offset in gx_emu where TRUE command/function is." is that you don't get command number/label there, but raw emulator function in PPC. In netemu exist kind of table with 0x1 commands, in gxemu not ,or I missed it. To be honest I didn't messed with this too long.
How can I make proper config then? Until your nickname isn't mysis, you can only compare functions in disassembler to translate functions between gx, and net emu. But even then is much easier if you have access to mentioned earlier table (which i don't have, and which mysis probably have
).
Ok, so the first value is an offset from an .elf you know if is always the main elf of the game ?
Or is posible to use the command with other elf ?
And the second value is an offset of the emu.self, right ?... where is located some code that is the responsible of making the hook ?
I was looking at this mostly to get an overview of it to continue adding details (and to use accurate names) in the table in PS2 emulation talk page in wiki, by now is ok for me about this command, i moved around to study others
But btw, when i was looking at the second value of netemu command 0x1 i was noticing all that values was close to each other and was low, so i was thinking it was
relative offsets (relative to the start offset of XXXXXXX area), and after reading your explain im thinking the same
The XXXXXXX area should be like a table containing all them, or some important point in the .self
@sandungas I made table here:
http://www.psdevwiki.com/ps3/Talk:P...mu_commands_compared_to_ps2_netemu_0x01_table
Feel free to rename/upgrade/better wikify it if needed. I try to fill it with data tomorrow after work. With this table you can translate offset to command, from gx_emu to netemu.
Is going to be specific for that .self from 4.81 though... but we dont have anything like that so it can be useful
I think is not posible to add it to the table i was doing because this is info specific about the internal structure of gxemu... and my new table represents all the other emus too so is a bit more generic
All kind of info is useful at this point, your idea can be made for the other .self from other firmwares, yeah this is insane but can be used by apps to automatize the extraction and conversion of the config files from the .self
But this is not enought to automatize it, there are other commands that needs more additional info, i dont have a good overview of all them though so im just braistorming and im not sure if is going to be posible to automatize everything, how hard is going to be, or if it makes sense to waste time in doing this for netemu command 0x1... because for sure there are going to be other commands that are going to be problematic to "port" to netemu
I though is for netemu. Anyway. Can anyone confirm working PS2 configs on ISO file with cobra 7.52 or higher? I can't test right now by myself.
