Add f3d material info page #2
Conversation
|
I wrote a f3d overview page that is intended for people to understand stuff as it is viewed from fast64 menus. These pages may need some additional info but for me they're pretty concise and cover the basics in a precise way. Please correct any errors or inform me of any quirks I missed |
There was a problem hiding this comment.
nice
Note RTD is failing to render
https://readthedocs.org/projects/fast64/builds/
https://readthedocs.org/projects/fast64/builds/23620074/
I'm guessing need to add sphinx_design to requirements.txt
also please pin down specific versions in requirements.txt
also x2 it seems you changed line returns from \n to \r\n, please use \n everywhere (and have a trailing \n in files)
|
yeah the new line thing is probably something to do with windows. I'm not sure exactly how it got in there but I'll fix it. |
|
I have fixed build issues and I also added some patterns to clean up the build so that all the missing file warnings from packages go away |
common/f3d_materials.md
Outdated
|
|
||
| * Environment Color: Free use register | ||
|
|
||
| * Primitive Color: Free use register. Encoded at the same time as LOD variables but those have no impact on the color. |
There was a problem hiding this comment.
I'd get rid of the Encoded at the same time as LOD variables but those have no impact on the color. part and just say something like Primitive Color also has some additional capabilities, but these are not relevant to F3D materials in Blender. Besides the LOD variables, prim color is buffered so that it can be changed between primitives without needing any kind of syncs. This is the only register which has this property.
common/f3d_materials.md
Outdated
| Discrete values are adjustable float values between 0 and 1 that you can use for blending or interpolating colors. These are simply factors that you can use to fine tune the contribution of each input to the color combiner. Some registers are created with specific graphical purpose, while others are just for user flexibility. | ||
|
|
There was a problem hiding this comment.
I'd add something that the most common "discrete value" registers used for interpolation etc. are prim alpha and env alpha, which are not on this list.
common/f3d_materials.md
Outdated
|
|
||
| ## Z Buffer | ||
|
|
||
| Enabling [Z buffer]{.key_text} will make it so that Z buffer calculations are carried out on drawn triangles. This makes it so that triangles can utilize depth checking per pixel if enabled inside the RDP. Disabling Z buffer will change the drawing algorithm of the triangles sent to the RDP to ignore depth. Depth values are never written to triangles in DMEM and when rasterizing depth is never considered for the entire primitive. |
There was a problem hiding this comment.
Nit: Disabling geometry mode Z buffer means Z values are not sent to the RDP, so the Z values used in the tri are garbage. This does not mean depth is not considered, if you have Z enabled in the blender, it'll use the garbage values. I'd replace the last part with saying "if you disable this, make sure Z is not used in the blender in your rendermodes".
There was a problem hiding this comment.
Is this also true for z_src_prim?
Sort of testing this out for now. I'm sure the info is mostly correct but let me know if there is an issue.
This needs some formatting changes to link the page properly and maybe each tab should be separated into a different page idk.
Also I need to update requirements.