Star Wars Battlefront III Wii .War

[JakeGreen]

Hey, so ages ago on xentax people were able to crack the .rax format for the xbox 360 build of Battlefront 3 making a UU3D plugin and a blender 2.49 plugin, but it seems like Free Radical changed the file formats for both models and animations for the Wii version as it's a much later version of the game then the xbox 360 build that was released.

The wii version does hold more updated assets compared to the leaked x360 build, that's why i've come here to see if anyone can help crack the format.

I was hoping someone could take a look at them and see if there is some way to get them converted with rigging, Some of the people that have looked into it on the FRD Archive say it can't be cracked because of how the data is split between the ob.war and the rdata.war.

SWBF3_Wii_Models_animations.rar

Edited January 13 by JakeGreen

[h3x3r]

5 hours ago, JakeGreen said:

Some of the people that have looked into it on the FRD Archive say it can't be cracked because of how the data is split between the ob.war and the rdata.war.

So the main file is the ob.war right? It has info about what is included in rdata.war right?

So i checked it a bit and find out that first uint32 value points on table which is located almost on the end of file. When i get there i see another pointers which return you on start of the file. Still didn't find anything related to the index/vertex count.

Well after some research i think the biggest issue will be correct serialization. Also not sure wher is content type variable. Like what is vertex/index/uv buffer, texture, skin, bone etc...

 

Sooo maybe these are file types? I think that var 1026 is some kind shape descriptor coz i found valid offset/size for face index. Still didn't get vertex offset.

 

Edited January 13 by h3x3r

[bobo]

So~ you said this file is from the Wii platform, yes, and the file structure is in big-endian format, correct. Firstly, I examined the file in .ob.war format from the hex view. Its structure looks quite loose, and it should be a file similar to those used in conjunction with .rdata.war. Yes, that's right, so .rdata.war actually contains the geometric data of the model. The .ob.war file points to skeletal information related to .rdata.war, as well as other things. Yes, now let's open an .rdata.war file, and you'll see the file structure is dense and very regular. Correct. So, it should be in a separate format. Let's use a fuzzy search to print the vertices. Yes, it appears that the vertex coordinates are placed at the forefront.