メニュー
Use this skill if you need to decompile a function that uses F3DEX. The presence of the Gfx type or gRegionAllocPtr are strongly indicative of an F3DEX or S2DEX microcode function.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Decomp-Permuter is a tool that automatically permutes C files to better match a target binary. Use this skill when you are decompiling a function and it is almost matching except for some register differences (i.e. 95%+). Or if you are otherwise unable to make progress on a function decompilation. Do not use it when there are control flow or functional differences; it's often easy to resolve those by hand, and neither the scorer nor the randomizer tends to play well with them.
Match a given segment to a libultra ROM segment. Use this when converting unidentified asm libultra ranges such as osRecvMesg to matching C source.
Adding a new asset to snowboardkids.yaml requires following specific steps to ensure assets are in the correct order and properly declared. Use this skill when you need to add a new binary asset.
Convert arrays with hardcoded pointer addresses to use ROM_START/ROM_END symbols. This automates the process of adding USE_ASSET declarations, updating array initialization, and configuring YAML segments.
Match data file describes how to add dat asegments to a C file. Use the match data file skill when you need to match a data file.
Renaming a C file or associated header (.h) file requires additional steps in decompilation projects or the build will fail. Use this skill when you want to rename a C file and/or a header file.
| name | decompile-microcode |
| description | Use this skill if you need to decompile a function that uses F3DEX. The presence of the Gfx type or gRegionAllocPtr are strongly indicative of an F3DEX or S2DEX microcode function. |
gRegionAllocPtr is indicative of a dynamically constructed F3DEX display list. F3DEX display list commands are microcode that are passed to the RSP for rendering. They are all 8 bytes long.
Special care needs to be taken with functions constructing display lists as the original developer likely used specific macros from include/PR/gbi.h (compiled with -DF3DEX_GBI). These macro calls need to be replicated in order for the function to match.
The first step is to identify the commands in question, for example a naive decompilation might produce:
temp_v1 = gRegionAllocPtr;
temp_a1 = (s32)arg0->unk30;
temp_v1->words.w0 = 0x01020040;
temp_v1->words.w1 = temp_a1;
Here there is a single F3DEX command. Its w0 starts with 0x01 — the F3DEX G_MTX opcode (F3DEX2's G_MTX is 0xDA; do not confuse the two). We can use gfxdis.f3dex to identify it:
gfxdis.f3dex -d 0102004000000000
Which gives us:
gsSPMatrix(0x00000000, G_MTX_NOPUSH | G_MTX_LOAD | G_MTX_MODELVIEW);
This is close to what we want. But it needs a few improvements:
gSPMatrix.This ultimately will give us:
gSPMatrix(gRegionAllocPtr++, (Mtx*)arg0->unk30, G_MTX_NOPUSH | G_MTX_LOAD | G_MTX_MODELVIEW);
Note the inline increment of gRegionAllocPtr, this is very common in commands dealing with F3DEX microcode.
The mapping may not always be this clear, however. You can consult @f3dex-microcode-reference.md for a full list of F3DEX commands and include/PR/gbi.h for suitable macros to use.
Be aware that some macros in gbi.h aggregate a number of regular F3DEX commands. You should always look for patterns of commands that could translate into one of these macros. The use of which is very likely to increase your match percentage. Common examples of this include:
But there are many others.