Differences

This shows you the differences between two versions of the page.

--- falcon4:file_formats:cam_trn_tac:obj_file [2009/02/14 22:01] – created lightning
+++ falcon4:file_formats:cam_trn_tac:obj_file [2024/07/31 08:40] (current) – links added. snakeman
@@ Line 1: / Line 1: @@
-====== .OBJ file ======
+====== Falcon 4 .OBJ file ======
-The OBJ file holds all the objectives in a mission. Objectives are basically static things, like towns, cities, bridges, bases. Things which cannot be moved.
-Objectives are usually composed of features. Each feature being a particular part of the overall objective. So an airbase objective may have runway, hangar and control tower as features.
+[[https://www.pmctactical.org/forum/viewforum.php?f=47|Falcon 4.0 Forum]], [[:falcon4|Falcon 4 Home]], [[falcon4:campaign|Falcon 4 Campaign]], [[falcon4:cockpits|Falcon 4 Cockpits]], [[falcon4:database|Falcon 4 Database]], [[falcon4:file_formats|Falcon 4 File Formats]], [[falcon4:srtm|Falcon 4 SRTM Terrain]], [[falcon4:terrain|Falcon 4 Terrain]], [[falcon4:textures|Falcon 4 Textures]], [[falcon4:tools|Falcon 4 Tools]]
-Objectives also have a fixed position on the map governed by their X, Y coordinates. They may also have:
+The OBJ file holds all the objectives in a mission. Objectives are basically static things, like towns, cities, bridges, bases. Things which cannot be moved. \\
-a parent - an objective that they are a child of, used in the naming sometimes.
+Objectives are usually composed of features. Each feature being a particular part of the overall objective. So an airbase objective may have runway, hangar and control tower as features. \\
-a name - an index into the strings file used to name the objective. 0 indicates the objective has no name of its own.
-a campaign ID - ID2 - used to related things.
+Objectives also have a fixed position on the map governed by their X, Y coordinates. They may also have: \\
-an owner - which side owns this objective.
-a controller - which side actually controls the objective.
+a parent - an objective that they are a child of, used in the naming sometimes. \\
-a type - an index into the OCD file showing which objective type this is.
+a name - an index into the strings file used to name the objective. 0 indicates the objective has no name of its own. \\
-Various flags associated with the objective
+a campaign ID - ID2 - used to related things. \\
-Details of each feature composing the objective, detailing how damaged it is.
+an owner - which side owns this objective. \\
-A list of links to other objectives - this gives routes to other places.
+a controller - which side actually controls the objective. \\
+a type - an index into the OCD file showing which objective type this is. \\
+Various flags associated with the objective \\
+Details of each feature composing the objective, detailing how damaged it is. \\
+A list of links to other objectives - this gives routes to other places. \\
 ===== .OBJ File Format =====
@@ Line 20: / Line 23: @@
 ==== Raw (compressed contents) ====
 ^Field^Data Type^Width (in bytes)^Description^
-|NumObjectives |Signed 32-bit integer|4|Number of objective records in the data that follows|
+|NumObjectives |Signed 16-bit integer|2|Number of objective records in the data that follows|
 |UncompressedSize|Signed 32-bit integer|4|Size, in bytes, of the data that follows, when it's uncompressed|
 |CompressedSize |Signed 32-bit integer|4|Size, in bytes, of the compressed file to follow|
-|DATA|byte[]|(CompressedSize)|LZSS-compressed binary data.|
+|DATA|byte[]|(CompressedSize)|[[falcon4:file_formats:cam_trn_tac:lzss_compression|LZSS-compressed]] binary data.|
 ==== Uncompressed contents of the DATA field ====
@@ Line 74: / Line 77: @@
 |num_|unsigned 32-bit integer|4| |
 |creator_|unsigned 32-bit integer|4| |