Most recent edit on 2011-03-03 11:02:40 by Gleem!

Additions:
8-1: Byte (1 Byte) - RawRefcount ( if > 1, then Refcount is this value -1, otherwise 0)

8-x: Byte (3 Byte) - Padding
9: Int32 (4 Byte) - # of Oversize Int32's after fixed portion, set 1
10: Int32 (4 Byte) - # of Oversize Int32's after fixed portion, set 2. [0,1,2]
15: Int32 (4 Byte) - Reference to next item's SectionID. [Or -1 for the end ?]
17: Int32 (4 Byte) - [Usually 200] May relate to display size of block in LH's Original Editor ?
Location 8-1 controls the count of the following data:
Oversize set 1: Location 9 controls the count of the following data
Oversize set 2: Location 10 controls the count of the following data

Deletions:
8: Int32 (4 Byte) - Unknown. [1,2]
9: Int32 (4 Byte) - # of Oversize Int32's after fixed portion
10: Int32 (4 Byte) - Unknown. [0,1,2]
15: Int32 (4 Byte) - Reference to another Type's SectionID. [Or -1 for the end ?]
17: Int32 (4 Byte) - [-1, 0, 1]
18: Int32 (4 Byte) - [Usually 200] May relate to display size of block in LH's Original Editor ?
Oversize: Location 9 controls the count of the following data

---

Edited on 2011-02-10 02:20:44 by Gleem!

Additions:

---

---

---

3: Int32 (4 byte) - Subtype
4: Single (4 byte) - Lot X position
5: Single (4 byte) - Lot Y position
6: Single (4 byte) - Lot Z position
7: Single (4 byte) - Lot Z Angle
8: Byte(1 byte) - [1-6] Path Set Count ( + 3 bytes padding)

9: Int32 (4 byte) - Link1 Count
10: Int32 (4 byte) - Link2 Count
13: Int32 (4 byte) - SyncBitflag
15: Int32 (4 byte) - Branch name TextElement Index (-1, -2, and -3 are special cases... maybe random choices?)
16: Byte (1 byte) - Branch Count [1-10]
TotalPaths = ((Path Set Count) x (Branch Count)) + (Path Set Count)

There seems to be an extra 'default' path set, as well as each branch choice. Perhaps to offer a straight linked-list path through a timeline

To read the next sections, you have to loop in the following manner
for j = 0 to Branch Count

for k = 0 to Path Set Count -1

Int32 (4 byte) - NextItem
Int32 (4 byte) - Path Index
Int32 (4 byte) - Unknown

for l = 0 to Branch Count -1

Single (4 byte) - Probability value?

---

---

---

---

---

---

Deletions:
3: Int32 (4 byte) - Unknown. [0,2]. Actor ?

7: Single (4 byte) - Unknown. Rotation or Scale ?
8: Int32 (4 byte) - [1-6] Controls Oversize.
9: Int32 (4 byte) - [Always 0]
10: Int32 (4 byte) - [Always 0]
15: Int32 (4 byte) - Unknown. [-3,-2,-1, 0-34, 36-39, 42-44, 46, 49, 52]
16: Byte (1 byte) - Controls count of singles at end of this structure. [1-10]
Count of (Loc 8) * ((Loc 16) +1) data in the following format:
Int32 (4 bytes) - Reference to another Type's SectionID, or -1.
Int32 (4 bytes) - Unknown. [-1,0,1]
Int32 (4 bytes) - Unknown. [120]
Count of Loc 16 data follows:
Single (4 bytes) - [.5,.3333,.25, .2,.1]

---

Edited on 2007-05-22 14:59:47 by Gleem!

Additions:
Refer to the FlmMainHeader page to read more technical details.

Categories

Deletions:
0x000; Int32; 4 ; Header Size; Number of bytes in the entire Header section; ; 0x004; Int32; 4 ; Magic Number; 18 for Original Movies, 19 for S & E Addon; 18, 19;
0x008; Int32; 4 ; Text Element Size; Number of bytes in Entire TextElementOffsets Section plus Entire TextElement Section; ;
0x00C; Int32; 4 ; CrewTE; Index of Crew TextElement; ;
0x010; Int32; 4 ; ; ; Always -1 ;
0x014; Single; 4 ; Year Start; Year the scene first is available; Usually 0, meaning always available.;
0x018; Single; 4 ; Year End; Year the scene is no longer available ? ; Usually 0, meaning no end;
0x01C; Single; 4 ; Trickiness?; Not sure what trickiness is.. if this is even it. Term appears in some INI files.; 0 - .82;
0x020; Int32; 4 ; ; ; Always -1 ;
0x024; Int32; 4 ; ; ; Always -1 ;
0x028; Int32; 4 ; ; ; Always -1 ;
0x02C; Byte; 1 ; Genre Count; Number of Genres in TE; ;
0x02D; Byte; 1 ; EnviroPyro Count; Number of CraneRig or Pyrotechnics; never more than 1;
0x02E; Byte; 1 ; TE Count; Number of elements in TextElements Section; max limit of 255;
0x02F; Byte; 1 ; Slider Count; Number of Slider entries; max limit of 255;
0x030; Int16; 2 ; Start Frame; What frame 'filming' starts on; 0 in special cases, or 70-546;
0x032; Int16; 2 ; Element Count; Number of Elements that are not Timeline Heads; 1-90;
0x034; Byte; 1 ; Direction Count; Number of Directors directions; ;
0x035; Byte; 1 ; Edit Flags; Bit Flags: 1 = Unk, 2 = Has Slider, 4 = Has Extras, 8 = Dolly, 16 = Crane; Always 6,14, or 22;
0x036; Byte; 1 ; Timeline Head Count; Number of Elements that are Timeline Heads; 1-20;
0x037; Byte ;1 ; Extra Count; Number of TextElements Extra flm file names. See Extras Section; ;
0x038; Int32; 4 ; Shot TE; References TE Index for a [Shot:xxx] entry or Trailer in certain ai_ flm files; Usually -1;
"
}}

---

Edited on 2007-05-22 14:53:36 by Gleem!

Additions:
CategoryFlmFormat

---

Edited on 2007-05-22 13:07:29 by Gleem! [Thinking of working some on this, but got distracted by other things :)]

Additions:
0x000; Int32; 4 ; PyroTE; contains the TextElement Index for a TE that says 'environmental_pyrotechnics' or 'rig_crane'. May be to indicate whether specialized crew is required and/or indicate usage of LotView props like the camera dolly.; ;

"}}

Deletions:
Int32 (4 bytes) - contains the TextElement Index for a special kind of prop (?)

---

Edited on 2007-03-27 01:59:14 by Gleem! [Changing all into to easier to read Tables]

Additions:
0x038; Int32; 4 ; Shot TE; References TE Index for a [Shot:xxx] entry or Trailer in certain ai_ flm files; Usually -1;

0x000; Int32; 4 ; Extra TE; contains the TextElement Index for a flm file name for an Extra to perform; ; "}}

Deletions:
0x038: Int32; 4 ; Shot TE; References TE Index for a [Shot:xxx] entry or Trailer in certain ai_ flm files; Usually -1

Int32 (4 bytes) - contains the TextElement Index for a flm file name for an Extra to perform.

---

Edited on 2007-03-27 01:53:41 by Gleem!

Additions:
The first part is a fixed-size of 60 Bytes. It contains all the significant information for the rest of the file.

Offset	Type	Size (bytes)	Field Name	Description	Typical Values
0x000	Int32	4	Header Size	Number of bytes in the entire Header section
0x004	Int32	4	Magic Number	18 for Original Movies, 19 for S & E Addon	18, 19
0x008	Int32	4	Text Element Size	Number of bytes in Entire TextElementOffsets Section plus Entire TextElement Section
0x00C	Int32	4	CrewTE	Index of Crew TextElement
0x010	Int32	4			Always -1
0x014	Single	4	Year Start	Year the scene first is available	Usually 0, meaning always available.
0x018	Single	4	Year End	Year the scene is no longer available ?	Usually 0, meaning no end
0x01C	Single	4	Trickiness?	Not sure what trickiness is.. if this is even it. Term appears in some INI files.	0 - .82
0x020	Int32	4			Always -1
0x024	Int32	4			Always -1
0x028	Int32	4			Always -1
0x02C	Byte	1	Genre Count	Number of Genres in TE
0x02D	Byte	1	EnviroPyro Count	Number of CraneRig or Pyrotechnics	never more than 1
0x02E	Byte	1	TE Count	Number of elements in TextElements Section	max limit of 255
0x02F	Byte	1	Slider Count	Number of Slider entries	max limit of 255
0x030	Int16	2	Start Frame	What frame 'filming' starts on	0 in special cases, or 70-546
0x032	Int16	2	Element Count	Number of Elements that are not Timeline Heads	1-90
0x034	Byte	1	Direction Count	Number of Directors directions
0x035	Byte	1	Edit Flags	Bit Flags: 1 = Unk, 2 = Has Slider, 4 = Has Extras, 8 = Dolly, 16 = Crane	Always 6,14, or 22
0x036	Byte	1	Timeline Head Count	Number of Elements that are Timeline Heads	1-20
0x037	Byte	1	Extra Count	Number of TextElements Extra flm file names. See Extras Section
0x038: Int32	4	Shot TE	References TE Index for a [Shot:xxx] entry or Trailer in certain ai_ flm files	Usually -1

This section's number of elements is determined by the Extra Count in the Main Header. The data is the Text Element Index, starting at zero for the first Text Element. Usually the Text Elements for extras are named "023_x_A" which relates to a flm file, without the .flm extension. Any flm file from any set *can* be used, but unpredictable results happen. If the count is zero, there is no data in this section.

Deletions:
The first part is a fixed-size of 60 Bytes. It most likely contains all the significant information for the rest of the file.

0: Int32 (4 bytes) - # of bytes in the entire MainHeader section (or offset to next section, if you like)
1: Int32 (4 bytes) - Always 18
2: Int32 (4 bytes) - # of bytes in Entire 'TextElementOffsets' Section plus Entire 'TextElement' Section

(or offset to next section after TextElements Section)

3: Int32 (4 bytes) - Count of Text Element entries
4: Int32 (4 bytes) - Always -1 (FF FF FF FF in hex)
5: Single (4 bytes) - Year Appearing.

[Usually 0. 1900 in _2_critical_conversation, 1950 in 001_scan_for_aliens, 1985 in _firing_blanks]

6: Single (4 bytes) - [0 or 1]
7: Single (4 bytes) - [0 - .82] Trickiness?
8: Int32 (4 bytes) - Always -1 (FF FF FF FF in hex)
9: Int32 (4 bytes) - Always -1 (FF FF FF FF in hex)
10: Int32 (4 bytes) - Always -1 (FF FF FF FF in hex)
11: Byte (1 byte) - # of TextElement elements related to a Genre
12: Byte (1 byte) - # of TextElement elements regarding use of the CraneRig or Pyrotechnics ?
13: Byte (1 byte) - # of elements in TextElementOffsets Section (and # of elements in TextElement Section)

so there is a maximum limit of 255 TextElements

14: Byte (1 byte) - # of Slider entries (and # of EndBlock -1 entries)
15: Int16 (2 byte) - Unknown. [0, or 70-546].

0 only in extra flm's like 005_x_chatters_1.flm, and crew flm's like 006_crew_00.flm. Camera ?

16: Int16 (2 byte) - Unknown [1-90]
17: Byte (1 byte) - # of Direction Entries
18: Byte (1 byte) - Unknown. [Always 6,14, or 22]
19: Byte (1 byte) - Unknown. [1-20]
20: Byte (1 byte) - # of TextElements relating to Extras. See Extras Section
21: Int32 (4 byte) - Usually -1, but can reference the TextElement Index for the "[Shot:xxx]" entry

or "Trailer" in certain ai_ flm files.

This section's number of elements is determined by the byte (20) in the Main Header. The data is the Text Element Index, starting at zero for the first Text Element. Usually the Text Elements for extras are named "023_x_A" which relates to a flm file. Any flm file from any set *can* be used, but unpredictable results happen. If the Header byte is zero, there is no data in this section.

---

Oldest known version of this page was edited on 2007-03-26 09:16:44 by Reacher []

The Movies .flm Format

The Main Header of the Lionhead flm File is 60 bytes, then there are dynamic sections based upon various values in the first 60 bytes. Technically, I suppose the first four bytes give the entire length of this header, but I have divided up the dynamic sections for ease of interpretation.

This is the way I broke down the flm file format into following Sections:

Main Header:

The first part is a fixed-size of 60 Bytes. It most likely contains all the significant information for the rest of the file.

Extras Section

This section's number of elements is determined by the byte (20) in the Main Header. The data is the Text Element Index, starting at zero for the first Text Element. Usually the Text Elements for extras are named "023_x_A" which relates to a flm file. Any flm file from any set *can* be used, but unpredictable results happen. If the Header byte is zero, there is no data in this section.

Each entry is :

Pyrotechnics Section

This section's number of elements is determined by the byte (12) in the Main header. The data is the Text Element Index. This only appears in a handful of flm files, and where there is one, there is always only one entry. Usually the Text Element is named 'environmental_pyrotechnics' or 'rig_crane'. If the header byte is zero, there is no data in this section.

Each entry is :

Genres Section

This section's number of elements is determined by the byte (11) in the Main Header. The data is the Text Element Index relating to the Genre named by the Text Element. If the Header byte is zero, there is no data in this section.

Each entry is:

TextElementOffset Section

This section's number of elements is determined by the byte (13) in the Main Header. The data is a list of offsets from this section's start to the end of each TextElement. The first entry is the size in bytes of the entire section, followed by a list of offsets. Or another way to think about it is that the difference between the current TEO (TextElementOffset) and the next, is the length in characters of the corresponding string at the same Index position in the next section -- the TextElement section.

Each entry is:

TextElement Section

This section's number of elements is the same as the previous, and is determined by the byte (13) in the Main Header. The data is a list of null-terminated strings (ending with Chr(0)) describing the list of various elements comprising the flm animation. There are so many different aspects in every animation, and this section reflects that. The order fo their appearance, if there is one, is unknown at this time. Their Indexes are derived from their position in the list, with zero as the first.


[A separate wikipage might be better suited for defining what these are and what they do, as they become known.]

The last element is padded with nulls to the next 4-byte boundary.

Each entry is:

Direction Section

This section's number of elements comes from the byte in the Main Header. Each element is a reference to the TextElement for 'action', 'cut', 'take_end' and 'dummy_extra'.

Each entry is:

Sliders Section

This section contains the slider definitions. The number of entries is partially controlled by MainHeader Loc 14. If it is zero, there is no data in this section. Header 14 determines how many TextElements will be read. How the section is defined is dependent upon the data in TextElements. Each element corresponds with a TextElement, starting at the first one. Unless the TE starts with 'sld_', the value is 0 (or should be...I think there is actually an error in LH's definition for 015_subway_entrance.flm!). If the TE data starts with 'sld_', then the data is the Slider Pos Count. The next Sliders elements (to Slider Pos Count) are the TE indexes that relate to the positions of that slider, which are LHTS string database identifiers. All elements are Int32s. I believe the TE's that aren't sliders in this section, are actually variable names used by the AMM.

For example, from 037_miniature_saucer.flm:
TE VALUE SLIDER DATA NOTES
endshoot 0
ai_ended_by_user 0
ai_director_mood 0
ai_actor_mood 0
ai_crew_speed 0
sld_duration 3 count of Slider Positions
FLT_TIME_SHORT 7 Value is the TE index for FLT_TIME_SHORT
FLT_TIME_MEDIUM 8 Value is the TE Index
FLT_TIME_LONG 9 Value is the TE Index
sld_scifi_miniature 2 count of Slider Positions
FLT_MINIATURE_SCIFI_FLYING 10 Value is the TE Index
FLT_MINIATURE_SCIFI_TURBULENCE 11 Value is the TE Index

EndBlock Section

This section contains Int32s all with the value of -1, count determined by MainHeader Loc 14.

Types Sections

The following sections from here to the end of the file are one of 10 types (0 through 9). Each type has its own structure. Some of the structures are fixed size, some are variable. What they control and how they are inter-linked is still mostly unknown at the moment. They control the parameters of the scene, such as camera position, actor position, timing, etc.
Each starts with the same format: an Int32 for the Type, an Int32 for the size of the structure, an Int32 for the ID of the section.