XeNTaX

Posted: **Sat Apr 23, 2005 5:00 pm**

Heres a file, all the others are too big. Its in WAD fomrat but not compatible with either extractor yet!

Heres the example file:

http://lukereeve.co.uk/HD.wad

Posted: **Mon Apr 25, 2005 6:37 am**

I was just about 2 make this topic. I hope someone can get the .wad format 2 work cause wm21 has some sweet textures I could use for other wrestling games

Posted: **Mon Apr 25, 2005 12:51 pm**

Thanks for the archive - we are downloading it now and will take a look at it soon.

WATTO
[email protected]
http://www.watto.org

Posted: **Mon Apr 25, 2005 2:27 pm**

Oh Hell yes! You guys rock!!

Posted: **Mon Apr 25, 2005 3:03 pm**

I downloaded it and it does not seem to much of a problem, at first glance. WIll look into it.

Posted: **Mon Apr 25, 2005 4:03 pm**

Sweet!

I cant wait you guys are simply amazing!

Posted: **Tue Apr 26, 2005 1:36 pm**

looking forward to your findings guys

Posted: **Tue Apr 26, 2005 2:55 pm**

This is it:

Code: Select all

0-2 	IDString	"WAD"
3-6 	32-bit		Unknown (01000000)
7-10	32-bit		Unknown (00000000)
11-14	32-bit		Number of files (N)

15-(15+N*12) All file entry-Offset info

This has the following (relative) format:

0-3	32-bit		Unknown
4-7	32-bit 		absolute offset of file entry
8-11	32-bit		Unknown (usually 0)

Each file entry has an info header and a data section. 

File Entry format:

0-1 	16-bit		Relative offset of (compressed) file data (ROCD)
2-5 	32-bit		Uncompressed Size of file
6-9	32-bit		Unknown
10	8-bit		The byte before the filename (0x01)
11-ROCD	String		Filename 
ROCD-??	DATA		Zlib Compressed file data.

There's one problem. There's no (to my knowledge) a "Compressed Size" variable for easy extraction of the compressed data.
Also, the file-entries are not in the same order as in the FIleentry-offset section, preventing easy calculation of compressed sizes.

Well, it's possible though. Just load all entries, sort them (ascending) and then calculate the compressed sizes.

Posted: **Tue Apr 26, 2005 3:21 pm**

Oh wel, I could create a script anyhow. Zlib knows when to stop decompressing, so I just took the uncompressed size as a measure. May not work on all files, but most will probably. Use the Custom BMS option.

Note: import does not work, even though MexCom might allow you to visit the Editor.

Also attached some examples. Jeez, never knew The Rock could take up such a gay position LOL.

Anyway the script is below as a .BMS.

Code: Select all

ComType ZLib1 ;
IDString 0 WAD ;
Get DUM Long 0 ;
Get DUM Long 0 ;
Get FNUM Long 0 ;
For T = 1 To FNUM ;
Get DUM Long 0 ;
Get FEO Long 0 ;
Get DUM Long 0 ;
SavePos EO 0 ;
GoTo FEO 0 ;
Get JP Int 0 ;
SavePos SS 0 ;
Math SS += JP ;
Get UCS Long 0 ;
Get DUM Long 0 ;
Get B Byte 0 ;
SavePos S 0 ;
Math SS -= S ;
GetDString FN SS 0 ;
SavePos FO 0 ;
Set FSI Long UCS ;
CLog FN FO FSI 0 0 UCS 0 ;
GoTo EO 0 ;
Next T ;

Posted: **Tue Apr 26, 2005 4:46 pm**

Wow thanks alot Im sure it will work great. But for some reason the MexBinderPlus App won't let me open the .mrf file so I can add the new wad.bms

It says run-time error 7. Maybe you could post your mrf file that has support for the new bms file you made or maybe you could suggest another fix. Thanks for all the hard work I really appreciate it. Ill keep messing around with it I can't wait 2 use it hehe

Posted: **Tue Apr 26, 2005 5:56 pm**

The MRF is changed since the last version, the new Binder has not been released yet. Meanwhile, the Use Custom BMS in Tools is the way to go, I guess.

Posted: **Tue Apr 26, 2005 6:31 pm**

I dont have that option!? please explain with more detail Im starting 2 think Im retarded lol

Posted: **Tue Apr 26, 2005 6:36 pm**

Well, you DO..."Run custom script on..."

XeNTaX

Help again! WWE WMXXI

Help again! WWE WMXXI