MLB 14 The Show PS Vita/Stadium 3D models

[lorak]

In the attachment you will find two .cb files containing the 3D model (I guess) of the Arizona Diamondbacks stadium. In addition, there is another file called "Locator.bin". It maybe has the vertices and faces offsets and its counts. I am not sure about it as I cannot understand the file. You can see the model of this stadium in-game in the attached screenshots.

Hopefully there is someone able to understand those .cb files to get the stadium model in Blender or Noesis. 

Thanks in advance.

Arizona Diamondbacks Stadium.zip

Edited October 8 by lorak

[lorak]

According to me, in the file stadium.cb vertices start at offset 0x40 or 0x48 and faces at offset 0xae4a.
Anyway, take this comment with a grain of salt.

[shak-otay]

The face indices start at 0xae48, in 12 bytes blocks, where the last 6 bytes need to be skipped (so reading 3 FIs per block).

Edited October 9 by shak-otay

[lorak]

On 10/9/2025 at 6:18 AM, shak-otay said:

The face indices start at 0xae48, in 12 bytes blocks, where the last 6 bytes need to be skipped (so reading 3 FIs per block).

I was close 😁

Many thanks!

I assume the vertex block size is at offset 0x3c.
One way to find the number of vertices (maybe the only one in this file?) is by computing (0xae48-0x48)/0xc = 0xe80 or 3712 in decimal.

Following the information you share, faces indices are in the block 0xae48 to 0x16feb (skipping the last 6 bytes of each block).
I will try to check what is in the rest of the file from offset 0x16fec until the end as it seems there are more faces and vertices blocks (maybe uv).

Do you have any idea of what kind of data is in "Locator.bin"? I just noticed that starting from offset 0x4, it seems to be a 0x14 byte block of data. The first bytes look like an index numbering or so. Blocks starting at 0x68 and 0x7c are full of zeroes beside the block index. Another group seems to start at offset 0x338. 

Edited October 10 by lorak

[shak-otay]

8 hours ago, lorak said:

Do you have any idea of what kind of data is in "Locator.bin"? I just noticed that starting from offset 0x4, it seems to be a 0x14 byte block of data.

I have no idea. Starting from 0x94, FVFsize 20, it looks like so:

 

Starting from 0xC8 there's some kind of block structure, I don't know:

# 0xc8: verts= 400
v 131.610489 0.000000 -106.864922
v 129.791977 0.000000 -108.108910
v 130.871521 0.000000 -130.392456
v 133.028336 0.000000 130.271164
v -130.619934 0.000000 106.807335
v -133.020599 0.000000 107.796707
v -131.548706 0.000000 91.773544
v -133.893036 0.000000 -250.735504

v 0.000000 0.000000 -242.854004
v 0.000000 0.000000 -249.910965
v 0.000000 0.000000 -241.886169
v 0.000000 0.000000 245.846008
v 0.000000 0.000000 253.690277
v 0.000000 0.000000 246.629028
v 0.000000 0.000000 254.654800
v 0.000000 0.000000 -76.308174

v 132.055237 0.000000 -76.925873
v 129.133331 0.000000 -115.179634
v 130.211090 0.000000 -115.815094
v 130.211090 0.000000 97.269958
v -132.706726 0.000000 96.599609
v -123.971092 0.000000 77.744301
v -134.455322 0.000000 77.066010
v -133.958496 0.000000 -231.927032
v 91.771675 0.000000 -231.715210
v 91.771675 0.000000 229.643967
v -91.838936 0.000000 230.274918
v -88.752533 0.000000 241.558060
v -39.968483 0.000000 241.558060
v -39.968483 0.000000 241.558060
v -39.968483 0.000000 241.558060
v -39.968483 0.000000 -165.794189

v 119.308289 0.000000 -184.741730
v 116.026817 0.000000 166.204681
v -119.773979 0.000000 186.299866
v -120.845444 0.000000 -112.508575
v 132.822128 0.000000 -112.508575
v 132.822128 0.000000 -177.601334
v 119.308289 0.000000 178.336029
v -119.773979 0.000000 -83.527054
v 132.309326 0.000000 -99.647011
v 126.703629 0.000000 -102.812477
v 124.808708 0.000000 -102.434982
v 129.385483 0.000000 79.609688
v -131.566162 0.000000 83.322784
v -129.675705 0.000000 99.360695
v -135.568207 0.000000 102.563026
v -132.673676 0.000000 118.995926
v -130.463287 0.000000 123.351372
v -130.463287 0.000000 106.930008
v -133.214722 0.000000 -109.352661
v 132.031540 0.000000 0.000000

v 0.000000 0.000000 62.757000
v 0.000000 0.000000 0.

 

[lorak]

Yes, thanks. Still not clear what kind of data is in Locator.bin.

By the way, walls.cb has the model for walls (as the file name suggests 🙂) and jumbotron or screen of the stadium as shown in the screenshots below.

I am trying to find uv in both files, stadium.cb and walls.cb with no success until now.

[shak-otay]

2 hours ago, lorak said:

I am trying to find uv in both files, stadium.cb and walls.cb with no success until now.

You could trick around with the values in the first column here:

address 0xae50:
27333 15813     2     1     3    10 
33574 15813     4     1     5    10 
20698 15679     5     1     0    10 
20698 15679     3     6     2    10 
50909 15763     2     6     7    10 
57821 15714     8     9    10    10 
41781 15991    10     9     2    10 
53722 15917    11    10    12    10 
62936 15979    12    10     2    10 
45166 15977    12    13    11    10 
10238 15846    11    13    14    10 
10238 15846     2    12    15    10 
58744 15664    15    12    13    10 
58744 15664     2    15     9    10 
34447 15579     9    15    16    10 
34447 15579    17    18    19    10 
address 0xaf10:
62859 15561    19    18    20    10 
49943 15669    21    22    23    10 

(Column 3 to 5 contain the FIs, btw.)

[lorak]

Thanks for the tip.
Apprently, the screenshot below shows uvs from walls.cb. At least uvs generated by Hex2Obj seem more or less reasonable.

I will be playing around with both files.