View previous topic :: View next topic |
Author |
Message |
justa_dude Grandmaster Cheater Reputation: 23
Joined: 29 Jun 2010 Posts: 891
|
Posted: Fri Nov 22, 2013 9:43 pm Post subject: Is there a trick to aobs in 64-bit? |
|
|
Hi guys,
I just picked up Van Helsing on sale, so I was looking at fixing up Recifense's table for the latest version. While updating the aob scans, though, I found some odd behavior. I usually double-check my aobs for correctness and uniqueness by doing a search in the memory viewer, search->find memory->(Array of byte)->From 0, etc. For some reason, in this case, I couldn't find any matches - this when searching for strings taken directly from the byte hex strings copied and pasted from the same address in the bottom half of the screen. Confused, I tried searching in the main interface for value type array of byte - again, using the data copied and pasted directly from the memory viewer. Again, no joy. For kicks and giggles, I tried making a simple script that sets a symbol at the aob address, and it did in fact work. So, what do I need to do to get my other searches to work? Has anyone else had this issue?
Thanks,
JD
|
|
Back to top |
|
|
++METHOS I post too much Reputation: 92
Joined: 29 Oct 2010 Posts: 4197
|
Posted: Fri Nov 22, 2013 10:46 pm Post subject: |
|
|
Did you try unchecking the 'writable' box?
|
|
Back to top |
|
|
Gniarf Grandmaster Cheater Supreme Reputation: 43
Joined: 12 Mar 2012 Posts: 1285
|
Posted: Fri Nov 22, 2013 10:51 pm Post subject: Re: Is there a trick to aobs in 64-bit? |
|
|
justa_dude wrote: | Confused, I tried searching in the main interface for value type array of byte - again, using the data copied and pasted directly from the memory viewer. | You have 3 checkboxes on the main UI that read "Writable", "Executable", and "CopyOnWrite", were they all ticked into GREY state? If not it's normal that you didn't find a code aob, right click on any of those checkboxes->preset: scan all memory, and the scanner should find your aob.
Other than that, make sure you're using the 64 bit version of ce to hack your x64 game. (Still, I don't see why a x86 aobscan would find something that the x86 scanner couldn't...)
The last possible thing I see is that your settings in main UI->settings->scan settings prevent the regular scanner from finding your aob.
_________________
DO NOT PM me if you want help on making/fixing/using a hack. |
|
Back to top |
|
|
justa_dude Grandmaster Cheater Reputation: 23
Joined: 29 Jun 2010 Posts: 891
|
Posted: Fri Nov 22, 2013 10:53 pm Post subject: |
|
|
++METHOS wrote: | Did you try unchecking the 'writable' box? |
Wow, good tip! Thank you. It never crossed my mind - I'll have to check next time I'm working in a 32-bit app, 'cause I don't remember ever having to mess with that before. How about for the "find memory" function in the disassembly window? It doesn't have any such options - what needs to happen to make it work?
Thanks,
JD
|
|
Back to top |
|
|
++METHOS I post too much Reputation: 92
Joined: 29 Oct 2010 Posts: 4197
|
Posted: Sun Nov 24, 2013 2:44 am Post subject: |
|
|
justa_dude wrote: | How about for the "find memory" function in the disassembly window? It doesn't have any such options - what needs to happen to make it work? | -I always use the main scanner for AOB searching. I do not believe such added options are available for the memory finder option - DB can verify.
|
|
Back to top |
|
|
|