Forum
Discordf3dex2
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
f3dex2 [2019/02/04 00:47] redetzky [E0: G_NOOP] |
f3dex2 [2019/05/12 21:25] trenavix Stupid example |
||
|---|---|---|---|
| Line 102: | Line 102: | ||
| This formula cannot be reversed for the value provided in the microcode, since the necessary information is absent. (Since the values are provided in the macro call generating this opcode, there's no guarantee any of the values match what they're "supposed" to be, e.g. //<color #ed1c24>near</color>// could be set to something far different from the location of the actual near clipping plane.) | This formula cannot be reversed for the value provided in the microcode, since the necessary information is absent. (Since the values are provided in the macro call generating this opcode, there's no guarantee any of the values match what they're "supposed" to be, e.g. //<color #ed1c24>near</color>// could be set to something far different from the location of the actual near clipping plane.) | ||
| + | |||
| + | **Note:** This command works differently in F3DZEX. | ||
| ---- | ---- | ||
| ==== 05: G_TRI1 ==== | ==== 05: G_TRI1 ==== | ||
| Line 114: | Line 116: | ||
| Example: Render a triangle using the vertex data specified at the vertex buffer positions 0, 1 (0x02 / 0x02) and 2 (0x04 / 0x02). | Example: Render a triangle using the vertex data specified at the vertex buffer positions 0, 1 (0x02 / 0x02) and 2 (0x04 / 0x02). | ||
| - | 05 00 02 04 00 00 02 04 | + | 05 00 02 04 00 00 00 00 |
| ---- | ---- | ||
f3dex2.txt ยท Last modified: 2020/02/26 14:17 by jesusyoshi54