Difference between revisions of "Talk:FA1C39F7"

Revision as of 21:32, 19 October 2010

Say What?

I`ve been investigating this record format because it is one of the most numerous formats in a lot file that I believe is corrupted. Unfortunately, I have been having some difficulty with the record format as described here. Still, I have been able to decode nearly all of it. However, as my understanding of the record format has improved, I have discovered that the data I am seeing does not quite match the description. In the hope that someone could help me [Please?], and that my experience might help others, and not wanting to mess up the existing description with my misunderstandings, I documented my observations here. Even though my understanding of the format has improved considerably since originaly posting this commentary, and I have updated my description to match, I am still working on this record at the time of writing.

I start with some relatively simple structures that occur a variable number of times in the record, and build my way up towards the full description:

I call these blocks "Slot" blocks because some of the "Name" fields actually have the word "slot" as part of their value, and because the co-ordinates they contain often [if not always] make perfect sense as the object-relative locations of the object features mentioned in the correspoding "Name" field.

I had to invent a name for these blocks, but was singularly uninspired at the time. Any suggestions?

Notes

After the main block, additional data occurs that varies with the type and version of the outermost block, but which does NOT appear after a block of the same type and version within another block.

• cObject blocks:

When the main block is a cObject block of version 16, it is sometimes followed by a single additional DWORD [always 0x00FE0000?].

When the main block is a cObject block of version 17, it is followed by one of the following:

• Nothing at all. Always marks the end of the record.
• A single DWORD, always 0x00FE0000. Always marks the end of the record.
• A DWORD Count [usually 0] with Count additional DWORDs. Always marks the end of the record.
• A DWORD Count [always 2?] with Count Blend blocks describing a platter of Appetizers, Cheese, or Chips.

Other versions of cObject blocks have not been seen.

• cAnimatable blocks:

When the main block is a cAnimatable block of version 16, it is always followed by one of the following, all of which mark the end of the record:

• Nothing at all.
• A single DWORD, always either 0x00FE0000 or 0xFD000000.
• A DWORD Count with Count additional DWORDs.
• A DWORD Count with Count Anim blocks.

When the main block is a cAnimatable block of version 17, it is always followed by one additional DWORD, always 0x00000000.

When the main block is a cAnimatable block of version 14, the format is unknown.

Other versions of cAnimatable blocks have not been seen. At this time, it appears that version 14 blocks never occur as the main block, as this should cause my tool to raise an exception that has not occured. As well, the existance of version 17 blocks needs to be verified.

• cPerson and cLocomotable blocks.

Because of the way that cPerson and cLocomotable blocks always occur only with a single instance of the other, it is impossible to determine if any data present belongs to the cPerson block or the cLocomotable block. At any rate, the cLocomotable block`s embedded cAnimatable block has been observed to be followed by any of the following:

• Two DWORDs, always one of

• 0x00000000, 0x00000000
• 0x00000001, 0x00000000
• 0x00000001, 0x00FE0000

Always marks the end of the record.

• A single DWORD 0x1D000000 followed by some unknown data containing a 7BITSTR "Routing - Eye Attractor " plus a decimal number in parentheses.
• A single DWORD 0x2B000000 followed by some unknown data containing a 7BITSTR mentioning a Sim by neighborhood and Character file name, a decimal number in parentheses, and "(glasses_grip)". Always marks the end of the record.
• A DWORD Count with Count Anim blocks, optionally followed by:

• Nothing at all. Always marks the end of the record.
• Two DWORDS, always one of
• 0x00000000, 0x00000000
• 0x00000001, 0x00000000

Other data may follow the Anim blocks, or appear in place of them, but this data has proven very resistant to analysis.

As part of my ongoing investigation, I have used my tool to test-read every lot in neighborhoods E001 and F001 and begun scanning the lots in neighborhoods G001, N001, N002, and N003, and still have some troubles with the data following the cLocomotable`s embedded cAnimatable block. As of the last scan of the file it resides in, at least one cPerson record had a Anim-block count of 3, followed by TWO Anim blocks and something that clearly is NOT an Anim block. The record in question is Neighborhoods\G001\Lots\G001_Lot23.package, TypeID=0xFA1C39F7, GroupID=4294967295, InstanceID=218. Several other files have what appears to be one or more of these non-Anim blocks at the end of one or more cPerson records, but so far I have only found the one record with such within the *counted* Anim blocks.

I still don`t know how to identify the presence of the Anim blocks by any way other than checking for the length of the unused data at the end of the record, but that method had proven absolutely reliable until that one abberant record was found, and has proven reilable for all other records observed to date. --GeneralOperationsDirector