F3DZEX2 - Revision history

Random06457 at 07:04, 6 May 2021

2021-05-06T07:04:51Z

Mzxrules: /* In RCP */

2021-03-23T15:56:27Z

‎In RCP

Mzxrules at 07:26, 10 September 2020

2020-09-10T07:26:56Z

PPLToast: strings, strings...

2020-09-06T09:07:35Z

strings, strings...

ShimmerFairy: Update references to F3DEX2, some notes on history.

2020-09-04T09:26:41Z

Update references to F3DEX2, some notes on history.

PPLToast: PPLToast moved page F3DZEX to F3DZEX2

2020-09-04T09:05:29Z

PPLToast moved page F3DZEX to F3DZEX2

PPLToast at 08:06, 4 September 2020

2020-09-04T08:06:59Z

Mzxrules: /* Color Combiner Settings */ Make table readable to humans without needing to rotate the screen

2019-10-15T21:08:47Z

‎Color Combiner Settings: Make table readable to humans without needing to rotate the screen

CloudMax: Updating table to use new color classes

2019-10-14T14:46:18Z

Updating table to use new color classes

CloudMax: Updating table to use new color classes

2019-10-14T14:39:17Z

Updating table to use new color classes

Show changes

@@ Line 414: / Line 414: @@
 The 16 bits that make up the cycle-dependent settings for the RDP blender specify what and how to actually blend things together. The blender runs on the formula
-     (P * A + M - B) / (A + B)
+     (P * A + M * B) / (A + B)
 to blend primitives into the framebuffer. The 16 bits specify the values of these variables for both cycles in the following layout:

@@ Line 234: / Line 234: @@
 ===In RCP===
-It's currently unknown how the vertex is stored in the RCP, after transformation and potential lighting calculations are performed. So far, it's only the enumerations given for opcode <tt>02</tt>, which are described in SDK comments as "byte offset[s] into point", which indicate a differing structure. Assuming the comment is true, then so far only this is known:
+The following vertex structure documentation is unconfirmed, and is based on documentation for Fast3D.
-  ?? ??  ?? ??  ?? ??  ?? ??    ?? ??  ?? ??  ?? ??  ?? ??
+  struct Vertex_RCP {
-  rr gg  bb aa  ss ss  tt tt    xx xx  yy yy  zz zz  00 00
+  /* 0x00 */ int16_t  xyzw_int[4];
+  /* 0x08 */ uint16_t xyzw_frac[4];
-with the RGBA color shown above always a color (if lighting is enabled, this will be the result of calculating the color), and the texture position coordinates post-transformation.
+  /* 0x10 */ u8 rgba[4]; // always a color. If lighting is enabled, this is the result of color calculations
 ==Matrix Structure==

@@ Line 1: / Line 1: @@
-'''F3DZEX2''' is a form of microcode for the RSP used by both Ocarina of Time and Majora's Mask. The name likely stands for "Fast 3D Zelda Extended", and appears to be most similar to the standard F3DEX2, if not identical to it.
+'''F3DZEX2''' is the primary 3D graphics microcode for the N64's Reality Signal Processor (RSP), used exclusively by both Ocarina of Time and Majora's Mask. It is a variant of the F3DEX2 (Fast 3D, Extended 2) microcode, containing a very similar (if not identical) binary interface.
 ==Differences from F3DEX2==
-The SDK given to all N64 developers includes several microcodes to load onto the Reality Signal Processor (RSP), one of which is the F3DEX2 3D graphics microcode (the latest iteration of Nintendo's 3D microcode offerings). The microcode used in N64 Zelda titles appears to be a variation of this microcode, though how exactly is unknown.
+The SDK given to all N64 developers includes several microcodes to load onto the RSP, one of which is the F3DEX2 3D graphics microcode (the latest iteration of Nintendo's 3D microcode offerings). The microcode used in N64 Zelda titles appears to be a variation of this microcode, though how exactly is unknown.
 The only known difference between the two is that the F3D'''Z'''EX2 readme encourages the use of the <tt>g*SPBranchLessZraw</tt> macros over the <tt>g*SPBranchLessZ</tt> macros (note that the <tt>Zraw</tt> form is available to developers using F3DEX2, but it's undocumented in the SDK). This doesn't explain the need for a separate compiled microcode, however, since these macros only differ in how a programmer specifies the Z value for the [[F3DZEX/Opcode_Details#0x04_—_G_BRANCH_Z|<tt>G_BRANCH_Z</tt>]] command.
-The readme for F3DZEX2 (as part of the iQue leak) reveals that this microcode required F3DEX2 to be installed first, with the Z-specific microcode object files and a <tt>ucode_z.h</tt> file installed on top of the F3DEX2 installation afterwards. This header file does not define any new macros or other new features over the standard F3DEX2 microcode, so the need for a Z-specific microcode object is not currently known. (It's also not known why the <tt>Zraw</tt> macro is part of the standard SDK if it was only mentioned to programmers using F3DZEX2, or why the readme doesn't bring up <tt>g*SPBranchLessZrg</tt> in its discussion of how to branch on the Z value.)
+The readme for F3DZEX2 (as part of the iQue leak) reveals that this microcode required F3DEX2 to be installed first, with the Z-specific microcode object files and a <tt>ucode_z.h</tt> file installed on top of the F3DEX2 installation afterwards. This header file does not define any new macros or other new features over the standard F3DEX2 microcode, so the need for a Z-specific microcode object is not currently known. It's also not known why the <tt>Zraw</tt> macro is part of the standard SDK if it was only mentioned to programmers using F3DZEX2, or why the readme doesn't bring up <tt>g*SPBranchLessZrg</tt> in its discussion of how to branch on the Z value.
 ==Versions Used==

@@ Line 12: / Line 12: @@
 The variation used in both OoT and MM is F3DZEX2.NoN.fifo, with "NoN" standing for No Near clipping (objects between the viewer and the near clipping plane are not clipped, and objects in this area aren't subject to Z buffer calculations), and "fifo" simply being a method of transferring commands to the RSP.
-Below is the version/copyright strings for F3DZEX2 present in Ocarina of Time. Note that the version strings claim the microcode as being "F3DZEX" microcode (which apparently did exist as the counterpart to F3DEX), but the iQue leak shows that the 2 was left out of the version string in F3DZEX2 object files.
+Below is the version/copyright strings for F3DZEX2 present in Ocarina of Time and Majora's Mask. Note that the version strings claim the microcode as being "F3DZEX" microcode (which apparently did exist as the counterpart to F3DEX), but the iQue leak shows that the 2 was left out of the version string in F3DZEX2 object files. The Japanese Nintendo 64 versions of Majora's Mask also contain an alternate string that lacks the credit to Kawasedo.
 {| class="wikitable"
 ! Version !! String
 |-
-! Nintendo 64
+! OoT Nintendo 64
 | <code style="white-space: pre;">RSP Gfx ucode F3DZEX.NoN  fifo 2.06H Yoshitaka Yasumoto 1998 Nintendo.</code>
 |-
-! GameCube
+! Majora's Mask JP N64 (Alt)
 | <code style="white-space: pre;">RSP Gfx ucode F3DZEX.NoN  fifo 2.08J Yoshitaka Yasumoto/Kawasedo 1999.</code>
 |}

@@ Line 1: / Line 1: @@
-'''F3DZEX''' is a form of microcode for the RSP used by both Ocarina of Time and Majora's Mask. The name most likely stands for "Fast 3D Zelda Extended", and appears to be most similar to the standard F3DEX2, if not identical to it.
+'''F3DZEX2''' is a form of microcode for the RSP used by both Ocarina of Time and Majora's Mask. The name likely stands for "Fast 3D Zelda Extended", and appears to be most similar to the standard F3DEX2, if not identical to it.
 ==Versions Used==
-The variation used in both OoT and MM is F3DZEX.NoN.fifo, with "NoN" standing for No Near clipping (objects between the viewer and the near clipping plane are not clipped, and objects in this area aren't subject to Z buffer calculations), and "fifo" simply being a method of transferring commands to the RSP.
+The variation used in both OoT and MM is F3DZEX2.NoN.fifo, with "NoN" standing for No Near clipping (objects between the viewer and the near clipping plane are not clipped, and objects in this area aren't subject to Z buffer calculations), and "fifo" simply being a method of transferring commands to the RSP.
-Below is the version/copyright strings for F3DZEX present in Ocarina of Time.
+Below is the version/copyright strings for F3DZEX2 present in Ocarina of Time. Note that the version strings claim the microcode as being "F3DZEX" microcode (which apparently did exist as the counterpart to F3DEX), but the iQue leak shows that the 2 was left out of the version string in F3DZEX2 object files.
 {| class="wikitable"

← Older revision	Revision as of 09:05, 4 September 2020
(No difference)

@@ Line 526: / Line 526: @@
 The configuration of this is done by [[F3DZEX/Opcode_Details#0xFC_—_G_SETCOMBINE|opcode <tt>FC</tt>]], and the values they take vary based on which parameter you're configuring for. A chart of valid configuration values is below:
-{| class="wikitable" style="text-align: center;"
+{| class="wikitable" {{ts|ac|ml5|font-family: monospace}}
-! Parameter
+! Parameter || Color A || Color B || Color C || Color D || Alpha A || Alpha B || Alpha C || Alpha D
 |-
 |}
 Note that, in SDK code, <tt>G_CCMUX_0</tt> is actually defined as <tt>0x1F</tt>, with the value ANDed to the right number of bits for the particular parameter. The other values the various <tt>G_CCMUX_0</tt> options occupy in each parameter are specified in other parts of SDK documentation.

@@ Line 537: / Line 537: @@
 |rowspan=4| {{vertical|<tt>G_CCMUX_SHADE</tt>}} ||rowspan=4| {{vertical|<tt>G_CCMUX_ENVIRONMENT</tt>}} || {{vertical|<tt>G_CCMUX_1</tt>}} || {{vertical|<tt>G_CCMUX_NOISE</tt>}}
 |colspan=8| <tt>G_CCMUX_0</tt>
-|colspan=16 style="background-color:#e2e2e2"|
+|colspan=16 class="bg-empty"|
 |-style="height:8em;"
 ! Color B
@@ Line 543: / Line 543: @@
 | {{vertical|<tt>G_CCMUX_CENTER</tt>}} || {{vertical|<tt>G_CCMUX_K4</tt>}}
 |colspan=8| <tt>G_CCMUX_0</tt>
-|colspan=16 style="background-color:#e2e2e2"|
+|colspan=16 class="bg-empty"|
 |-style="height:12em;"
 ! Color C
@@ Line 555: / Line 555: @@
 <!-- first 6 from above -->
 | {{vertical|<tt>G_CCMUX_1</tt>}} || {{vertical|<tt>G_CCMUX_0</tt>}}
-|colspan=24 style="background-color:#e2e2e2"|
+|colspan=24 class="bg-empty"|
 |-style="border-top-width: 2px; height:4.5em;"
 ! Alpha A
 |rowspan=2| {{vertical|<tt>G_ACMUX_COMBINED</tt>}} ||rowspan=4| {{vertical|<tt>G_ACMUX_TEXEL0</tt>}} ||rowspan=4| {{vertical|<tt>G_ACMUX_TEXEL1</tt>}} ||rowspan=4| {{vertical|<tt>G_ACMUX_PRIMITIVE</tt>}}
 |rowspan=4| {{vertical|<tt>G_ACMUX_SHADE</tt>}} ||rowspan=4| {{vertical|<tt>G_ACMUX_ENVIRONMENT</tt>}} ||rowspan=2| {{vertical|<tt>G_ACMUX_1</tt>}} ||rowspan=4| {{vertical|<tt>G_ACMUX_0</tt>}}
-|colspan=24 style="background-color:#e2e2e2"|
+|colspan=24 class="bg-empty"|
 |-style="height: 4.5em;"
 ! Alpha B
-|colspan=24 style="background-color:#e2e2e2"|
+|colspan=24 class="bg-empty"|
 |-style="height: 11em;"
 ! Alpha C
 | {{vertical|<tt>G_ACMUX_LOD_FRACTION</tt>}} <!-- next 5 from above -->
 | {{vertical|<tt>G_ACMUX_PRIM_LOD_FRAC</tt>}} <!-- next from above -->
-|colspan=24 style="background-color:#e2e2e2"|
+|colspan=24 class="bg-empty"|
 |-style="height: 9em;"
 !Alpha D
 | {{vertical|<tt>G_ACMUX_COMBINED</tt>}} <!-- next 5 from above -->
 | {{vertical|<tt>G_ACMUX_1</tt>}} <!-- next from above -->
-|colspan=24 style="background-color:#e2e2e2"|
+|colspan=24 class="bg-empty"|
 |-
 |}