Objects - Revision history

Mzxrules at 16:34, 23 March 2021

2021-03-23T16:34:23Z

Mzxrules at 20:35, 29 November 2019

2019-11-29T20:35:54Z

Mzxrules: /* Loading/Managing Object Files */

2019-01-29T22:02:02Z

‎Loading/Managing Object Files

Mzxrules: /* Anatomy of an Object File */

2018-06-18T00:55:07Z

‎Anatomy of an Object File

Mzxrules at 08:43, 14 November 2017

2017-11-14T08:43:03Z

Mzxrules: /* "Object Space" */ oops

2016-12-06T06:00:22Z

‎"Object Space": oops

Mzxrules: /* "Object Space" */ rip constants

2016-12-03T22:37:51Z

‎"Object Space": rip constants

Mzxrules at 20:42, 31 October 2016

2016-10-31T20:42:40Z

Mzxrules: no longer stubbly

2016-09-08T09:06:10Z

no longer stubbly

Mzxrules at 09:05, 8 September 2016

2016-09-08T09:05:49Z

@@ Line 9: / Line 9: @@
 Object files have no "format" per se, but contain different types of "static" data:
-* Display Lists, in the form of [[F3DZEX]] GBI (graphical binary interface).
+* Display Lists, in the form of [[F3DZEX2]] GBI (graphical binary interface).
 * Textures and palette data, typically referenced by said display lists
 * [[Animation Format|Animation Data]]

← Older revision		Revision as of 20:35, 29 November 2019
Line 1:		Line 1:
	{{article link\|Objects}}		{{article link\|Objects}}
−	~~{{for\|listing of object files\|Object Listings}}~~
	'''Object Files''' or '''Objects''' are files which primarily contain the graphical assets (display lists, textures) for actors, as well as animation data and collision surfaces for some actors.		'''Object Files''' or '''Objects''' are files which primarily contain the graphical assets (display lists, textures) for actors, as well as animation data and collision surfaces for some actors.

@@ Line 39: / Line 39: @@
 The process for filling this space is as follows. Note that all object files are inserted into the lowest start address available, with no "gaps" between each object file:
-* {{object ref|0001}} is always allocated first. Additionally, [[segment address]] 04 is set to it's start address.
+* {{object ref|0001}} is always allocated first. [[Segment address]] 04 is set to it's start address.
-* {{object ref|0002}} or {{object ref|0003}} is allocated, depending on the 0x07 [[Scenes and Rooms|scene header]] command. Additionally, segment address 05 is set to it's start address.
+* Optionally, {{object ref|0002}} or {{object ref|0003}} is allocated, depending on the 0x07 [[Scenes and Rooms|scene header]] command. Segment address 05 is set to it's start address, if loaded.
 * {{object ref|0014}} or {{object ref|0015}} is allocated, depending on whether Link should spawn as an adult or a child.
 After that, object files are allocated based on the order they appear in the 0x0B [[Scenes and Rooms|room header]] command of the room Link initially spawns in. Whenever Link travels between two rooms, the game will compare the objects that were loaded by the first room to the objects requested by the second, starting with the first object number in each list. When the game encounters a number that does not match, all object files after the last match will be de-allocated, and any missing object file requests pending for the second room will be allocated.
-An important thing to note about "Object Space" is that whenever the game is paused, this space is repurposed in order to store the pause screen's graphical files and object dependencies.
+An important thing to note about "Object Space" is that whenever the game is paused, this space is re-purposed in order to store the pause screen's graphical files and object dependencies.
 === GI Objects ===

@@ Line 13: / Line 13: @@
 * Textures and palette data, typically referenced by said display lists
 * [[Animation Format|Animation Data]]
-* [[Collision Format (Scenes)|Collision Surfaces]] for actors with complex collision (eg. odd shaped platforms, destructible walls)
+* [[Collision Mesh Format|Collision Surfaces]] for actors with complex collision (eg. odd shaped platforms, destructible walls)
 == Loading/Managing Object Files ==

@@ Line 2: / Line 2: @@
 {{for|listing of object files|Object Listings}}
 '''Object Files''' or '''Objects''' are files which primarily contain the graphical assets (display lists, textures) for actors, as well as animation data and collision surfaces for some actors.
 == Anatomy of an Object File ==

@@ Line 22: / Line 22: @@
 | 0xFA000 || Scene Index = 0x51 (Hyrule Field) <!-- Special Cased in code -->
 |-
-| 0x11F800 || Scene Index = 0x4F (Ganon Boss Fight), and Scene Setup is 4 (Tower Collapsing Cutscene)
+| 0x11F800 || Scene Index = 0x4F (Ganon Boss Fight), and Scene Setup is *not* 4 (Tower Collapsing Cutscene)
 |-
 |rowspan=3| 0x106800 || Scene Index = 0x17 (Spirit Temple Boss Room)

@@ Line 15: / Line 15: @@
 === "Object Space" ===
-The vast majority of object files are loaded into an 0xFA000 byte space (referred to as "Object Space"), located immediately before the start address of the current scene file. The process for filling this space is as follows. Note that all object files are inserted into the lowest start address available, with no "gaps" between each object file:
+The vast majority of object files are allocated to a space referred to as "Object Space", located immediately before the start address of the current scene file. The following table lists the size given to "Object Space":
 * {{object ref|0001}} is always allocated first. Additionally, [[segment address]] 04 is set to it's start address.
@@ Line 23: / Line 42: @@
 After that, object files are allocated based on the order they appear in the 0x0B [[Scenes and Rooms|room header]] command of the room Link initially spawns in. Whenever Link travels between two rooms, the game will compare the objects that were loaded by the first room to the objects requested by the second, starting with the first object number in each list. When the game encounters a number that does not match, all object files after the last match will be de-allocated, and any missing object file requests pending for the second room will be allocated.
 An important thing to note about "Object Space" is that whenever the game is paused, this space is repurposed in order to store the pause screen's graphical files and object dependencies.
 === GI Objects ===

← Older revision		Revision as of 09:06, 8 September 2016
Line 1:		Line 1:
−	~~{{stub}}~~
	{{article link\|Objects}}		{{article link\|Objects}}

@@ Line 2: / Line 2: @@
 {{article link|Objects}}
-'''Objects''' or '''Object Files''' are files which primarily contain the graphical assets (display lists, textures) for actors, as well as animation data and collision surfaces for some actors.
+'''Object Files''' or '''Objects''' are files which primarily contain the graphical assets (display lists, textures) for actors, as well as animation data and collision surfaces for some actors.
 == Loading/Managing Object Files ==
@@ Line 19: / Line 28: @@
 === GI Objects ===
 Whenever Link holds an item over his head, or pulls out an item to show it to an NPC, a GI_Object file (an object file containing a "high res" 3D model of an item) will be loaded into a much smaller space allocated after Link's instance before the item is shown.
 [[Category:Objects| ]]