[gingerbread]

@aldostools

I notice that "CheatsDB_BSD_Version.txt" is not in windows format.

If you could include this .reg files in your installer will be great. And also create a shortcut in start menu under "Bruteforce Save Data\Restore Settings" during installing, would be convenient.

http://rghost.net/44211691

Thanks Aldo!!

[aldostools]

Originally Posted by gingerbread Startup load time is greatly improved! Thanks Aldo! I notice some bugs. 1. When you start BSD the 2nd time, the YES in the cheat column are missing. 2. When you start BSD the 2nd time, when you click XXX [Blank], it becomes Blank. 3. Sometimes, right-click takes very long to appear. Will it be possible to add, "Open Patch File" on save that has YES on Cheats. It will fire up the default text editor with the patch file. Thanks Aldo.

The issues 1 & 2 should be fixed on build 3.4.7

The issue 3 could be some memory lag/swap on your Windows... it's working fast here.

"Open Patch File" option was added to the context menu:
- If the save item does not have a ps3savepatch file, the option is not available.
- If the save has a ps3savepatch, and it is decrypted or UNPROTECTED, it shows the list of cheats
- If it is encrypted, it opens the cheats in the internal editor
- If you select "Open Patch File" holding Shift key, it opens the cheats in the default text editor.

Originally Posted by gingerbread @aldostools I notice that "CheatsDB_BSD_Version.txt" is not in windows format. If you could include this .reg files in your installer will be great. And also create a shortcut in start menu under "Bruteforce Save Data\Restore Settings" during installing, would be convenient. http://rghost.net/44211691 Thanks Aldo!!

The "CheatsDB_BSD_Version.txt" was not in Windows format because your .gitattributes is missing this line: *.md text eol=crlf

I don't think it is necessary to include these .reg files...
There is now a new option to restore the column settings
The recent path can be reset to defaults if you start the program holding Ctrl
The other .reg would delete all the other settings (they can be configured from the program) or the user can use your files or delete the keys using regedit.

The installer for 3.4.7 includes the cheats set version 0.15

@gingerbread
I have updated again the build 3.4.7 with some minor changes in the Patch Engine:
- If the label contains the text (required), the patch is checked by default
- New tags at the begining of the label:
group: -> the labels of patches that follow this label are grouped as child
default: -> the patch is checked by default
yellow: -> the label is displayed with yellow background. Other available colors are:
cyan:
blue:
green:
red:
orange:
gray:

Example:

[group:orange:Group #1]
[default:Cheat 1]
00000000 00000000

[red:info:Cheat below does not work]

[Cheat 2 (partial working)]
00000000 00000000

[Cheat 3 (not working)]
00000000 00000000

[gingerbread]

@aldostools I had some sync error on github. I had to create a new repo.

I hope you can update the app to make relevant changes.

New repo

https://github.com/gingerbread-ps3hax/CheatsDB-For-BSD

[aldostools]

Originally Posted by gingerbread @aldostools I had some sync error on github. I had to create a new repo. I hope you can update the app to make relevant changes. New repo https://github.com/gingerbread-ps3hax/CheatsDB-For-BSD

not nice

updated the program with the new link to this repo...

[gingerbread]

Originally Posted by aldostools not nice updated the program with the new link to this repo...

Sorry about it!!

[gingerbread]

@aldostools

PROTOTYPE 2 has a dependency file CRC.BIN

Could I use the method that you used on GoldenEye 007?

Would this be correct?

[Max Evolution]
200017C4 00269AD0
set [crc32]:crc32


; dependency: CRC.BIN
:BLUS30756-DATA-*\CRC.BIN
[Update CRC32 on CRC.BIN (required)]
write at 0x18:[crc32]

[aldostools]

Originally Posted by gingerbread @aldostools PROTOTYPE 2 has a dependency file CRC.BIN Could I use the method that you used on GoldenEye 007? Would this be correct? [Max Evolution] 200017C4 00269AD0 set [crc32]:crc32 ; dependency: CRC.BIN :BLUS30756-DATA-*\CRC.BIN [Update CRC32 on CRC.BIN (required)] write at 0x18:[crc32]

I don't have a save for PROTOTYPE 2 to confirm, but if the CRC32 of the data file (that you don't list in the code) is found at offset 0x0018 in the CRC.BIN file, then it should be correct.

The line "set [crc32]:crc32" calculates the crc32 of the current file and stores it in the temporary variable [crc32].

Then, "write at 0x18:[crc32]" writes the content of the variable [crc32] at the offset 0x18.

[gingerbread]

Originally Posted by aldostools I don't have a save for PROTOTYPE 2 to confirm, but if the CRC32 of the data file (that you don't list in the code) is found at offset 0x0018 in the CRC.BIN file, then it should be correct. The line "set [crc32]:crc32" calculates the crc32 of the current file and stores it in the temporary variable [crc32]. Then, "write at 0x18:[crc32]" writes the content of the variable [crc32] at the offset 0x18.

If it not stored at offset 0x18? How do find the offset? Is crc always 32? Is there a tool?

Once I have found it, do I need to add "set [crc32]:crc32" at every last line of the cheats?

Thanks Aldo!

[aldostools]

Originally Posted by gingerbread If it not stored at offset 0x18? How do find the offset? Is crc always 32? Is there a tool? Once I have found it, do I need to add "set [crc32]:crc32" at every last line of the cheats? Thanks Aldo!

crc32 is a type of hash. BSD supports: crc16, crc32, md5, md4, md2 and sha1

I don't know if it is always stored in offset 0x18 for all games... but it's very probably that not.

To find the offset, you must decrypt the original files, calculate the crc32 of the data file (you can use my PS3 Game Integrity, HashTab, Winrar, etc). Then search for these bytes in the dependency file with a hex editor to find the offset.

The "set [variable]:crc32" usually goes at the end of the patches.

[gingerbread]

Originally Posted by aldostools crc32 is a type of hash. BSD supports: crc16, crc32, md5, md4, md2 and sha1 I don't know if it is always stored in offset 0x18 for all games... but it's very probably that not. To find the offset, you must decrypt the original files, calculate the crc32 of the data file (you can use my PS3 Game Integrity, HashTab, Winrar, etc). Then search for these bytes in the dependency file with a hex editor to find the offset. The "set [variable]:crc32" usually goes at the end of the patches.

Thanks for the information. Using you guide, I manage to find the offset in goldeneye's save file using the dependency file's crc value.

But using that same method, it tried on PROTOTYPE 2. I was unable to find the offset.

This are values of crc.bin after decryption.

CRC32: 7CAE22BB
MD5: 8C64E68601F1493941DCE23675D24103
SHA-1: 2C9BF55F67946D78783233EC605F5CC9BCDBD571

I opened USERDATA.BIN (decrypted) in hex editor, but I was unable to locate any of those values.