m000z0rz
a3ca8cfbda
* Ignore IntelliJ editor data
* [OoT] Add skeleton import test scripts
In preparation for fixing skeleton imports from the MM decomp, make a
script for testing skeleton imports.
Running `python3 scripts/make_all_skeletons.py <decomp path> <output
folder>` will attempt to import all skeletons from every file in the
decomp that appears to contain a skeleton, and report on how many
files raised exceptions during the import. The generated .blend files
are stored in the output folder. Including a third argument of ` will
attempt to import all animations for files that contain a single
skeleton as well.
Running this on the mm decomp at commit
803ff1fb1593cdc0c62d14882973af04dc0f988e (from 2024-07-13) results in
only 3/174 (1.7%) of files with skeletons importing them without exceptions.
* [OoT] Strip comments in limb list
The MM decomp specifies `EnumName` values for limbs in the asset XML,
which generates an enum naming bone indicies. These enum values are
also generated in comments in the limb list:
void* gDekuButlerSkelLimbs[] = {
&gDekuButlerRootLimb, /* DEKU_BUTLER_LIMB_ROOT */
Fast64's current limb list parsing does not expect comments here,
which causes the limb list parse to fail.
Add a function to strip comments of this style, and strip them before
parsing limb list entires.
* [OoT] Identify and parse enums when importing skeletnos
The MM decomp defines EnumNames for limbs in asset XML, which causes
ZAPD to generate limb definitions that use these enum values for the
next child and next sibling (with an offset of 1).
StandardLimb gDekuButlerRootLimb = {
{ 0, 2775, 0 }, DEKU_BUTLER_LIMB_PELVIS - 1, LIMB_DONE,
ootGetLimb currently only supports int values, hex values, or
LIMB_DONE here.
In preparation for supporting limb enum values of this form, add the
object's header file to skeletonData and parse all enums found during
skeleton import. The next patch in this series will use the parsed
enums to handle limb definitions of this form.
* [OoT] Support limb enums for limb nextChild / nextSibling
Use the parsed enums to support next child and next sibling
definitions of the form `<limb enum value> - 1`.
With this change and the others from this patch series,
`make_all_skeletons.py` goes from just 3/174 (1.1%) of MM decomp files
with successful skeleton imports to 169/174 (97.1%).
Fast64
This requires Blender 3.2+. Blender 4.0+ is recommended.
Forked from kurethedead/fast64 on BitBucket.
This is a Blender plugin that allows one to export F3D display lists. It also has the ability to export assets for Super Mario 64 and Ocarina of Time decompilation projects. It supports custom color combiners / geometry modes / etc. It is also possible to use exported C code in homebrew applications.
Make sure to save often, as this plugin is prone to crashing when creating materials / undoing material creation. This is a Blender issue.
https://developer.blender.org/T70574
Credits
Thanks to anonymous_moose, Cheezepin, Rovert, and especially InTheBeef for testing. Thanks to InTheBeef for LowPolySkinnedMario.
Discord Server
We have a Discord server for support as well as development here.
Links to Docs / Guides for Each Game
Installation
Download the repository as a zip file. In Blender, go to Edit -> Preferences -> Add-Ons and click the "Install" button to install the plugin from the zip file. Find the Fast64 addon in the addon list and enable it. If it does not show up, go to Edit -> Preferences -> Save&Load and make sure 'Auto Run Python Scripts' is enabled.
Tool Locations
The tools can be found in the properties sidebar under the 'Fast64' tab (toggled by pressing N). The F3D material inspector can be found in the properties editor under the material tab.
F3D Materials
Any exported mesh must use an F3D Material, which can be added by the 'Create F3D Material' button in the material inspector window. You CANNOT use regular blender materials. If you have a model with Principled BSDF materials, you can use the Principled BSDF to F3D conversion operator to automatically convert them. The image in the "Base Color" slot will be set as texture 0, while the image in the "Subsurface Color" slot will be set as texture 1.
Vertex Colors
To use vertex colors, select a vertex colored texture preset and add two vertex color layers to your mesh named 'Col' and 'Alpha'. The alpha layer will use the greyscale value of the vertex color to determine alpha.
Large Texture Mode
In F3D material properties, you can enable "Large Texture Mode". This will let you use textures up to 1024x1024 as long as each triangle in the mesh has UVs that can fit within a single tile load. Fast64 will categorize triangles into shared tile loads and load the portion of the texture when necessary.
Decomp vs Homebrew Compatibility
There may occur cases where code is formatted differently based on the code use case. In the tools panel under the Fast64 File Settings subheader, you can toggle homebrew compatibility.
Converting To F3D v5 Materials
A new optimized shader graph was introduced to decrease processing times for material creation and exporting. If you have a project that still uses old materials, you may want to convert them to v5. To convert an old project, click the "Recreate F3D Materials As V5" operator near the top of the Fast64 tab in 3D view. This may take a while depending on the number of materials in the project. Then go to the outliner, change the display mode to "Orphan Data" (broken heart icon), then click "Purge" in the top right corner. Purge multiple times until all of the old node groups are gone.
F3DEX3 Features
Fast64 supports exporting data for F3DEX3, a modded microcode which brings many new features and higher performance. Preview of these new features in the 3D view is not currently supported, but they will be exported correctly. To modify the vertex colors of an object with a material which is using packed normals (shading/lighting and vertex colors together), temporarily switch to a vertex colored preset or uncheck Lighting in the material geometry mode settings. Once the vertex colors are painted how you want them, re-enable Lighting and Packed Normals.
Selecting F3DEX3 as your microcode unlocks a large number of additional presets based on F3DEX3 features. For more information on all these features, see the F3DEX3 readme, GBI, and these videos. The preset names get very long and are abbreviated as follows:
Shaded: Computes lighting, which normally affects shade color.Vcol: Vertex colors are enabled in addition to lighting; normally these are multiplied together to become shade color.Ao: Ambient occlusion.Cel: Cel shading. If followed by a number, this is the number of cel levels.Ltcol: Cel shading tints are loaded from light colors.Blendvs.Mulfor cel shading: Whether to apply the tint in the blender with linear interpolation, or by multiplication in the CC. The latter sometimes looks better, but does not support vertex colors.Lerpvs.Multfor multitexture (water): Whether the two textures are combined by linear interpolation or multiplication.
For cel shading, it is recommended to start with one of the cel shading presets, then modify the settings under the Use Cel Shading panel. Hover over each UI control for additional information about how that setting works.
Updater
Fast64 features an updater (CGCookie/blender-addon-updater).
It can be found in the addon preferences:
Click the "Check now for fast64 update" button to check for updates.
Click "Install main / old version" and choose "Main" if it isn't already selected:
Click OK, there should be a message "Addon successfully installed" and prompting you to restart Blender:
Clicking the red button will close Blender. After restarting, fast64 will be up-to-date with the latest main revision.
Fast64 Development
If you'd like to develop in VSCode, follow this tutorial to get proper autocomplete. Skip the linter for now, we'll need to make sure the entire project gets linted before enabling autosave linting because the changes will be massive. https://b3d.interplanety.org/en/using-microsoft-visual-studio-code-as-external-ide-for-writing-blender-scripts-add-ons/
Formatting
We use Black, version 23.
To install it, run pip install 'black>=23,<24'.
To make VS Code use it, change the python.formatting.provider setting to "black".
To format the whole repo, run black . (or python3 -m black . depending on how it is installed) from the root of the repo.
The (minimal) configuration for Black is in /pyproject.toml.
There is a GitHub action set up to check that PRs and the main branch are formatted: /.github/workflows/black-lint.yml
If you see a message such as
Oh no! 💥 💔 💥 The required version `23` does not match the running version `24.1.0`!
Make sure the black --version is 23. Install a 23 version with pip install 'black>=23,<24'.
Updater notes
Be careful if testing the updater when using git, it may mess up the .git folder in some cases.
Also see the extensive documentation in the https://github.com/CGCookie/blender-addon-updater README.
The "Update directly to main" button uses bl_info["version"] as the current version, and versions parsed from git tags as other versions. This means that to create a new version, the bl_info version should be bumped and a corresponding tag should be created (for example "version": (1, 0, 2), and a v1.0.2 tag). This tag will then be available to update to, if it denotes a version that is more recent than the current version.
The "Install main / old version" button will install the latest revision from the main branch.