• ❔At the moment I don't have the Switch and Miitomo body models, I believe they would once again require skeletal posing to be implemented..
• ❔Poses from the Wii U Mii Maker are planned as soon as skeletal animations work.
  • Every pose is just a single-frame animation from MiiAnim.bfres, same source as everything else.
  • I'm pretty sure the camera positions are in JpgPoseCam.bfres, but Switch Toolbox cannot open it, so... not sure what I'm going to do about that.
  ❔Need to reverse the Tomodachi Life and Miitopia QR code formats. Miitomo codes are planned as soon as Kaerutomo properly implements them.

  • To be clear, this is not referring to being able to merely scan their codes, but rather make use of the extra game-specific data within.
  • ... For example, applying the custom colors (hair color, etc.) within, displaying their voice or personality traits...
    • In the case of Miitomo, this means extracting the "nx_mii_core_data" Switch data that QR codes are supposed to give you, for the wider colors.
  • I actually did find the AES key and was able to make an encoder/decoder for the extra data within these codes for all of those games, check it out: https://jsfiddle.net/arian_/ckya346z/8/
  • For Tomodachi Life and Miitopia, all of the data is within the code and just needs to be reversed. For Miitomo, it's more complicated, and sadly existing codes won't work, because:
  • It looks like the only thing Miitomo stores in the QR code is some sort of ID ("token_for_json_data") - it expects the server to store the extra data with this ID and will use it to retrieve that data back from the server.
  • Problem is, Kaerutomo does not store or retrieve this data for you. At all. And since it's not open source, nobody can add it except for them, and they aren't interested. 😐
  • (If you are a Kaeru dev reading this, PLEEEASEEEE get in touch!!! 😭)
• ❔Need to match the texture filtering/mipmap options.
  • I feel that the clarity of the face texture doesn't match Wii U or Miitomo, I don't know.
  • Some face features are hard to make out at low resolutions like 96x96.
  • Will need to take a long hard look at this one day...
  ❔Replicating 3DS and Wii renders has been considered but isn't easy or a priority.

  • This requires extracting the meshes (and textures? but those can be downscaled from the new ones) from CFL_Res.dat, but its header hasn't been reversed.
  • In a pinch RFL_Res.dat could work, but 3DS/Wii U hair styles, textures etc. wouldn't work, and while there's an RFL decomp, I can't find the source code for the one RFL_Res.dat editor everyone uses.
  • Now, I could try making an extractor for the RFL_Res.dat format using the RFL decomp for structures, and then see how far I can apply that to CFL_Res.dat.
  • ... But if it doesn't work, well I'm not familiar with many games that have symbols for CFL (or even how to look at 3DS binaries in Ghidra), and frankly don't care enough to put a lot of time into it. Sorry, 3DS Mii render fans.
  • Second obstacle is shaders, neither of these consoles use GLSL-compatible shaders. This can probably be worked around (or remade since it's very basic) but is still annoying.
• ❔Miitomo/Tomodachi Life clothing/headgear/wigs may be planned.
  • Don't expect any of these any time soon, especially clothing and wigs.
  • Do keep in mind that these body models are different from the Wii U/Switch models and therefore the clothing may not work on those.
  ❔Fully rendering Miis in the browser is a longterm goal of mine. I can't promise anything, but I am steadily working towards it.

  • I did get FFL-Testing building with Emscripten in August, and if I handle it just right, it is able to fully render a Mii head, albehit without hair and many WebGL errors...
  • So what else is left? For starters, the assets need a more efficient compression method instead of zlib. I'm thinking of using Draco for meshes, and then ASTC for textures. As of writing, neither are implemented yet.
  • An interface will need to be made to bridge the C exports of FFL to be callable from JS, and then make a shader callback implementation in JS using WebGL or three.js.
  • So I haven't gone that far with this, and have not yet connected FFL in WASM to JS. But...
  • As of October 2024, I have a little jsfiddle here that will read a Mii exported to glTF from my site, and render it with the Wii U shader! Isn't that nice?
  • Now, once this is properly implemented and working, I can't even begin to think about the possibilities. At the minimum, this site could go serverless, and services using Miis may not even need to render and store icons on their side. Woo.
  • As usual, if you want to help or put pressure on me to work on this with more haste, ping me.
• ❔I've thought about making a Mii Maker-like app with the FFL decomp, but... don't get your hopes up too far about this.
• However, if you like the sound of this...
• ... and you're either working on something like this right now and it just needs Mii heads, OR you'd want to design the UI for this and let me add the rendering logic, do get in touch!
• (This is assuming, yaknow. it's not a Scratch or Roblox game or something)

Unplanned:

• Custom hairstyles or frankly custom anything
• Miitopia makeup, or custom expressions (sorry)
  • Miitomo expressions are the only exception, since they're built into AFL (its version of FFL). See?
• BoTW/TOTK models, or "semi-Miis"
• Xbox Miis, Apple Miis, Samsung Miis, any other stupid bootleg Miis
  • Never ask me for these 🤬