Difference between revisions of "GRAF:3D Sex Villa BXP"

From XentaxWiki
Jump to: navigation, search
(Undo revision 5574 by 85.124.203.37 (talk))
Line 1: Line 1:
If you are from thriXXX : PLEASE READ THE http://wiki.xentax.com/index.php/Talk:3D_Sex_Villa_BXP DISCUSSION
+
 
  
 
{{GRAFTemplate1|
 
{{GRAFTemplate1|

Revision as of 23:32, 15 March 2012


Back to index | Edit this page

BXP

{{GRAFPageMisc{{ subst:#if: Archive | {{subst:!}}Archive }}{{ subst:#if: Little Endian | {{subst:!}}Little Endian }}}}

Format Specifications

// ARCHIVE HEADER

char {8}     - Header ("BXP" + (byte)2 + "ARCH")
uint64 {8}   - Archive Length [+32]
uint64 {8}   - Padding (88,39,255,135,206,225,196,1)
uint64 {8}   - null


// ARCHIVE INDEX

char {8}     - Header ("BXP" + (byte)2 + "INDX")
uint64 {8}   - Unknown
uint64 {8}   - Padding (88,39,255,135,206,225,196,1)
uint64 {8}   - null
byte {16}    - CRC?
byte {16}    - CRC? (same as above field)


// FOLDER TREE

char {8}     - Header ("BXP" + (byte)2 + "TREE")
uint64 {8}   - Offset to the "// FILE DATA" [+128] (ie relative to "// DIRECTORIES")
uint64 {8}   - Padding (88,39,255,135,206,225,196,1)
uint64 {8}   - null


// DIRECTORIES

// for each directory
char {8}     - Header ("BXP" + (byte)2 + "SDIR")
uint64 {8}   - Unknown Length/Offset
byte {16}    - null
uint32 {4}   - Number Of Sub-Directories in this directory
uint32 {4}   - Number Of Files in this directory
uint64 {8}   - Length Of Filename Directory Component (length of subDirName+null + fileNames+nulls)
byte {16}    - null


// for each sub-directory in this directory
uint32 {4}   - null
uint32 {4}   - Relative Offset To This Directory? (32) (relative to the start of this subDirEntry)
uint32 {4}   - Hash?
char {X}     - Sub-Directory Name
byte {1}     - null Sub-Directory Name Terminator
byte {X}     - null Padding to a multiple of 32 bytes


// for each file in this directory
uint64 {8}   - Filename Offset (relative to the start of the filename directory)
uint64 {8}   - null
byte {16}    - CRC?
uint32 {4}   - null
uint32 {4}   - Unknown (1)
uint64 {8}   - null
uint64 {8}   - File Length (not including the file header fields?)
uint64 {8}   - File Offset (relative to the start of the file data)


// repeat for each sub-directory (repeat from "// for each directory")


byte {32}    - CRC?


// FILENAME DIRECTORY

// for each file
char {X}     - Filename
byte {1}     - null Filename Terminator


byte {X}     - null Padding to a multiple of 32 bytes


// FILE DATA

char {8}     - Header ("BXP" + (byte)2 + "DATA")
uint64 {8}   - Total Length Of File Data (length of everything in "// for each file")
uint64 {8}   - Padding (88,39,255,135,206,225,196,1)
uint64 {8}   - null


// for each file
char {8}     - Header ("BXP" + (byte)2 + "FILE")
uint64 {8}   - File Length (length of "X - File Data" only) [+30]
uint64 {8}   - CRC?
uint32 {4}   - null
uint32 {4}   - Unknown (1)
byte {X}     - File Data
byte {X}     - null Padding to a multiple of 32 bytes

Notes and Comments

These were copied from the template, I'm not sure if they're on the right page.

Notes by Gregory:

1. In the version 24, the file names are encrypted as XOR 0xBE.

2. "BXP" + (byte) in all headers: In the version 24, the (byte)=3.

3. // ARCHIVE INDEX

   char {8}     - Header ("BXP" + (byte)2 + "INDX")
   uint64 {8}   - Unknown   <-----   this shuld be relative offset to the first "BXP.FILE" 

I have used folloxing piece of C++ code:

 ArchiveOffset = 0x00;
 IndexOffset = 0x20;
 TreeOffset = 0x60;
 DirOffset = 0x80;
 DataOffset = DirOffset + (__int64*) &buffer[TreeOffset + 8];
 FileOffset = DirOffset + (__int64*) &buffer[IndexOffset + 8];

4. There are some directories containing both files and sub-directories. In such case, the files are listed prior to the sub-directories. I guess that the structure of directory is:

 {
   char {8}     - Header ("BXP" + (byte)2 + "SDIR")
   uint64 {8}   - Unknown Length/Offset
   byte {16}    - null
   uint32 {4}   - Number Of Sub-Directories in this directory
   uint32 {4}   - Number Of Files in this directory
   uint64 {8}   - Length Of Filename Directory Component (length of subDirName+null + fileNames+nulls)
   byte {16}    - null 
   for (each file)
   {
     uint64 {8}   - Filename Offset (relative to the start of the filename directory)
     uint64 {8}   - null
     byte {16}    - CRC?
     uint32 {4}   - null
     uint32 {4}   - Unknown (1)    // or (0) - a switch?
     uint64 {8}   - null
     uint64 {8}   - File Length (not including the file header fields?)
     uint64 {8}   - File Offset (relative to the start of the file data) 
   }
   for (each sub-directory)
   {
     uint32 {4}   - null   // Filename Offset (relative to the start of the filename directory)
     uint32 {4}   - Relative Offset To This Directory? (32) (relative to the start of this subDirEntry)
   }
   for (each entry)            // entry is file or sub-directory
   {
     uint32 {4}   -   Hash?  
   } 
   for (each entry)
   {
     char {X}     - Filename                         // XOR 0xBE      in version 24
     byte {1}     - null Filename Terminator         // 0xBE          in version 24
   }
 }

5. I have successfuly extracted all files from the archive. Sound (*.ogg) files play well, however some other files (scripts) seems to be encrypted. Further I am wholly confused with CRCs, HASHs and Paddings for now, so I can not build an modified archive.

MultiEx BMS Script

Not written yet

Supported by Programs

Documentation

None

Games

  • 3D Sex Villa *.bxp

Navigation

Jump to a listing by...
All Formats - Common Formats - Standard Formats - Malformed Pages
Platforms
Microsoft:
Xbox
Xbox 360
Nintendo:
GameCube
DS
Desktop:
PC
Sega:
Dreamcast
Sony:
PlayStation
PlayStation 2
PlayStation 3
PlayStation Portable
Type
Animation - Archive - Audio - Image - Mesh - Miscellaneous - Model - Video
Endianness
Little-endian - Big-endian
BMS Scripts
Pages Without a BMS Script

All Pages with Scripts:
Recently Added Scripts

Program Support
No Known Support

MultiEx Commander - Game Extractor

Format Specification Completion
Work in Progress - Almost Done - Completed
Compression and Encryption
No Compression or Encryption Used - Unknown Compression or Encryption Used

One or Both Used:
Compression Used - Both Compression and Encryption Used