..:: PCSX2 Forums ::..

(12-27-2014, 07:46 PM)FeRcHuLeS Wrote: [ -> ]Just read synce's creating widescreen patches in less than 10 steps, you can find the link in the page 1 in this thread

thank you for your answer!!

(12-28-2014, 11:08 AM)prettyboy Wrote: [ -> ]Little giant,thank you so much!I understood!
here is the 16:9 hacks of [Kuon(NTSC-J)]:
--------------------------------------------------------
gametitle=Kuon [NTSC-J] (SLPS-25329)
comment=Widescreen hack
//16:9
patch=1,EE,00138104,extended,3c023f19
patch=1,EE,00138108,extended,3443999a
--------------------------------------------------------
16:9 x/0.75(or x 1.3333333)=0.600000=3f19999a
so we get x = 0.45;
then we make the 16:10 hacks,
16:10 0.45/0.83333333 (or x1.2 )
=0.54000000216=3F0A3D71
so the 16:10 hacks of [Kuon(NTSC-J)]:
--------------------------------------------------------
gametitle=Kuon [NTSC-J] (SLPS-25329)
comment=Widescreen hack
//16:10
patch=1,EE,00138104,extended,3c023F0A
patch=1,EE,00138108,extended,34433D71
--------------------------------------------------------
Am I right?
but I have test the 16:10 hacks,it seems not to be a 16:10 ratio value.
then I changed [patch=1,EE,00138104,extended,3c023f19] to
[patch=1,EE,00138104,extended,3c023f2a].
finally I found it should be a 16:10 ratio value.
sorry for my broken english,thanks again for your help!!

I'm sorry I forgot.

It have two pattern

1：
16：9 is original value ÷ 0.75 (or × 1.3333333) 【God Hand】
2：
16：9 is original value × 0.75 (or ÷ 1.3333333) 【Kuon】

Kuon original value is （you can use PS2dis to find it）
00138104 3c023f4c
00138108 3443cccd

3f4ccccd = 0.8000000119
16:10 is 0.8000000119 ÷ 1.2 = 0.6666666865 = 3F2AAAAB

EDIT: about Silent Hill 3 (PAL)
The pnach is composed of 2 distinct codes; for PAL and NTSC displays, chosen at the game boot
Actually, this works well when we select the PAL display; in NTSC, the display remains deformed (I tried by removing the PAL part codes of the pnach: no effect)

Hi, Here it is another SEGA Hit enjoy it, sorry for the black fighters (I don't know how to configure the emu to show them).
By the way no one has replied my questions, could anyone please?
1.- What are elf hacks? I've just released one, I know but what is...
2.- What are memory hacks? When I read memory hacks comments there are lots of zeros then you gave non zero values to those addresses.
and
3.- Is there anyway to export addresses from ELF SEARCH TOOL to CHEAT ENGINE quickly? I'm copying-pasting one by one, It takes so long
Please anyone, I'm trying to make some widescreen hacks, That's all I want to learn, please!!

SEGA AGES VOL. 16 VIRTUA FIGHTER 2 (NTSC-J)

(12-23-2014, 12:33 AM)PsxFan107 Wrote: [ -> ]16:9 Request: Spider-Man (NTSC-U) (SLUS-20336)

Can someone please make a 16:9 patch for spider-man?

(12-29-2014, 01:49 AM)FeRcHuLeS Wrote: [ -> ]1.- What are elf hacks? I've just released one, I know but what is...

I'll start with the basics and then go into detail.

When a PS2 developer compiles their PS2 application, they end up with an ELF file (amongst other things). ELF files contain all of a PS2 application's executable logic.

ELF hacking consists of modifying that file's code and/or "built-in" values. Some people prefer that way because it's a more "direct" way of hacking, since the code/values that are modified will never ever get changed by the application while it's running. So ELF hacking is less prone to problems that sometimes affect memory hacking. It's also possible to use a HEX editor to directly modify ELF files to avoid the need for cheat devices or pnaches.

On a side note, as we've recently seen with Sega Classics Collection, sometimes certain games (like compilations/demo discs) contain multiple ELF files, which makes it impossible to create "proper" ELF hacks in pnach files because you can't be sure which ELF file is running at any given point in time. This can be worked around by using "E" type cheat device codes to detect which ELF is currently running, then write your ELF hacks into memory so the hacks are only used at appropriate times. More info about it can be found in some of my recent posts.

(12-29-2014, 01:49 AM)FeRcHuLeS Wrote: [ -> ]2.- What are memory hacks? When I read memory hacks comments there are lots of zeros then you gave non zero values to those addresses.

While a game is running, the game's engine will usually dynamically write a lot of values into "live" memory (addresses that appear with "//00000000" in pnach comments). Live memory can potentially change at any time depending on what the game is doing.

For example, if you browse through a game's main menu and then go in-game, a whole bunch of memory addresses' values will change. This makes memory hacking kind of "unsafe" IMO. If you overwrite a live memory address, but that address gets repurposed by the game depending on what it's doing, the value you overwrote that address with could potentially introduce problems in the game, like glitchy graphics, crashes, etc. This won't always be a problem in all games in the context of widescreen hacking, but the potential is always there.

I think most people usually start off by creating live memory hacks, and then "port" them into ELF hacks. Here are a few brief examples on how to do that:

1. Use certain tools (e.g. IDA Pro, ps2dis, ELF Search Tool, etc) to search through an ELF file for HEX values that were found in live memory. Sometimes the value you're looking for might only exist once or a couple of times throughout a game's ELF file, which can make life easy. Life becomes much harder if the value exists dozens/hundreds of times throughout the ELF file... . In some cases half of a float value might exist inside a MIPS instruction, in which case you might have more luck searching for the first or last 2 bytes of your float's HEX value (e.g. 1.0 float = 3F800000, so search for 3F80).
   
2. Newer Git development builds of PCSX2 contain a built-in debugger. If you know what you're doing, you can use it to set breakpoints to "freeze" the game when a live memory address gets written to and its value changes. From there you can look through the MIPS instructions that were running at the time the game wrote to the live address and figure out the origin of the value that was written. Sometimes the value is just loaded from somewhere in the game's ELF file. But other times the value can be the result of a calculation the game does on-the-fly, which is a lot more painful to deal with...

(12-29-2014, 01:49 AM)FeRcHuLeS Wrote: [ -> ]3.- Is there anyway to export addresses from ELF SEARCH TOOL to CHEAT ENGINE quickly? I'm copying-pasting one by one, It takes so long

I don't think there's any way to mass copy/paste a bunch of addresses into Cheat Engine in one shot. However, if you're only looking for all instances of a 4 byte (8 character) HEX value, you can search for it in Cheat Engine directly. Just set its memory range between 20000000-30000000, tick the "Hex" checkbox, then enter the HEX value you're looking for and scan for it. From there you can highlight all the addresses it found and click the red arrow button to bring them into the bottom panel. From there, you can highlight them all again and change their type and/or show them as decimal to get decimal (easy-to-read) numbers.

(12-28-2014, 03:30 PM)Little giant Wrote: [ -> ]I'm sorry I forgot.

It have two pattern

1：
16：9 is original value ÷ 0.75 (or × 1.3333333) 【God Hand】
2：
16：9 is original value × 0.75 (or ÷ 1.3333333) 【Kuon】

Kuon original value is （you can use PS2dis to find it）
00138104 3c023f4c
00138108 3443cccd

3f4ccccd = 0.8000000119
16:10 is 0.8000000119 ÷ 1.2 = 0.6666666865 = 3F2AAAAB

OK,I understood!thanks very much for answering again!
now I can try to make the 16:10 hacks for my other game!

(12-29-2014, 07:51 AM)Aced14 Wrote: [ -> ]I'll start with the basics and then go into detail.

When a PS2 developer compiles their PS2 application, they end up with an ELF file (amongst other things). ELF files contain all of a PS2 application's executable logic.

ELF hacking consists of modifying that file's code and/or "built-in" values. Some people prefer that way because it's a more "direct" way of hacking, since the code/values that are modified will never ever get changed by the application while it's running. So ELF hacking is less prone to problems that sometimes affect memory hacking. It's also possible to use a HEX editor to directly modify ELF files to avoid the need for cheat devices or pnaches.

On a side note, as we've recently seen with Sega Classics Collection, sometimes certain games (like compilations/demo discs) contain multiple ELF files, which makes it impossible to create "proper" ELF hacks in pnach files because you can't be sure which ELF file is running at any given point in time. This can be worked around by using "E" type cheat device codes to detect which ELF is currently running, then write your ELF hacks into memory so the hacks are only used at appropriate times. More info about it can be found in some of my recent posts.



While a game is running, the game's engine will usually dynamically write a lot of values into "live" memory (addresses that appear with "//00000000" in pnach comments). Live memory can potentially change at any time depending on what the game is doing.

For example, if you browse through a game's main menu and then go in-game, a whole bunch of memory addresses' values will change. This makes memory hacking kind of "unsafe" IMO. If you overwrite a live memory address, but that address gets repurposed by the game depending on what it's doing, the value you overwrote that address with could potentially introduce problems in the game, like glitchy graphics, crashes, etc. This won't always be a problem in all games in the context of widescreen hacking, but the potential is always there.

I think most people usually start off by creating live memory hacks, and then "port" them into ELF hacks. Here are a few brief examples on how to do that:

1. Use certain tools (e.g. IDA Pro, ps2dis, ELF Search Tool, etc) to search through an ELF file for HEX values that were found in live memory. Sometimes the value you're looking for might only exist once or a couple of times throughout a game's ELF file, which can make life easy. Life becomes much harder if the value exists dozens/hundreds of times throughout the ELF file... . In some cases half of a float value might exist inside a MIPS instruction, in which case you might have more luck searching for the first or last 2 bytes of your float's HEX value (e.g. 1.0 float = 3F800000, so search for 3F80).
   
2. Newer Git development builds of PCSX2 contain a built-in debugger. If you know what you're doing, you can use it to set breakpoints to "freeze" the game when a live memory address gets written to and its value changes. From there you can look through the MIPS instructions that were running at the time the game wrote to the live address and figure out the origin of the value that was written. Sometimes the value is just loaded from somewhere in the game's ELF file. But other times the value can be the result of a calculation the game does on-the-fly, which is a lot more painful to deal with...

I don't think there's any way to mass copy/paste a bunch of addresses into Cheat Engine in one shot. However, if you're only looking for all instances of a 4 byte (8 character) HEX value, you can search for it in Cheat Engine directly. Just set its memory range between 20000000-30000000, tick the "Hex" checkbox, then enter the HEX value you're looking for and scan for it. From there you can highlight all the addresses it found and click the red arrow button to bring them into the bottom panel. From there, you can highlight them all again and change their type and/or show them as decimal to get decimal (easy-to-read) numbers.

Thanks for all your answers now all is plain and clear, by the way do you think all the values proposed in making elf hacks to find renders or horizontal fovs helps to find vertical fovs as well?.
Thank you very much again.

(12-29-2014, 06:46 AM)PsxFan107 Wrote: [ -> ]Can someone please to make a 16:9 patch for spider-man?

Why not to make a try friend you can make it by yourself?. Just try synce's "Creating widescreen patches in less than 10 steps", if it doesn't work, try making an elf hack just use ELF SEARCH TOOL and search for addresses that devina40's "Widescreen Patch Archive, & Helpful Info" proposes, come on you'll have fun for sure!!!

(12-29-2014, 04:06 PM)FeRcHuLeS Wrote: [ -> ]Why not to make a try friend you can make it by yourself?. Just try synce's "Creating widescreen patches in less than 10 steps", if it doesn't work, try making an elf hack just use ELF SEARCH TOOL and search for addresses that devina40's "Widescreen Patch Archive, & Helpful Info" proposes, come on you'll have fun for sure!!!

I'm asking because I've already tried before and have had absolutely no luck.

Also, I have an updated patch for teenage mutant ninja turtles, however, the in-game cutscenes are in vert - because I was unable to find a way to zoom out. If anyone can fix this, I would greatly appreciate it.