Where to get PS2CC?

[Lazy Bastard]

Yes, but if the source provided for the entire project doesn't compile for most people, that won't help.

I suppose I'm just single-minded sometimes, and don't like to move on to other things before finishing the current one. I could simply update the compiled binaries in advance. I had intended to do some testing before I did so (so I could give a proper block of instructions to users), and I didn't get to do that last night. Perhaps tonight.

[Lazy Bastard]

I went ahead and updated the Artemis BountySource Download page. Worst case, if people can't figure out how to use the latest binaries, they can fall back on the old "Hacking System Package". I'll get around to doing testing and documentation later...

[LiquidManZero]

It seems ps2cc will work fine... If you screw with it enough. At least on my setup it refuses to connect to the ps2 if the console's IP is anything but 192.168.0.80.

[bungholio]

I tried PS2CC and it works. The problem I had was that those search options for values wouldn't let me set values. I would set a first low value, I would put a number in, and after that nothing would set it and neither would ENTER. I clicked out of the number box, and it always reset to 0. I also didn't know, but every game needs that "PS2 Waits" box checked or it never works. That last window to the right of SEARCH and RESULTS caused PS2CC to crash and windows shut it down with an error report.

[kh2k4]

Type the value and hit Enter. Clicking off the box or hitting Esc is seen as canceling.

...

[bungholio]

My ENTER key isn't broken, but it isn't setting the value either. I was wondering if the stuff on the right side in the "Results" tab was specifically for entering you own codes while playing. If it is, I couldn't figure it out with Fatal Frame 3. I put in the first line for the entire ghost list code, set to 32 bits, and set the check box so it was on. No effect.

[bungholio]

There's a simple thing that needs to be changed in PS2CC, even though you already have it on the list of "things to do". The scans should only dump the addresses of results that you still have. It's odd dumping 31MB of game data just to check 2 addresses when it would save time to just dump those 2 addresses' results.

[misfire]

Yes, that should be obvious. I can remember that the GSCC only dumped all memory from the lowest possible address to the highest.

[bungholio]

I managed to check the memory editor after I set whether it would show 1, 2, or 4 bytes.

The scan options to "remove if within range" and "remove if not within range" don't work. For value 1 and 2, I put "00000000" and "FFFFFFFF", and then switched them around to "FFFFFFFF" and "00000000". I did an initial scan, and then after any of those 2 scans with any value, I always had 0 results after I scanned.

After that I immediately looked for a sort of search type that looked for results that were less than or greater than a certain value. There was neither, but that wouldn't matter if those 2 range scans get fixed.

[misfire]

There's a simple thing that needs to be changed in PS2CC, even though you already have it on the list of "things to do". The scans should only dump the addresses of results that you still have. It's odd dumping 31MB of game data just to check 2 addresses when it would save time to just dump those 2 addresses' results.

Viper, if you have the time, you should seriously consider implementing this. It'd be great if ps2cc only dumped all memory from the lowest possible address to the highest.