PSX 9999 Limit Breaking ?

  • Thread starter Thread starter Cloud7
  • Start date Start date
Status
Not open for further replies.
C

Cloud7

Guest
I already heard of it in a few posts about the PSX version.
There are a few YT videos about it , but nobody answers my questions... :/

Is there really a WORKING 9999 breaking patch ?

The megaupload lidl posted in the climhazard post does not work, neither in english nor in german version.

SO what can you guys tell about that ?

Fact or Fiction ?


PS: I already tried to minimize cut some files out of the image beacause the existing .X files where not the same size as hte original one.
Didnt work.

Yours , Cloud7.
 
Yes, it does exist. Still beta and much bugs. For PC, it works. For PSX, I don't know, really sorry. If you can provide me a good .IMG compiler/decompiler, I believe I could help.
 


Uploaded with ImageShack.us

that's my problem.
I'm using CDmage, the image file is a .img-file + a .ccd file which was
there after compilation.
Before importing the .x files it asks me if I want to fill the spaces with zeros,
tried both possibilities non of them worked.
 
Last edited:
Always fill spaces with zeros. By using ePSXe, I believe there is a possibility to do that, but pretty unsure.
 
Seems like you're using an incorrect version of the game. If the patch is specified to work only with the US build, don't try it on European or other builds because no matter how much zero padding you tell CdMage to add IT WON'T WORK EVEN IN A MILLION TRIES.
 
Last edited:
Cloud7, I think you need to better understand what happens to applications when they're compiled, and how binaries actually work. I think you should do a bit more programming, then wrestle with ASM, looking at the binaries your applications compile to. Until then, I don't think you'll 'get' some of the issues we're talking about, because I don't think you have a clear idea how high-level instructions translate to low-level data. The binary-level instructions in different builds, using different data, will move about quite a lot.

I've heard of PSX 9999 breaker patches. I would just ask the creator which sets of instructions he needed change in the US version, then find the equivalent in the PAL release. Ask him if anything unusual appears on any of the registers whilst the limit is applied, so you can use a debugger to stop the app when that event occurs. Your debugger should stop you right when the code in question is being executed.

Always fill spaces with zeros. By using ePSXe, I believe there is a possibility to do that, but pretty unsure.
Click to expand...
You really shouldn't need to.
 
You are right ,
I want to learn.
But if nobody answers ?...
Tell me what to do, I'll do it.

I have the English version of the Game too...
Tried it , but it did not work for me...
that's quite confusing.

Bosola ?
I already wrote to 3 of those peops, but they didn't answer my question,
they didn't even respond in any way.
Maybe you can help ?

€: I think , first thing I have to do is to know what the files (.x)
actually are (models , cfgs ?)
Then try to open them. and change , blaablabla.
OK, what's this file extension ?
filext.com says that it has multiple usages... -.-' *crap*
Do you guys know something about that ?
 
Last edited:
The .X files? They're binary files that contain executable data, pointer tables and some other... stuff. You shouldn't be thinking of these files as having distinct purposes, like image files or .exes - take the LIMTMENU, for instance, which contains the limit menu code *and* the attack data for each limit. In any case, you should be trying to find the instructions you'll change by running the game with a debugger, finding the instructions in question and only then locating them in the disc's files.

As for learning, here's my advice:

1. Learn to write basic programs in C. Not C++ (yet), just plain ANSI C.
2. Learn to use pointers, manipulate data on the bit-by-bit level and perform arithmetic in hexadecimal.
3. Learn how to compile these programs. Try to use as few libraries as possible. You want as 'self contained' a program as possible for the next step.
4. Learn how to use a debugger on these applications. See what their assembly looks like, and learn to 'hack' them on an ASM level. A tool called a decompiler might help you.
 
I'll learn , or at least begin to learn that stuff, if
it helps me solving those problems :
hurray.
 
Status
Not open for further replies.
Back
Top