Hacking Pointer Searcher

[BullyWiiPlaza]

[...] and does not require to rename the dump file for the next search (it's really helpful to be able to give the file a meaningful name).

I make a folder with a meaningful name and put the .bin files in there. Isn't that good? It is important to keep the destination address saved and it let's you start the search faster then. I also put my thoughts into the design of this

 

[Mr. Mysterio]

does this Version @Mr. Mysterio only allow 1 Deep pointer when it does pointer in pointer?

Yes because anything deeper takes too long.

EDIT: I have also never encountered any codes that require more than two pointers.

 

[Skiller]

Yes because anything deeper takes too long.

EDIT: I have also never encountered any codes that require more than two pointers.

in all the systems i have hacked. i have seen more then 1 a few time, Can you add it as an option to allow of setting the amount of Depth it goes

this would make it so people would not use much Memory unless they change it

 

[Mr. Mysterio]

in all the systems i have hacked. i have seen more then 1 a few time, Can you add it as an option to allow of setting the amount of Depth it goes

this would make it so people would not use much Memory unless they change it

I calculated that it would take about four days to do a three deep pointer search in low memory mode. I would want to spend enough time to thoroughly test that feature, so I'll leave that to BullyWiiPlaza's tool, if it can do it.

 

[BullyWiiPlaza]

so I'll leave that to BullyWiiPlaza's tool, if it can do it.

It can't do it either, yet and I probably won't plan on doing it. It's also more complicated to implement kinda and not very useful overall. But someone should help Skiller out though

 

[CosmoCortney]

@Mr. Mysterio Here's an idea how to speed up your pointer searcher.
I have just noticed that your program calculates pointer codes for values that do not end with 0, 4, 8 or c. Such pointers usually don't appear.
Maybe your program would be faster if you include a value check like:
(sry for the syntax, never programmed in c# before)

if (pointer index[8] = 0 | 4 | 8 | C)
{
rest of your code;
}
else repeat code for next .word;


I think Bully has included something like this into his tool

 

[Skiller]

i think Zombie U is one of the cases of using Deeper Pointers .>>

example
you first have a Pointer to Player
then you have Pointer to weapons/Ammo from inside the Player section ..

 

[CosmoCortney]

@BullyWiiPlaza and @Mr. Mysterio you could maybe add a function to exclude range 0x20000000 - 0x40000000 from the search since there are barely any results. This could speed up the search a lot

 

[Cyan]

ZombiU item location are in 0x24 range. (not the pointers location, but the target addresses)
so keep it, but make it an option maybe ? or let the user edit the range to make shorter dumps/searches.

When I create a memory dump, I do 0x10 to 0x26 to create a ~350MB dump. I just edit the range manually, it's not that difficult.

But adding an option to limit the dump's parsing to a specific range in case the user made a full dump is a good idea to use less ram.

 

[CosmoCortney]

ZombiU item location are in 0x24 range. (not the pointers location, but the target addresses)
so keep it, but make it an option maybe ?

That's what I meant
Well, it won't matter if the actual value we want to modify is in the range to be skipped by the pointer search.
But it really would speed up the search a lot due smaller range to search + shorter loading times

 

[BullyWiiPlaza]

i think Zombie U is one of the cases of using Deeper Pointers .>>

example
you first have a Pointer to Player
then you have Pointer to weapons/Ammo from inside the Player section ..

That is already supported with pointer in pointer searches, isn't it?

@BullyWiiPlaza and @Mr. Mysterio you could maybe add a function to exclude range 0x20000000 - 0x40000000 from the search since there are barely any results. This could speed up the search a lot

How does it matter to wait like 1 minute longer when you already wait about 10 minutes for a single memory dump? In terms of memory usage I can understand so @Mr. Mysterio should add this feature.

 

[CosmoCortney]

That is already supported with pointer in pointer searches, isn't it?

How does it matter to wait like 1 minute longer when you already wait about 10 minutes for a single memory dump? In terms of memory usage I can understand so @Mr. Mysterio should add this feature.

You're right
but maybe for those who don't have an SSD

 

[Mr. Mysterio]

I'm not making any more versions of this. Instead, I'm adding it to Uwizard. However, I will add this feature idea of searching sections of dumps to the new Uwizard version!

 

[Onion_Knight]

One of the simplest things to do when you want to dump faster is to increase the CodeHandlers byte range for each packet sent. By default its only sends every 0x400(1024) of bytes of data. However due to the MSS of a typical Wireless packet, you can get up to 1360 bytes. By just increasing your buffer size to send at to 0x500, you get around a 20% bump in data coming back without increases the number of packets needing to be sent. Granted, you will get a slight increase of data being sent back that is non-zero sized, but I've seen a noticeable drop in time it takes to make a dump. The other thing to really do that is on my list is to use the zlib inside the wiiu to compress the data coming back before sending. There might be a subtantial payoff in data transfer...if you async the decompressing on the PC than it might get you another bump.

 

[Mr. Mysterio]

It would be very fast also if the Wii U could do known value searches and then send back the results. For the first layer at least.

 

[Onion_Knight]

It would be very fast also if the Wii U could do known value searches and then send back the results. For the first layer at least.

It is much faster, I can search the range 0x10000000 - 0x40000000 in about 10 secs for a known value search and return an (unsigned int *) array. It just sometimes crashes my Wii U. I need to scale it back a bit.

 

[Skiller]

That is already supported with pointer in pointer searches, isn't it?

i missed a step ..
Pointer to Current Level > Player > Weapon.

 

[Sam from NL ;)]

Hey thnx for making this awesome tool! i just dont get 1 thing: what do i need to enter here:

in the pointer destination?

 

[Cyan]

we can't see your file as you linked it to your own computer.
You need to host the file online (click "update a File" button below the edit area, or host it on an external website first, like filetrip.net or any other image hosting services)

 

[Sam from NL ;)]

we can't see your file as you linked it to your own computer.
You need to host the file online (click "update a File" button below the edit area, or host it on an external website first, like filetrip.net or any other image hosting services)

http://imgur.com/TYImQKh < what do i need to enter in the ''destination bar''?