Rendering - Revision history

Mzxrules: /* Graphics Context */

2021-08-06T16:48:56Z

‎Graphics Context

Mzxrules at 16:48, 6 August 2021

2021-08-06T16:48:17Z

Mzxrules: /* Graphics Context */

2018-03-24T20:36:42Z

‎Graphics Context

Mzxrules: /* Graphics Context */

2018-03-08T05:21:17Z

‎Graphics Context

Mzxrules: /* Graphics Context */ DMEM not IMEM

2018-03-08T05:20:58Z

‎Graphics Context: DMEM not IMEM

Mzxrules: /* Graphics Context */ rcp transfer stuff

2018-03-08T04:24:30Z

‎Graphics Context: rcp transfer stuff

Mzxrules: /* Graphics Context */ i'm dum

2016-11-23T22:11:39Z

‎Graphics Context: i'm dum

Mzxrules: /* Graphics Context */

2016-11-23T22:07:00Z

‎Graphics Context

Mzxrules: /* Graphics Context */

2016-11-22T18:11:27Z

‎Graphics Context

Mzxrules: /* Graphics Context */

2016-11-22T11:05:28Z

‎Graphics Context

@@ Line 107: / Line 107: @@
 | 02EC || ptr || Function Pointer || ?
 |-
-| 02F0 || ptr || [[Global Context]] ||
+| 02F0 || ptr || [[Game Struct]] ||
 |}

@@ Line 9: / Line 9: @@
 These four display lists have their own buffers, which can be used to write display list commands programmatically. To do so, each has a "append start" pointer and "append end" pointer, as seen in the table below. The "append start" pointer points to the next free spot for display list commands. In order to append a new display list, you simply write your instructions starting at the "append start" pointer, then increment the pointer past your instructions. The "append end" pointer points to the address past the end of the remaining buffer. This pointer is used to append data for commands that are programmatically set during that frame. For example, the perspective and camera matrices (used to transform 3D models to a 2D space) change every frame. To add the matrix data, the "append end" address is decremented by 0x40 (the size of the matrix), then the matrix is stored at the new "append end" address.
-Display list buffers should only be used to store instructions that cannot be pre-computed beforehand, since otherwise you'll be wasting cpu, time, and the limited buffer space.
+Display list buffers should only be used to store instructions that cannot be pre-computed beforehand, since otherwise you'll be wasting CPU, time, and the limited buffer space.
 == Graphics Context ==
-At [[Global Context]] + 0x0000 is a pointer to a struct located on the "graph" thread stack that contains data used to assist in rendering.
+At [[Game Struct]] + 0x00 within all [[Game States]] is a pointer to a struct located on the "graph" thread stack that contains data used to assist in rendering.
 {|class="wikitable"

@@ Line 35: / Line 35: @@
 | 008C || int || ?, set to 4 ||
 |-
-| 0090 || ptr || Microcode Ptr || ?
+| 0090 || ptr || Microcode Ptr || ?,
 |-
 | 0094 || int || Microcode Length || Length in bytes of the microcode sequence referenced by 0090
 |-
-| 0098 || ptr || Microcode Ptr || ?
+| 0098 || ptr || Microcode Ptr || ?, possibly F3DZEX
 |-
 | 00B8 || ptr || Completed WORK_DISP Start || branches to the DList task the RCP should be working on this cycle

@@ Line 49: / Line 49: @@
 | 00C4 || int || Unknown Buffer (0xC00) Size ||
 |-
-! colspan=4 | End RCP IMEM Transfer Struct
+! colspan=4 | End RCP DMEM Transfer Struct
 |-
 | 01B0 || ptr || Working WORK_DISP Start ||

@@ Line 29: / Line 29: @@
 | 005C || OSMesgQueue || ? || First OSMesg at 0038
 |-
-! colspan=4 | Next 0x40 bytes transferred to RCP IMEM addr 0xFC0
+! colspan=4 | Next 0x40 bytes transferred to RCP DMEM addr 0xFC0
 |-
 | 0088 || int || ?, set to 1 ||

@@ Line 76: / Line 76: @@
 |-
 | 02E8 || int || Frame Counter 2 || Used for swapping framebuffers
 |}

@@ Line 24: / Line 24: @@
 |-
 | 0014 || ptr || Working OVERLAY_DISP start ||
 |-
 | 00B8 || ptr || Completed WORK_DISP Start || branches to the DList task the RCP should be working on this cycle