Originally posted by paulguy

---

Since when is TT64 cross platform compatible?

---

---

----------------------------

| Polygon drawing Commands |

----------------------------



[F3] [00 0,0 00] 07 [7F F][1 00]



[1] : F3 = command to load the texture into the texture memory along with more settings 

[2,3,4] : the s, t coordinates of the upper left corner of the texture tile in fixed point

format (not used?)

[5] : the tile number on the lower 3 bits

[6,7,8]: width and height of texture represented as a slant. hhhwww

width=256/www*32

height=hhh/32/width



------------------------------------



[FD] [10] 00 00 [09] [00 48 00]



[1]: FD = load texture

[3] : format/pixel size fffpp000

f = format

RGBA = 000 (there are other options)

p = storage size of 1 texel

16 bits = 10 (other options too)

0 = unused



[5]: RAM segment number

[6,7,8]: Offset in segment



------------------------------------



[03] [88] [00 10] [08] [00 C0 90]



[1]: 03= Load color for next triangles.

[2]: When is 0x86, loads the bright color, when 0x88(?) loads darkened color.

[3,4]: ??

[5]: RAM segment number

[6,7,8]: Offset in segment

(colors referred are in 32-bit RGBA format 8888)



------------------------------------



[04] [B0] [00 C0] [07 00 BD 50]



[1]: 04= Loads a chunk of vertices into RSP (The RSP cannot contain too much vertices)

[2] : number of vertices minus one in the high nibble and where in the vertex cache to load in

the low nibble 

(eg 0xb+1= 0xc=12 vertices loaded into index 0)

[3,4] : number of bytes of vertex data to load( 16(dec) for each vertex) (redundant?)

[5]: RAM segment number

[6,7,8]: Offset in segment and base address for next triangles.



------------------------------------



[F5] [00 00 00 00 00 00 00]



[1]: F5= Texture mode

[2,8]: Texture mode bits: lllkk.jj jjjjjjji iiiiiiii .....hhh ggggffee eeddddcc bbbbaaaaa

ff= Clamping S coord (cms)

cc= Clamping T coord (cmt)

bbbb= Mask offset S coord (masks)

eeee= Mask offset T coord (maskt)



------------------------------------



[B6] [00 00 00] [00 00] [00 00]



[1]: B6= Clears geometry mode

[5,6]: Culling and other settings, 16-bits= ??ab???? ???????? where a=culling back and b=culling front

[7,8]: Other geometry settings, 16-bits



------------------------------------



[B7] [00 00 00] [00 00] [00 00]



[1]: B7= Clears geometry mode

[5,6]: Culling and other settings, 16-bits= ??ab???? ???????? where a=culling back and b=culling front

[7,8]: Other geometry settings, 16-bits



------------------------------------



[BF] [00 00 00] [00] [28 32 3C]



[1] : BF= Triangle command

[2,3,4] : mean nothing and are likely ignored

[5] : vertex to get normal or color from for flat shading, if flat shading is used; seems to

always be 0.

[6,7,8] : vertex number times 10(dec) 



------------------------------------



[06] 00 00 00 [04] [00 CA 00]



[1]: 06= Jumps to another point in the triangle data. 

[2,3,4]:??

[5]: RAM segment number

[6,7,8]: Offset in segment



------------------------------------



[B8] [00 00 00 00 00 00 00]



[1]: B8: Command that jumps back to the next command after the last "06" jump (uses a stack)

[2-8]: always zero



------------------------------------



[E6] [00 00 00 00 00 00 00]



[1]: E6= This is just makes the RSP wait until it is not using any textures, 

or something like that, in preparation for loading the texture image.

[2-8]: always zero



------------------------------------



Other additional polygon (RSP graphic lib) commands are used in SM64: 

E6, BA, B9, F8, BC, FB, FF, BB, FC, E7, E8 and F2.

---

Originally posted by HyperHacker

---

I don't know enough about Mario 64 to be sure, but really, there are very few models in this game. The tracks, item boxes (I think), Nintendo logo, trophies, palm trees, and moving objects (boat, train, chomp etc) are all that come to mind. Everything else is textured quads. If you've ever noticed things like the snowmen have no backs (you can even get 4 players each looking at a different side and they all see a face!) that would be why.

Of course you could easily export the models to a bunch of bitmaps and import them as textures in place of the old ones.

I would assume though that F3DEX supports more commands than Fast3D, but I don't see much reason to port raw RSP commands between the two.

---

---

The Seven Basic Microcodes
There are seven basic versions of the graphics microcode:
gspFast3D
gspF3DNoN
gspLine3D
gspTurbo3D
gspSprite2D
gspS2DEX
gspZ-Sort
Each basic version has a different set of graphics rendering features and up to three subtypes.

The F3DEX Microcode Series
In addition to the seven basic microcodes, there are seven additional modified versions of gspFast3D, gspF3DNoN, and gspLine3D that have been specially modified to .fifo subtypes to improve performance. These modified versions are:
gspF3DEX
gspF3DEX.NoN
gspF3DLX
gspF3DLX.NoN
gspF3DLX.Rej
gspF3DLP.Rej
gspL3DEX
Together these seven modified microcode versions are known as the "F3DEX microcode series" or the "F3DEX package."

---

---

F3DEX - gspF3DEX.fifo.o or gspF3DEX.NoN.fifo.o
These are extended versions of the Fast3D microcode. The vertex cache size is increased to 32, and gSP2Triangles, a GBI command for displaying two triangles at once, is supported. Not supported is the gSP1Quadrangle command, a GBI command for displaying rectangles that was supported in F3DEX Version 1.21 and earlier versions. (However, this is emulated by gSP2Triangles.)

---