(09-19-2014, 09:26 PM)Blyss Sarania Wrote: [ -> ]vsub and tadatada are the resident forum cheat code/patch Gods.
I'm a bit embarrassed. I admit that I know many things about cheating, but I've learnt many things from vsub in this forum.
Hi!
So I'm running into a little bit of a problem. I keep searching for and can't find the crc code anywhere, nor the name the emulator sees from the game, so i can't seem to get the pnach in working order. The game itself runs perfectly. This is my emulog:
PCSX2 1.2.1.r5873 - compiled on Feb 3 2014
Savestate version: 0x9a0a0000
Host Machine Init:
Operating System = Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
Physical RAM = 16280 MB
CPU name = AMD FX™-9370 Eight-Core Processor
Vendor/Model = AuthenticAMD (stepping 00)
CPU speed = 4.413 ghz (8 logical threads)
x86PType = Standard OEM
x86Flags = 178bfbxx 3e9832xx
x86EFlags = 2fd3fbxx
x86 Features Detected:
MMX.. SSE.. SSE2.. SSE3.. SSSE3.. SSE4.1.. SSE4.2.. AVX.. FMA
MMX2 .. SSE4a
Reserving memory for recompilers...
Loading plugins...
Binding GS: C:\Program Files (x86)\Ps2 emulator\Plugins\gsdx32-sse4-r5875.dll
Windows 6.1.7601 (Service Pack 1 1.0)
Binding PAD: C:\Program Files (x86)\Ps2 emulator\Plugins\lilypad-r5875.dll
Binding SPU2: C:\Program Files (x86)\Ps2 emulator\Plugins\spu2-x-r5875.dll
Binding CDVD: C:\Program Files (x86)\Ps2 emulator\Plugins\cdvdGigaherz.dll
Binding USB: C:\Program Files (x86)\Ps2 emulator\Plugins\USBnull.dll
Binding FW: C:\Program Files (x86)\Ps2 emulator\Plugins\FWnull.dll
(GameDB) 9655 games on record (loaded in 181ms)
Binding DEV9: C:\Program Files (x86)\Ps2 emulator\Plugins\DEV9null.dll
Plugins loaded successfully.
HLE Notice: ELF does not have a path.
Initializing plugins...
Init GS
Windows 6.1.7601 (Service Pack 1 1.0)
Init PAD
Init SPU2
Init CDVD
Init USB
Init FW
Init DEV9
Plugins initialized successfully.
Opening plugins...
Opening GS
Opening PAD
Opening SPU2
* SPU2-X: Enumerating PortAudio devices:
*** Device 0: 'Primary Sound Driver' (Windows DirectSound)
*** Device 1: '1 - SAMSUNG (2- AMD High Definition Audio Device)' (Windows DirectSound)
*** Device 2: 'Audio digital (S/PDIF) (Dispositivo de High Definition Audio)' (Windows DirectSound)
*** Device 3: 'Audio digital (S/PDIF) (Dispositivo de High Definition Audio)' (Windows DirectSound)
*** Device 4: 'Audio digital (S/PDIF) (Dispositivo de High Definition Audio)' (Windows WASAPI)
*** Device 5: 'Audio digital (S/PDIF) (Dispositivo de High Definition Audio)' (Windows WASAPI)
*** Device 6: '1 - SAMSUNG (2- AMD High Definition Audio Device)' (Windows WASAPI)
*** Device 7: 'Output (AMD HD Audio HDMI out #0)' (Windows WDM-KS)
*** Device 8: 'SPDIF Out (Salida de SPDIF de HD Audio 5)' (Windows WDM-KS)
*** Device 9: 'SPDIF Out (Salida de SPDIF de HD Audio)' (Windows WDM-KS)
Opening CDVD
isoFile open ok: C:\Users\Administrador\Documents\PCSX2\- isos\Xxxx Xxxxxx Xxxxxx - Xxxxxxx 4 (USA).iso
Image type = DVD
* CDVD Disk Open: DVD, Single layer or unknown:
* * Track 1: Data (Mode 1) (2151344 sectors)
Opening USB
Opening FW
Opening DEV9
McdSlot 0: C:\Users\Administrador\Documents\PCSX2\memcards\Mcd001.ps2
McdSlot 1: C:\Users\Administrador\Documents\PCSX2\memcards\Mcd002.ps2
Plugins opened successfully.
EE/iR5900-32 Recompiler Reset
Bios Found: USA v01.60(19/03/2002) Console
BIOS rom1 module not found, skipping...
BIOS rom2 module not found, skipping...
BIOS erom module not found, skipping...
(UpdateVSyncRate) Mode Changed to NTSC.
(UpdateVSyncRate) FPS Limit Changed : 59.94 fps
Closing plugins...
Closing DEV9
Closing FW
Closing USB
Closing CDVD
Closing SPU2
Closing PAD
Closing GS
Plugins closed successfully.
Not sure if this post is for this thread but if all else fails,open the disk\image(with whatever you have(7zip\WinRar also work if you don't have anything that can open iso),start pcsx2 and drag drop the file from the disk\image that looks like this S***_***.** to the pcsx2 main window
In the console pcsx2 is supposed to show the crc
PS.If you are going to use 7zip\WinRar,I prefer to extract the file somewhere rather than making the program to extract it to the Temp folder and pcsx2 to run it from there.
Cheat Problem Guide has been updated.
Code:
Date Description
Oct. 6, 2014 Fixed incorrect 9-digit CRC to 8-digit one.
Added an annotation regarding the Cheats= key in inis/PCSX2_ui.ini in section (2-6).
Added chapter 6. Update history.
The web, Word and PDF versions of this guide were updated by tadatada.
P.S.
Just FYI. I've proposed a new feature below:
If any cheats file is not found, the "Not found Cheats file" message will appear with its full path of the cheats file on the log screen.
[attachment=52671]
This message would help to solve some frequent cheating related questions like "Cheat doesn't work."
Cheats: Added a cheats related log, changed color of a few positive logs. #326
https://github.com/PCSX2/pcsx2/pull/326
Cheat Problem Guide has been updated.
Code:
Date Description
Oct. 17, 2014 Added chapter 6. Type D and E codes.
Is the first time I see that thread. If I understood the guide's purpose I'd propose it's name to be "Cheat Troubleshot Guide", just for the sake of cleanness.
Thanks. How about "Cheat Troubleshooting Guide"?
I've googled "Troubleshot Guide" and "Troubleshooting Guide". A number of results of the latter is greater than of the former.
(10-17-2014, 03:58 PM)tadatada Wrote: [ -> ]Thanks. How about "Cheat Troubleshooting Guide"?
I've googled "Troubleshot Guide" and "Troubleshooting Guide". A number of results of the latter is greater than of the former.
Indeed, troubleshooting sounds good, let's hope an English native speaker to have the say. Actually "Cheat Problems Troubleshooting Guide" looks OK also.
The final name choice is yours
Edit: sorry for the bad misspelling, the name change was proposed for the sake of clearness and not cleanness as stated.
I think that the name "Cheat Problems Troubleshooting Guide" is precisely described its purposes of this guide. I've decided to it and I'll fix to it later.
Cheat Problems Troubleshooting Guide has been updated.
Code:
Date Description
Oct. 18, 2014 Changed the title of this guide from "Cheat Problem Guide" to
"Cheat Problems Troubleshooting Guide."
Rewrote the PDF version of this guide.