This topic was archived here:

https://web.archive.org/web/20230000000000fw_/https://www.zenhax.com/viewtopic.php?t=17320

globodepre, posted Fri Aug 19, 2022 11:55 pm (73081)

---

I would like to know how it is possible to extract images from the Fighting Evolution Rebirth game from Play Station 2 (SLPS_255.29)_?

BloodRaynare, posted Sat Aug 20, 2022 12:51 am (73083)

---

Please provide the sample file so we can help you.

globodepre, posted Sat Aug 20, 2022 6:58 am (73087)

---

Thanks. This file is 300MB https://www.mediafire.com/file/79e97e8if739jll/file1.bin/file

BloodRaynare, posted Sat Aug 20, 2022 7:22 am (73088)

---

I didn't see any indication of the table of contents inside (file offset, size, filenames). Is there a smaller files besides the file1.bin (Something like file1.idx)? If it's not there can you just give me the game's executable files instead (SLPS_255.29)?

globodepre, posted Sat Aug 20, 2022 3:20 pm (73090)

---

It looks like most of the graphics are compressed.

file executable "SLPS_255.29".
https://www.mediafire.com/file/6mm15yo2wgux3lk/SLPS_255.29/file

I'm looking for graphics, for example the main menu.

BloodRaynare, posted Sun Aug 21, 2022 4:43 am (73093)

---

Here's some BMS script to handle what you need. To use these script, you'll need QuickBMS

- Use the ultraman_fighting_evolution_rebirth.bms script first to extract all the files inside the FILE*.BIN by pointing it to SLPS_255.29 file like this:

Code:

quickbms ultraman_fighting_evolution_rebirth.bms SLPS_255.29

Make sure the SLPS_255.29 and all the FILE*.BIN from FILE1.BIN to FILE4.BIN is in the same directory, because this script will perform the extraction on ALL of the FILE*.BIN files at once. And one more thing, the TOC inside the SLPS_255.29 has no record for the filenames, so all the files will be having names of the hex notation of which offset address they were belong to. But at least they were grouped by the directory of the number that denotes the BIN archives (ex: 00 for FILE1.BIN, 01 for FILE2.BIN, and so on).

- The image/texture files are inside the file with .POM extension which resides in "00" directory, sometimes they were packed/compressed inside the FUM or DFS file (actual extension is .ENC for DFS). Use either of ultraman_fer_enc.bms script for decompressing the ENC/DFS file or ultraman_fer_fum.bms for extracting the contents inside the FUM file (and sometimes you need to decompress the extracted files too since most of the times the FUM files contains the ENC/DFS files).

For ENC/DFS

Code:

quickbms ultraman_fer_enc.bms [destination of the enc/dfs file] [target directory (optional)]

For FUM

Code:

quickbms ultraman_fer_fum.bms [destination of the fum file]  [target directory (optional)]

- After you obtained the POM file, now it's time to convert the POM files to PS2's standard TIM2 (.tm2) file. Like this:

Code:

quickbms ultraman_fer_pom2tm2.bms [destination of the pom file]  [target directory (optional)]

The resulting .tm2 file can be opened with many tools available, like Rainbow (Useful for images with multiple palettes. You will have to figure out how to recover the colors back though. Luckily only some files are like that) or XnViewMP.

There'a also optional script for IPU files (mainly used by the game for few animated particle effects or FMVs) named ultraman_fer_ipu.bms

You can find all the script needed in the attachment below.

Some tip: The main menu images are inside in one of the FUM files inside the 00 directory, forgot which one.

UFER.zip

globodepre, posted Sun Aug 21, 2022 6:05 pm (73102)

---

Thanks friends you know a lot. How do I use the codes ???. Should I create a *.bat file with the line of code inside the folder along with the "File*.BIN" and the respective "script.bms"? Or can I click on QuickBMS and do the steps as it asks, eg: " select the script to use", "select the large file..." and "now select the folder for extraction" ?
I tried a few times but I didn't succeed... do you have a video that shows the step by step?
Gives this result:
for ISO:


for File1:

BloodRaynare, posted Sun Aug 21, 2022 8:48 pm (73104)

---

globodepre wrote:

Thanks friends you know a lot. How do I use the codes ???. Should I create a *.bat file with the line of code inside the folder along with the "File*.BIN" and the respective "script.bms"? Or can I click on QuickBMS and do the steps as it asks, eg: " select the script to use", "select the large file..." and "now select the folder for extraction" ?
I tried a few times but I didn't succeed... do you have a video that shows the step by step?
Gives this result:
for ISO:


for File1:

No, you're doing it all wrong.

- You shouldn't pointing the script to the ISO file itself but the files inside.

- I thought I said it pretty clearly:

BloodRaynare wrote:

Use the ultraman_fighting_evolution_rebirth.bms script first to extract all the files inside the FILE*.BIN by pointing it to SLPS_255.29 file like this:

Code:

quickbms ultraman_fighting_evolution_rebirth.bms SLPS_255.29

Point it to SLPS_255.29, not to the FILE*.BIN files directly.

globodepre, posted Mon Aug 22, 2022 5:22 am (73109)

---

Friend BloodRaynare excuse my ignorance, I took the first step. Thanks in advance!!! I was able to extract the files from File1.BIN to a "00" folder. At the moment I'm looking for that main menu file among the "*.fum". There are exactly 170 files that vary in size. Thanks again friend.


How would it be to recompress these files to go back to the place they were extracted from... go back to being like the original?

BloodRaynare, posted Mon Aug 22, 2022 10:11 pm (73122)

---

globodepre wrote:

Friend BloodRaynare excuse my ignorance, I took the first step. Thanks in advance!!! I was able to extract the files from File1.BIN to a "00" folder. At the moment I'm looking for that main menu file among the "*.fum". There are exactly 170 files that vary in size. Thanks again friend.


How would it be to recompress these files to go back to the place they were extracted from... go back to being like the original?

Run the script like this:

Code:

quickbms -w -r -r -r (your bms script) (the file you want to reimport to) (same directory as where you extracted them previously)

For compressed files, it's recommended to delete everything else except the files you've modified to avoid false alarm when recompressing.
EDIT: Currently TM2 to POM reimport is impossible for now, might need to write a separate BMS script just for handling that alone.

globodepre, posted Tue Aug 23, 2022 2:40 am (73127)

---

Friend assuming I already have the edited "*.POM" files ready to take the places of the originals that were extracted. What would the steps be like doing the reverse work in "ultraman_fer_enc.bms" then in "ultraman_fer_fum.bms" and finally in ultraman_fighting_evolution_rebirth.bms creating the new file "File1.BIN" ?

BloodRaynare, posted Tue Aug 23, 2022 3:02 am (73128)

---

globodepre wrote:

Friend assuming I already have the edited "*.POM" files ready to take the places of the originals that were extracted. What would the steps be like doing the reverse work in "ultraman_fer_enc.bms" then in "ultraman_fer_fum.bms" and finally in ultraman_fighting_evolution_rebirth.bms creating the new file "File1.BIN" ?

To recompress the pom files back to enc, do it like this:

Code:

quickbms -w -r -r -r ultraman_fer_enc.bms [name of your enc/dfs file] [path where you decompressed the enc/dfs file (optional)]

For packing the enc files back to fum:

Code:

quickbms -w -r -r -r ultraman_fer_fum.bms [name of your fum file] [path where you unpacked the fum file (optional)]

To repack the FILE*.BIN:

Code:

quickbms -w -r ultraman_fighting_evolution_rebirth

or

Code:

quickbms -w -r -r -r ultraman_fighting_evolution_rebirth

The difference is with the second one, you won't be limited by the sizes of the original file.

globodepre, posted Tue Aug 23, 2022 3:51 am (73129)

---

I couldn't get.

Code:

quickbms_4gb_files.exe -w -r -r -r ultraman_fer_enc.bms [t_bg_pom.POM]

BloodRaynare, posted Tue Aug 23, 2022 3:52 am (73130)

---

globodepre wrote:

I couldn't get.

Code:

quickbms_4gb_files.exe -w -r -r -r ultraman_fer_enc.bms [t_bg_pom.POM]

Original .enc file, not the already decompressed one.

globodepre, posted Tue Aug 23, 2022 4:14 am (73131)

---

So?

Code:

quickbms_4gb_files.exe -w -r -r -r ultraman_fer_enc.bms [t_bg_pom.ENC]

BloodRaynare, posted Tue Aug 23, 2022 4:40 am (73132)

---

Try remove the "[" and "]"

globodepre, posted Tue Aug 23, 2022 11:30 am (73137)

---

Friend got the ENC step and also the FUM step and also the File1.BIN step. It is correct this message reimports 3 files but 2 have logs.....

After creating the *.FUM comparing the sizes between the original and the modified one it gets bigger.

BloodRaynare, posted Tue Aug 23, 2022 12:28 pm (73138)

---

globodepre wrote:

It is correct this message reimports 3 files but 2 have logs.....

It's normal, if you only left the modified files, QuickBMS will skip the others and just focus with the reimporting of the modified file.

globodepre wrote:

After creating the *.FUM comparing the sizes between the original and the modified one it gets bigger.

Ah, this is one of the QuickBMS quirks. If the compressed files are still slightly bigger than the original, it will put the new one at the end of the file by appending it and zeroing the original then sets the offset and the sizes accordingly.

globodepre, posted Tue Aug 23, 2022 2:26 pm (73142)

---

I'm making progress but there are some errors due to not having mastered the tools yet.

globodepre, posted Wed Aug 24, 2022 3:00 am (73148)

---

Thanks brother BloodRaynare!
I'm doing the steps slowly so I don't lose focus on the codes. Hope to unfold soon and thank you for your attention.

globodepre, posted Thu Aug 25, 2022 6:24 am (73164)

---

Question: Why even I using " -w -r " in the code to keep the original file size. "Remembering that the file was edited on top of the original". In the process from *.POM to *.ENC it has the same size in bytes, but the content seen in HEX is smaller and is padded with zeros to get the size of the original?

BloodRaynare, posted Thu Aug 25, 2022 6:40 am (73166)

---

globodepre wrote:

Question: Why even I using " -w -r " in the code to keep the original file size. "Remembering that the file was edited on top of the original". In the process from *.POM to *.ENC it has the same size in bytes, but the content seen in HEX is smaller and is padded with zeros to get the size of the original?

"-w -r" aka regular REIMPORT, is for files that has the same size as the original or less, "w -r -r" aka REIMPORT2 is for the files that are bigger than the original. "-w -r -r -r" aka REIMPORT3 is more or less the same as REIMPORT2 "with the only difference that the archive is shrinked or enlarged if there is no offset field used in the archive and the size of the input file differs than the original." per QuickBMS's documentation

globodepre, posted Thu Aug 25, 2022 7:52 pm (73176)

---

Friend "You are the Guy!" The solution was Reimport2. Project in progress...
Thanks!

globodepre, posted Sat Aug 27, 2022 2:20 pm (73218)

---

Friend, i managed to buy some files ,POM to .ENC but others I can't even trying with the 3 reimports giving this error.