Why are there a bunch of different hooks in gecko os? I only use the one it was preset on.(I think VBI) Any advantages from changing.
they will trigger a different number of times per main loop and will trigger at different points in that loop. so using one could cause it to trigger after an event has happened and another could trigger before an event has happened. some also just aren't found in different versions of the sdk due to changes in the code
So does it matter which one I use?
It matters which game you´re trying to hack.
Mostly, VBI hook will work. Sometimes, it won´t.
Then you want to use Ossleepthread. But games that work with VBI mostly don´t like Ossleepthread (freezing issues).
You only need these two hooks to hack any game (I know of).
That´s all you need to know, basically.
Quote from: toonlink444 on March 29, 2012, 08:51:26 PM
Why are there a bunch of different hooks in gecko os? I only use the one it was preset on.(I think VBI) Any advantages from changing.
As megazig said, some hooks will occur before certain events, while other hooks will be after them. As an example, GeckoTunnel requires the PadRead hook, because it writes to the players' pad data, and if you use the VBlank hook, the game will overwrite the pad data before reading it. In general, if you find that a game is overwriting a value when you try to poke it, changing hook types has a chance of helping. (Or you could use a C2 code, which is more likely to solve the issue.)
yep, very sometimes a codehandler ram write/poke won´t succeed at all. The game´s write overwrites the codehandlers write before the hacked value can take effect. We then need ASM to make it work. It COULD be unfortunate if we were on the right path, but gave up because our pokes didn´t do anything. Trying to find codes with different hooks may be annoying. Maybe there´s a way to never have our pokes/writes overwriten (because of a bad hook spot in the loop). I remember some codes which I never succeeded to find for specific games only, maybe that´s why?