PS3 Game Patches

That is data type, be32 is 32bit big endian, be16 is 16bit big endian etc. The first one is 4 bytes long and the other 2 bytes long.
I have been testing this pattern I talked about on b16 data type. And it does not work. I am getting pretty sure that this pattern only works for be32 data type. Does anyone know how to proper rewrite b16 data for the Artemis be able to read it?
 
This looks confusing but it's a big start. Thanks bro, I appreciate it. And this can be done with every game? Or is there a limit? And is this change permanent once you set it? Cause it would be nice if the change stayed even after reboot.
I just figured it out. What he taught you is to do this commands directly from the Webmanmod, on the ps3mapI tab. Than you put the address he gave you and changed the values f8651c60 for 38800001 to do exactly what he is doing through Artemis, you just insert zeros ("0") until the address code have 8 digits. In this case would be 008d2e94 then the value he gave you so Artemis overwrite it for you. 38800001. Final result would be:

Unlock FPS
0
illusion
0 008d2e94 38800001
#

I just figured it all out thanks of the latest comment on this topic, from AndreVinniciosCampos. Many thanks.
So I was able to get Uncharted 2 patch to work on Artemis, since its unlock fps on RPCS3 patches is in be16 data type. And not be32, till now I was only able to apply patches through Artemis when they were be32 data type. there are other types like be16, bef32, byte
and utf8. A friend of mine was able to find a solution for bef32 on the internet somewhere, but I am more focused on be16 and byte data types.

ps: code for Uncharted 2 fps unlock:

Unlock FPS
0
Mitsu (?) (Unknown author)
0 00E9C1FB 00000001
#

Many thanks to the community and developers.
 
Last edited:
All of the listing needs to be tested but shall work because it has the same principles I used for others which worked. The principles are explained on my previous comments.

Alice: Madness Returns BLES01265: [ 01.00 ]

Unlock FPS
0
FlexBy
0 0034cad0 60000000
#

Batman Arkham City GOTY
BLES01587: [ 01.00 ] BLUS30978: [ 01.00 ]

Unlock FPS
0
FlexBy
0 001b1d30 60000000
#

Borderlands 2 BLUS30982: [ 01.15 ] BLES01684: [ 01.15 ] NPUB30898: [ 01.15 ]

Unlock FPS
0
FlexBy
0 001ef34c 60000000
#

I also figured out that you could skip 50% of @zeWaardt way of doing it. By just using the https://rpcs3.net/compatibility website, I look for the game I want, click on it and it will direct you to https://wiki.rpcs3.net/ (/gamenameyouarelookingfor). The patches for the game will be on a tab at the very end of the game specs. Right under special notes or netplay testing in some cases. Click expand.

The patches tab will be there IF that game you are looking for has any patches developed for it. Most games won't have any patches. This way will save you a lot of time, not having to deal with the Emulator at all.
 
Last edited:
That's cool, congratulations. Could you provide more knowledge, brother. How do you know which codes from that site apply to Artemis? For example, how do you know which address to go to and which numbers to modify based on the patch information? because where you mentioned there are so many numbers and codes that it gets confusing. could you give us an example gmanarte
 
In our RSX overclocking experiments, @Mitsu™ found some videos showcasing 60 FPS Patches for RPCS3 working on a real console.

As you can see in this video:

.

Additionally @zeWaardt, made a video about how to use the patches on the real ps3


Subsequently, @NunoRS2000 generously shared a patch for two popular titles:

1. The Last of Us (version 1.11):

  • Search for 1571A6F and modify the byte from 02 (30fps) to either 01 (60fps) or 00 (unlocked).

2. Uncharted 2 (version 1.09):
  • Search for E9C1FB and modify the byte from 02 (30fps) to 01 (60fps) or 00 (unlocked).


If anyone else is aware of additional game patches or modifications, please share it.
If anyone is interested, I can make it work in the DLC The Last of Us Left Behind. and just put the code below through Artemis:


The last of us: Left behind.
0
Unlock
0 00039d1c 38a00000
#
 
In our RSX Overclocking Experiment's , @Mitsu™ found some videos showcasing 60 FPS Patches for RPCS3 working on a real console.

1. The Last of Us (version 1.11):

  • Search for 1571A6F and modify the byte from 02 (30fps) to either 01 (60fps) or 00 (unlocked).
    found some videos showcasing 60 FPS Patches for RPCS3 working on a real console.

    Subsequently, @NunoRS2000 generously shared a patch for two popular titles:

    1. The Last of Us (version 1.11):
    • Search for 1571A6F and modify the byte from 02 (30fps) to either 01 (60fps) or 00 (unlocked).
Can you show a picture on how or where to put the code in for the last of us (((BCUS)))
im trying to get a 60fps unlock patch working for tlou i got one working for GTA IV BLES AND BLUS using Artemis

what's the code for 60fps on the last of us BCUS98174 regular game not The DLC
 
@AndreVinniciosCampos
So, the video @zeWaardt posted, he utilizes the RPCS3 itself, to open game patches and look at the codes directly from there. It is not necessary, you can skip it by just going to the RPCS3 wiki website. You type "RPCS3 God of war 3 (name of the game you are looking for)" the first option will be the RPCS3 wiki page. In that web page at the bottom of it, there will be a topic called "patches" on the right side of it there will be a clickable link "expand". Expand it, and the codes will be right there. But remember, not all games have patches discovered to it. Some games you will search for and there won't even be any "patches" topic. For better understanding I will bring one example. The example will be Just Cause 2. Type RPCS3 Just Cause 2 on google. Open the first link wiki,rpcs3,net link. Scroll down pass "Configurations" and "Known issues" till you reach "Special Notes". On these special notes, there is the topic "Patches". Click expand. The first/top info you will get is this

"60 FPS":
Games:
"Just Cause 2":
NPUB30606: [ 01.02 ]
Author: "illusion"
Notes: Patch Version: 1.0
Patch:
- [ be32, 0x004087a8, 0x38600000 ]

"60 FPS" is the name of the patch (what it does.)
NPUB30606 is the game region version it works with
[01.02] means that game version has to be updated to version 1.02
Patch version it is not important, at least not at my understanding...
be32 means it is big endian 32 (till now I was only able to make ps3 patches work [on original console] with be32 data type codes.)
0x004087a8 means the address code is 4087a8
0x38600000 means that the 8 first digits (at 4087a8 address code) will be replaced/overwritten as 38600000

if you have Webman mod installed on your ps3, you can type your ps3 IP on a web browser. Run the game you are planning on apply patches, on your ps3 (in this case Just Cause 2). Then go back to the web browser, and click on PS3 MAPI. You will notice the Ps3MAPI recognized the game running on you ps3. Scroll down till you see "Address Code: _____" . Type 4087a8. At the very bottom of that web site page there will be a bunch of number and letters. Black on white, seeming like a text box. Erase the first 8 digits on that text box and replace it with 38600000. > what you have just done is the same as creating a code

unlock fps
0
illusion
0 004087a8 38600000
#

for Artemis. But doing it directly from Ps3MAPI instead of using Artemis to do it for you.

One thing might get you confused, if you search for The Last of Us, you will notice that the address code they give for fps unlock/60fps is different than 01571A6F. You will notice that they give you different address codes, for game versions 1.00 and 1.11. Different than 01571A6F. Even so, they work. So it is possible to achieve patch results like "Unlock FPS" with different address codes. That is how your comment helped me. Because before that I was thinking the first code after be32, wasn't an address code, since it differs from some codes we already knew of, like this The Last of Us case.

Another useful information is, there are some patches that needs you to change more than one address code and their values to achieve the results you are looking for. They will appear as:
[be32, 0x00bb8c94 , 0x38600001]
[be32, 0x00bb8c98 , 0x4e800020]
this case I am bringing you the "50 Fps" code for Metal Gear Solid 3: Snake Eater - HD Edition
region version: BLUS30847 (it has to be this one)
game version 1.00 (not updated)
translating this to Artemis it is gonna look like this:

50 Fps
0
TriggerHappy
0 00bb8c94 38600001
0 00bb8c98 4e800020
#

Sorry for the late reply, I was on a trip. I hope this is enough for you to understand.

Regards,

@gmanarte
 
Last edited:
@AndreVinniciosCampos
So, the video @zeWaardt posted, he utilizes the RPCS3 itself, to open game patches and look at the codes directly from there. It is not necessary, you can skip it by just going to the RPCS3 wiki website. You type "RPCS3 God of war 3 (name of the game you are looking for)" the first option will be the RPCS3 wiki page. In that web page at the bottom of it, there will be a topic called "patches" on the right side of it there will be a clickable link "expand". Expand it, and the codes will be right there. But remember, not all games have patches discovered to it. Some games you will search for and there won't even be any "patches" topic. For better understanding I will bring one example. The example will be Just Cause 2. Type RPCS3 Just Cause 2 on google. Open the first link wiki,rpcs3,net link. Scroll down pass "Configurations" and "Known issues" till you reach "Special Notes". On these special notes, there is the topic "Patches". Click expand. The first/top info you will get is this

"60 FPS":
Games:
"Just Cause 2":
NPUB30606: [ 01.02 ]
Author: "illusion"
Notes: Patch Version: 1.0
Patch:
- [ be32, 0x004087a8, 0x38600000 ]

"60 FPS" is the name of the patch (what it does.)
NPUB30606 is the game region version it works with
[01.02] means that game version has to be updated to version 1.02
Patch version it is not important, at least not at my understanding...
be32 means it is big endian 32 (till now I was only able to make ps3 patches work [on original console] with be32 data type codes.)
0x004087a8 means the address code is 4087a8
0x38600000 means that the 8 first digits (at 4087a8 address code) will be replaced/overwritten as 38600000

if you have Webman mod installed on your ps3, you can type your ps3 IP on a web browser. Run the game you are planning on apply patches, on your ps3 (in this case Just Cause 2). Than go back to the web browser, and click on PS3 MAPI. You will notice the Ps3MAPI recognized the game running on you ps3. Scroll down till you see "Address Code: _____" . Type 4087a8. At the very bottom of that web site page there will be a bunch of number and letters. Black on white, seeming like a text box. Erase the first 8 digits on that text box and replace it with 38600000. > what you have just done is the same as creating a code

unlock fps
0
gmanarte
0 004087a8 38600000
#

for Artemis. But doing it directly from Ps3MAPI instead of using Artemis to do it for you.

One thing might get you confused, if you search for The Last of Us, you will notice that the address code they give for fps unlock/60fps is different than 01571A6F. You will notice that they give you different address codes, for game versions 1.00 and 1.11. Different than 01571A6F. Even so, they work. So it is possible to achieve patch results like "Unlock FPS" with different address codes. That is how your comment helped me. Because before that I was thinking the first code after be32, wasn't an address code, since it differs from some codes we already knew of, like this The Last of Us case.

Another useful information is, there are some patches that needs you to change more than one address code and their values to achieve the results you are looking for. They will appear as:
[be32, 0x00bb8c94 , 0x38600001]
[be32, 0x00bb8c98 , 0x4e800020]
this case I am bringing you the "Unlock Fps" code for Metal Gear Solid 3: Snake Eater - HD Edition
region version: BLUS30847 (it has to be this one)
game version 1.00 (not updated)
translating this to Artemis it is gonna look like this:

Unlock FPS
0
gmanarte
0 00bb8c94 38600001
0 00bb8c98 4e800020
#

Sorry for the late reply, I was on a trip. I hope this is enough for you to understand.

Regards,

@gmanarte
Most of the patches you copied from RPCS3 wiki and gave no credits for original authors wont work on PS3. They require changing vblank which is not possible on PS3. Also the MGS3 patch is not unlock FPS but 50 FPS, MGS3 runs natively at 60 and Batman Arkham City is a debug menu patch lol.
Its pretty sad to see some users just converting an existing patch to different format and not giving credits to original author.
 
@AndreVinniciosCampos also another thing I
Most of the patches you copied from RPCS3 wiki and gave no credits for original authors wont work on PS3. They require changing vblank which is not possible on PS3. Also the MGS3 patch is not unlock FPS but 50 FPS, MGS3 runs natively at 60 and Batman Arkham City is a debug menu patch lol.
It's pretty sad to see some users just converting an existing patch to different format and not giving credits to original author.

As I previously said some of the patches I brought need further testing. What I am doing is just trying to help some ppl that got here not long ago (just like me) and got no answers and only more questions. Cause it seems like ppl are hiding (not sharing) info. The tutorials are always "do this and do that" not explaining at all what the hell is going on. Like everyone here isn't smart enough to help the scene. I just noticed you were the one who discovered the unlock fps for Batman Arkham City as I went to check if I did a mistake as you pointed out. You are correct I did a mistake as I was writing down plenty of codes as soon as I discovered how it all works.

Even though MGS3 is originally 60 fps, the example I gave was enough for ppl understand what they have to do when they encounter patches that need values changed in more than one address code.

I am a member here since 2021 if I am correct, but I was mainly focused on Ps2 back then. And I just discovered this whole universe of ps3 patches. I had to learn it all mostly by myself.

About not crediting the original authors it was because I thought for Artemis would be another authorial code… Now that I understand a lot better what is going on. I see the shitty thing I did and I want to apologize to you and to all community. But I also would like to point out how no one showed up here at this forum or wherever to help ppl out, to actually explain what they are doing. Or trying to do. But when someone comes here and don't credit original authors it doesn't take 24 hours for you to reply.

You might think it is sad what I did and I agree and recognize my mistake. I am truly sorry for that. But to me, more sad is to see how some ppl hide information from others. A guy like you who is smart enough to create/find patches by yourself needed to be humble enough to come here and explain to these ppl what I tried to. In a much better way, I assume. If you were taking 10 minutes of your time to do it. A recent member of the community wouldn't be here doing this type of bullshit.

Respectfully,

@gmanarte

@FlexBy I also will make sure I will edit all my previous comments giving credit to the original authors. Thanks for pointing that out, although it was in a "rude" way. I understand your anger and I hope you understand and believe the reason of my mistake. Like you said, just because I am writing it in another format it doesn't make me the author. That was exactly what happened.
 
Last edited by a moderator:
So what's the status on a compilation of all the confirmed working patches? I see a GitHub repository by @LuanTeles but no contributions.

As an alternative/ additional option I'd be willing to host a google drive containing a bunch of the Artemis patches.

Trying to make a chart of all the patches in this thread, I'm like 6 pages in and kinda tired so I'ma post what I got so far
CF221F37-6698-44EB-A8EB-BC2088E7B4D8.png
39F558F2-4665-453F-B5AF-32CE86FDF0EF.png
7F87EC79-65BE-4201-8DC8-CAB561F5314B.png

827BC095-CD59-4E2B-909D-67211FF0E66B.png
 
Last edited by a moderator:
What ini settings did you try changing in Fallout New Vegas?

There are some that don't work, like Resolution and FOV for example, but there are plenty that do. Quick example below with some visually obvious changes for demonstrative purposes.

Default ini settings

iMaxAnistropy = 8 and FGrassStartFadeDistance = 3500

View attachment 43052

Modified ini settings

iMaxAnistropy = 0 and FGrassStartFadeDistance = 0

View attachment 43053

---------------------------

Also, I've been doing further testing with the autoexec.cfg files in games made by Monolith Productions using the LithTech Jupiter EX engine after discovering that the FPS cap could be changed.

In addition to changing the MaxFPS cap line to a specific figure, the line can just be deleted entirely. Setting the MaxFPS cap at 60 seems to limit the game to ~58 FPS, but deleting it entirely allows the game to hit 59.94 FPS. Setting the MaxFPS cap at 30 seems to limit the game to ~29.6 FPS but setting it at 30.33 allows it to reach 29.98 - 30.03 FPS. I haven't been able to achieve an exact 29.96 FPS cap on this title.

I've found that you can also change the FOV in both F.E.A.R. 2 and Condemned 2 by introducing the FovY line to the autoexec.cfg file though. For F.E.A.R. 2, I would reccomend keeping it to 80 or lower as numbers above 80 result in clipping from some weapons (primarily the SMG). For Condemned 2, I didn't notice any visible clipping, but haven't tested beyond 90 as I'm content with that.

View attachment 43054

Default F.E.A.R. 2 FOV

View attachment 43055

F.E.A.R. 2 80 FOV

View attachment 43056
How you do FEAR 2 60 FPS
 
How you do FEAR 2 60 FPS

I've quoted my comments from the overclock thread and this one below which explain the adjustment.

You'll need to access the game files to edit the autoexec.cfg, so you'll want to create a back up of your F.E.A.R. 2 game (preferably in JB Folder format for easy editing), I personally do this using Multiman. I then use FTP to access the autoexec.cfg file on my computer (file path is in the comments below), change the 'MaxFPS' line with notepad and then save it.

I have been digging through some of my games files in pursuit of the above and found that the FPS cap can be changed for F.E.A.R. 2: Project Origin, Condemned 2: Bloodshot and Middle-earth: Shadow of Mordor. These all appear to be games made by Monolith Productions using the LithTech Jupiter EX engine. F.E.A.R. which was also made by Monolith on an earlier version of the same engine doesn't appear to have this file.

All 3 of these games have an "autoexec.cfg" file within PS3_GAME > USRDIR which controls the "MaxFPS", I've tested these games at both 30 and 60 FPS and adjustments to the "MaxFPS" figure do seem to apply. F.E.A.R. 2 and Shadow of Mordor both have 45 FPS caps by default, whereas Condemned 2 has a 40 FPS cap.

View attachment 42992

Also, I've been doing further testing with the autoexec.cfg files in games made by Monolith Productions using the LithTech Jupiter EX engine after discovering that the FPS cap could be changed.

In addition to changing the MaxFPS cap line to a specific figure, the line can just be deleted entirely. Setting the MaxFPS cap at 60 seems to limit the game to ~58 FPS, but deleting it entirely allows the game to hit 59.94 FPS. Setting the MaxFPS cap at 30 seems to limit the game to ~29.6 FPS but setting it at 30.33 allows it to reach 29.98 - 30.03 FPS. I haven't been able to achieve an exact 29.96 FPS cap on this title.
 
I've quoted my comments from the overclock thread and this one below which explain the adjustment.

You'll need to access the game files to edit the autoexec.cfg, so you'll want to create a back up of your F.E.A.R. 2 game (preferably in JB Folder format for easy editing), I personally do this using Multiman. I then use FTP to access the autoexec.cfg file on my computer (file path is in the comments below), change the 'MaxFPS' line with notepad and then save it.
Thanks dude i appreciate that
 
Because it's easier and safer to apply a patch on memory than tampering with the EBOOT (decrypting, applying the patch, encrypting), which could break it if not done properly forcing you to recover it.
Respectfully it's not any harder, whether you edit the offset via prod, debugger, ps3mapi, make a rtm tool or just edit the EBOOT it's all the same. I think a lot of people just don't know much about editing memory in general for some reason, which is weird considering there is dozens of tutorials
 
If anyone is interested, I can make it work in the DLC The Last of Us Left Behind. and just put the code below through Artemis:


The last of us: Left behind.
0
Unlock
0 00039d1c 38a00000
#

The Last Of Us: Left Behind is a game that requires login to PSN account (online requirement[?]). My question is, applying Artemis Cheat Patcher while logged in, isn't risky? Furthermore having its EBOOT.BIN permanently editted for a mere fps boost, can't it be "mistaken"/detected by sony's anti-cheat system as a cheat and get your account banned, or more importantly your PS3's ID? When going online, do they trivially scan EBOOT.BINs looking for editted code or not?
 
Back
Top