MREA (Metroid Prime) - Revision history

Jackoalan at 05:57, 26 February 2017

2017-02-26T05:57:33Z

Aruki: /* Collision */

2016-12-29T23:46:44Z

‎Collision

Aruki at 02:03, 24 May 2016

2016-05-24T02:03:02Z

Aruki at 02:00, 24 May 2016

2016-05-24T02:00:15Z

Aruki at 02:02, 23 May 2016

2016-05-23T02:02:35Z

Aruki: /* World Geometry */

2016-05-23T02:01:48Z

‎World Geometry

Aruki: /* World Geometry */

2016-05-23T02:01:35Z

‎World Geometry

Aruki at 02:01, 23 May 2016

2016-05-23T02:01:20Z

Show changes

Aruki at 01:45, 23 May 2016

2016-05-23T01:45:57Z

Aruki: /* Geometry */

2016-02-21T06:20:43Z

‎Geometry

@@ Line 234: / Line 234: @@
 === Visibility Tree ===
-This section is labeled "VISI". Some areas don't have visibility trees; in that case this section will be completely empty and listed with a size of 0.
+{{main|VISI (MREA Section)}}
 === Path ===

@@ Line 222: / Line 222: @@
 === Collision ===
-{{todo|Format known, needs documentation written up.}}
+''Main article: [[Area Collision (File Format)]]''
 === Unknown Section ===

@@ Line 212: / Line 212: @@
 {{main|AROT (MREA Section)}}
-The AROT section stores the area's octree, accelerating back-to-front rendering of contained meshes, it is also used for spacial queries such as collision.
+The AROT section stores the area's octree, accelerating back-to-front rendering of contained meshes. It is also used for spacial queries such as collision.
 === Script Layers ===
-{{todo|SCLY is definitely complicated enough to need its own article.}}
+{{todo|Format known, needs documentation written up.}}
 The SCLY section contains data for objects.
@@ Line 222: / Line 222: @@
 === Collision ===
-{{todo|Collision needs a separate article because it shares so many similarities with DCLN. How should we document the parts where the format diverges, though?}}
+{{todo|Format known, needs documentation written up.}}
-−
-You have three guesses what the collision section is for, and the first two don't count.
 === Unknown Section ===
-This one is sandwiched between collision and lights, and usually just contains a single 32-bit "1". Purpose is unknown.
+This one is sandwiched between collision and lights, and usually just contains a single 32-bit "1". Purpose is unknown. In the Prime 3/DKCR MREA format, this section is labelled <code>LLTE</code>.
 === Lights ===
-This section is for dynamic lights, see the [[Lights_(Metroid_Prime)|Light]] article for details.
+This section is for dynamic lights. See the [[Lights_(Metroid_Prime)|Light]] article for details.
 === Visibility Tree ===
-This section is labeled "VISI". This section is sometimes not actually present in the file, labeled with a size of 0.
+This section is labeled "VISI". Some areas don't have visibility trees; in that case this section will be completely empty and listed with a size of 0.
 === Path ===
-This is the final section in the file; it's always 0x20 bytes, and its only value is a single [[PATH (File Format)|PATH]] file ID.
+This is the final section in the file; its only value is a single [[PATH (File Format)|PATH]] file ID.
-−
-== Tools ==
-* [https://drive.google.com/file/d/0B9MLV21H7SDvMk9PN1lrM1g3ZVE/view?usp=sharing Parax's MREA maxscript] can import MREA terrain geometry into 3DS Max.
+{| class="wikitable"
 [[Category:File Formats]]
 [[Category:Metroid Prime]]

@@ Line 9: / Line 9: @@
 Like [[CMDL (Metroid Prime)|CMDL]], MREA files are split up into a number of 32-byte aligned sections. Every section both starts and ends on a 32-byte boundary. These are used to separate different parts of the file; different types of sections typically indicate different sets of data. The header declares the section count and the size of each one; using these is the only way to navigate the file.
 === Header ===
@@ Line 106: / Line 137: @@
 |}
-=== Data Sections ===
+=== World Geometry ===
-−
-MREA data sections are in the file in the following order:
-−
-{| class="wikitable"
-! Identifier
-! Name
-|-
-| {{none}}
-| [[#World Geometry|World Geometry]]
-|-
-| <code>AROT</code>
-| [[#Area Octree|Area Octree]]
-|-
-| <code>SCLY</code>
-| [[#Script Layers|Script Layers]]
-|-
-| <code>0xDEAFBABE</code>
-| [[#Collision|Collision]]
-|-
-| {{none}}
-| {{unknown|[[#Unknown Section|Unknown]]}}
-|-
-| <code>0xBABEDEAD</code>
-| [[#Lights|Lights]]
-|-
-| <code>VISI</code>
-| [[#Visibility Tree|Visibility Tree]]
-|-
-| {{none}}
-| [[#Path|Path]]
-|}
-−
-==== World Geometry ====
 ''See [[Materials (Metroid Prime)]] and [[Geometry (Metroid Prime)]]''
@@ Line 179: / Line 177: @@
 |}
-===== Visor Flags =====
+==== Visor Flags ====
 {| class="wikitable"
@@ Line 210: / Line 208: @@
 |}
-==== Area Octree ====
+=== Area Octree ===
 {{main|AROT (MREA Section)}}
@@ Line 216: / Line 214: @@
 The AROT section stores the area's octree, accelerating back-to-front rendering of contained meshes, it is also used for spacial queries such as collision.
-==== Script Layers ====
+=== Script Layers ===
 {{todo|SCLY is definitely complicated enough to need its own article.}}
@@ Line 222: / Line 220: @@
 The SCLY section contains data for objects.
-==== Collision ====
+=== Collision ===
 {{todo|Collision needs a separate article because it shares so many similarities with DCLN. How should we document the parts where the format diverges, though?}}
@@ Line 228: / Line 226: @@
 You have three guesses what the collision section is for, and the first two don't count.
-==== Unknown Section ====
+=== Unknown Section ===
 This one is sandwiched between collision and lights, and usually just contains a single 32-bit "1". Purpose is unknown.
-==== Lights ====
+=== Lights ===
 This section is for dynamic lights, see the [[Lights_(Metroid_Prime)|Light]] article for details.
-==== Visibility Tree ====
+=== Visibility Tree ===
 This section is labeled "VISI". This section is sometimes not actually present in the file, labeled with a size of 0.
-==== Path ====
+=== Path ===
 This is the final section in the file; it's always 0x20 bytes, and its only value is a single [[PATH (File Format)|PATH]] file ID.

@@ Line 4: / Line 4: @@
 {{todo|There's a LOT of sections that are mostly known, but need some documentation written up. SCLY and collision need separate articles (although the unique parts of the collision format, like the octree, could maybe be documented here). The rest should probably stay on this page.}}
-{{research|minor|Discounting unknowns within the actual data sections, the only things that aren't known are what the .}}
+{{research|minor|Discounting unknowns within the actual data sections, the main thing that still isn't known is what the unknown data section is for.}}
 == Format ==

@@ Line 158: / Line 158: @@
 |-
 | 0x0
-| [[#Visor Flags]]
+| [[#Visor Flags|Visor Flags]]
 | 1
 | '''Visor Flags'''

@@ Line 176: / Line 176: @@
 |-
 | 0x4C
-| colspan=2 {{unknown|End of mesh header section}}
+| colspan=4 {{unknown|End of mesh header section}}
 |}

@@ Line 84: / Line 84: @@
 * Normals are ''always'' shorts, so vertex format 0 is never used.
 * Most MREA meshes use lightmaps, so normally the first UV coordinate on each vertex will read from the short UV array. This isn't always the case, though; you need to make sure you check the material so you know where to read from.
-* Surfaces will usually have a bounding box in the extra data in the submesh header. This bounding box is used for depth sorting.
+* Surfaces will usually have a bounding box in the extra data in the surface header. This bounding box is used for depth sorting.
 * Each mesh starts with an extra header section which is formatted like this: