(02-12-2013, 08:20 AM)TheShyGuy Wrote: I've had a bit of experience with binary files from my ssbb hacking days and it won't be too hard to make my own. It might be a bit time consuming though...

• Header data
  for each object type
  • Identifier for object (anythings fine so long as you can tell what it is while loading)
    for each instance of object
    • a true bool
      object data
      
    a false bool (to tell the load loop to stop loading this type of object)
    
  Footer data
  

Spoiler

• Header
  
  • Relocation Tables
    
  • Raw Data
    
  • String table
    

(below)
nts -> null terminated string
#-> number of bytes

Header:
(nts) Tag
(4)Size of file
(4 * x)relocation table offset(s) -> x depends on type of data file
For a ssbb model, it would've included tables for vertices, the bone tree hierarchy, the string table, one for the polygons...etc.

Relocation Table:
(4)entry count
(4 * x)entry offsets

Raw DataLets says this is just a sprite with a source rectangle and name of the sprite sheet for the source sprite)
(4)name offset(local?/global?)
(4)X
(4)Y
(4)Width
(4)Height

String Table(null terminated strings)
(4) entry count
(nts * x) name ("Shy Guy Sprite Sheet")

Quote:binary reader / writer doesn't deal in bits, you should never need to play with them for a modern game unless your doing very low level work. (or your using flags or doing some specialised math)
C# dont use unsafe pointers, reference types (class / array) do the job of pointers and unsafe code as the name suggests is not a common practice in C#.

BinaryWriter Wrote:int num = 5;
BinaryWriter.Write(num)

Quote:int index = 0;
byte[] buffer = new byte[4]
BinaryDataHelper.Write(buffer,ref index, num);

Spoiler

Bit shifting Wrote:class BinaryDataHelper
{
public void Write(byte[] buffer, ref int index, int num)
{
buffer[index++] = (byte)(num >> 0);
buffer[index++] = (byte)(num >> 8);
buffer[index++] = (byte)(num >> 16);
buffer[index++] = (byte)(num >> 24);
}
public void Write(byte* buffer, ref int index, int num)
{
buffer[index++] = (byte)(num >> 0);
buffer[index++] = (byte)(num >> 8);
buffer[index++] = (byte)(num >> 16);
buffer[index++] = (byte)(num >> 24);
}
public void Read(byte[] buffer, ref int index,out int num)
{
num = buffer[index++] << 0 |
buffer[index++] << 8 |
buffer[index++] << 16 |
buffer[index++] << 24;
}
}

' Wrote:size of file you dont need, so long as your save and load loops aren't all over the place your load loop should never even have the option of reading past the end of file.
relocation table? I'm not familiar with the concept, if it offsets loaded positions then forget it, single floating point values will suffice, just save the original positions.