HomeForumsWhat's newResources 
 
 
Issue with ByteSearch based on VDP1 extracted tile
feudjey - Jul 20, 2024
  feudjey Jul 20, 2024
First thing, hello all.
Second thing, I'm new here, this is my first post.
Third thing, I'm french, so please be kind with my English.

I decided to make an undub version of Saturn Bomberman, I find audio digits just much crazyer in japanese.
I was first looking for a way to edit audio in the US version but I didn't find any tutorial. In contrast I found Malenko's Let's replace Sega Saturn graphics... great post in this place.
I do not have to follow every step because I have both JP and US versions of the game and only have to replace japanese text tiles by english ones.



First tile I get from VDP1 is the "Stage" button. Fortunately, all menu buttons have exacty the same address, width, height and color mode in both versions.



I won't have to edit the image, but I want to be sure I dumped the right data, so I open my stage_j.bin in Crystal Tile, and I get this :



I assume I can now look for the file containing my tile data in the japanese extracted iso.
I use ByteSearch, looking for a very small chunk, but always get 0 results when I search for more than 3 or 4 bytes:

Code: 
  
PS D:\bomberman\tools> .\byte_search.exe --source_type string --target ..\dump\jp\  --source F77762222222AAA2

ByteSearch v1.7
Written by Derek Pascarella (ateam)

> Gathering list of all files in target scan folder...

> Initiating scan process against 84 files...

> Scan complete! Found 0 match total.

I have no idea of what is going wrong. Maybe some files are compressed ?
I know .CPK are video files and .AIF are audio files, but I don't know anything about ._PRE and ._TRK
I hope someone can help me to go further.
Here is the files structure for the japanese version, everything is on the same level, no sub-directories.
Thanks in advance.

Code: 
  
PROGRAM.BIN   12 976 962
0KRNL.BIN        786 432
0._POST          307 200
1._PRE           352 800
1._TRK         3 824 352
2._PRE           352 800
2._TRK        28 329 840
3._PRE           352 800
3._TRK        26 916 288
4._PRE           352 800
4._TRK        31 335 696
5._PRE           352 800
5._TRK        32 217 696
6._PRE           352 800
6._TRK        26 659 920
7._PRE           352 800
7._TRK        21 643 104
8._PRE           352 800
8._TRK        19 733 280
9._PRE           352 800
9._TRK         2 368 464
10._PRE          352 800
10._TRK       31 058 160
11._PRE          352 800
11._TRK       14 631 792
12._PRE          352 800
12._TRK       28 917 840
13._PRE          352 800
13._TRK       21 525 504
14._PRE          352 800
14._TRK        7 199 472
15._PRE          352 800
15._TRK       30 373 728
16._PRE          352 800
16._TRK       27 175 008
17._PRE          352 800
17._TRK        5 129 712
18._PRE          352 800
18._TRK        1 773 408
19._PRE          352 800
19._TRK        1 368 864
20._PRE          352 800
20._TRK        1 234 800
21._PRE          352 800
21._TRK        6 820 800
22._PRE          352 800
22._TRK        6 460 944
23._PRE          352 800
23._TRK        6 620 880
24._PRE          352 800
24._TRK        7 676 928
25._PRE          352 800
25._TRK        7 079 520
26._PRE          352 800
26._TRK        1 234 800
27._PRE          352 800
27._TRK        1 074 864
28._PRE          352 800
28._TRK       26 561 136
29._PRE          352 800
29._TRK          531 552
M_007.AIF        173 964
M_015.AIF        154 164
M_021.AIF        164 748
M_025.AIF        203 276
M_026.AIF        154 124
M_030.AIF        141 836
M_032.AIF        139 948
M_037.AIF         21 860
M_039.AIF        175 884
M_058.AIF        300 492
M_059.AIF        124 620
M_060.AIF        151 270
M_061.AIF        262 092
M_062.AIF        237 708
M_063.AIF        188 300
M_064.AIF        396 108
M_065.AIF        363 738
M_066.AIF         90 930
M_067.AIF        263 756
M_087.AIF         64 216
BOMSS1.CPK    28 373 676
BOMSS2.CPK    32 859 508
BOMSS3.CPK    35 441 572

  Malenko Jul 23, 2024
Byte_search won't be able to find compressed data by searching the uncompressed data. You could use a diff program like WinMerge ( WinMerge - You will see the difference…... ) to compare the files from each version , that should narrow down where the data could be.