Talk:Mii data

From WiiBrew
(Redirected from Talk:Mii Data)
Jump to navigation Jump to search

Unknown Bytes?

"Six unknown bytes (mostly zeroes) follow." - These bytes could be for options like Mingle, favorite color, or the "Favorite" flag. Or are those part of the "Mii data"?

If none of those, it may have to do with whether the Mii can be edited. I was wondering... if you transfer a Mii to a Wiimote, remove it from the Wii, and transfer it back, can it still be edited? It would be nice to be able to make it so that Miis perhaps created on a computer and then transferred to the Wiimote could be edited on the Wii. If there were a Mii-sharing site, that could be a user-set option (whether it was read-only for downloaders)

--Fashnek 15:48, 8 December 2006 (CST)

[Reply] There are four bytes that are derived from your Wii's mac address (checksum of first 3 bytes, then the actual last 3 bytes of the mac address). If you copy a Mii created on another Wii to your computer, edit these four bytes to match your mac address, then copy it back to the Wiimote, you will be able to edit it on your Wii. We will likely add this functionality to the next version of the WDML MiiTransfer program. Also: Favorite is system specific. Favorite can't be turned on with a Mii from someone else's system since you can't edit them. -WDML
I did a test, making 2 standard miis, marked one favorite. Seems that it's stored at the console, as the mii data blocks were identical when all I changed was the favorite flag. --opello 23:09, 13 December 2006 (CST)

Why u16?

I like the new data format section. Maybe this is a dumb question, but why use u16 for values that only take 1 - 8 bits? I don't know terribly much about data allocation, but it doesn't seem necessary to just take the lower couple of bits from a 16-bit integer. --71.204.46.49 11:35, 11 December 2006 (CST)

[Reply] The u16s and u32s are used to group similar data, so that all information about the hair, for example, can be kept in one variable, rather than having two or three u8s to keep track of. For some things this may seem odd, as we haven't figured out all the bits in the u16 yet. For others, I have a feeling some u16s will need to be merged into u32s. -WDML

MiiTransfer Discussion

I'm not having any luck with the MiiTransfer program. It sees my wiimote, but it says ERROR when I try to read or write a data slot. I tried on 2 different computers with 2 different BT dongles. What can I do to help debug? -LiquidIce

[Reply] What bluetooth stack are you using? The program was tested with the default Windows XP SP2 stack, and uses the ReadFile method rather than getting HID reports from the device directly. -WDML
[Reply] I have a Linksys USBBT100 which uses the Broadcom BT Stack. Wii-mote works fine with GlovePIE, WiinRemote and other apps, but not this one. Installing Visual C Express to try to compile it now myself. Any suggestions would be appreciated. have you been to irc efnet #wiidev ? -LiquidIce
Try using the default WindowsXP stack if you can with that device. -WDML
Nice it works with the Microsoft BT Stack. Kinda inconvenient to be switching between the two for glovepie and miis but that works for now. Thanks for the software and for sharing the source code.
I put up a pag

1000 e for people to share Mii Data. Upload your Mii's here: http://www.wiimodwii.com/miis/

-LiquidIce
I'll look into making it compatible with other stacks in the next version. -WDML
Give the new version 0.9.1 a try, it should work with more stacks, though I have not tested bluesoleil as of yet. -WDML
I can confirm that it works with the WIDCOMM stack. Thanks for all your hard work, WDML! --AJ 187 16:20, 13 December 2006 (CST)
Bluesoleil still doesn't appear to be working. :(

Any updates on availability of new version(s)? - xiaNaix

When is a Bluesoleil compatible version going to appear??? I really want to get sending Miis around the internet but I also use Glovepie and it is really inconvenient to keep having to switch between drivers! Please release a Blueoleil version soon! Thanks!

Can someone provide me a link to the cheapest bluetooth adapter that's compatible with MiiTransfer? --71.225.64.232 07:55, 19 February 2007 (PST)

My name is pokesomi and I have gotten Bluesoleil to connect to and allow glovepie to get some values from the wiimote. I would be willing to test a workable version of Miitransfer on my server setup. Also, where can I get the Microsoft Bluetooth stack?

Hi, im jibgilmon. ive been using a widcomm stack and the kensington usb 2.0 bluetooth device. other programs like glovpie and wiinremote and all that work but not the miitransfer and i have double checked that the address is corect -jibgilmon EDIT: sorry, it works now, i was using 1.9.0 not 1.9.1

EDIT: spam removed

my opinion

[borat] It's nice [/borat] —Preceding unsigned comment added by Anonymous user (talkcontribs)

Checksum on Mii id?

When I swipe a Mii's ID for use on another, it works properly. When I try to create a Mii from scratch, it never shows up. - トウメイ —Preceding undated comment added 00:24, 18 June 2009 (UTC).

"NigaoeNR"?

What does the Mii Channel Codename stand for? Im curious because it can release information about the Wiis Development. --RVLREECE 15:41, 5 October 2009 (UTC)

Over a year later, but "nigaoe" is something like "portrait", and my guess is that "NR" is "no Revolution". Basically something like "Wii Portrait(s)". - Vague Rant 09:45, 31 October 2010 (CET)

8 bit checksum on MAC address

As I can't find if the checksum has been discovered or not, and since it isn't any of the common ones out there, I have studied it for some time; my findings are as follow:

The lower 4 bits of the checksum seems to be equal to the sum of the last 4 bits of the 3 bytes. On overflow, the overflowed amount is added to the upper 4 bits of the checksum. The upper 4 bits of the checksum seems to be equal to the sum of the upper 4 bits of the 3 bytes, but:

- If the sum of the 4 upper bits of the 3 bytes are > 8, then it cuts the value down to less than 8. In other words, seems to do division by 8.
- The last 4 bits' overflow are taken into consideration for cutting the value down of the 4 upper bits sum.

Right now, this doesn't explain how valid numbers like C2 can be generated.

The checksum is calculated as follows (pseudocode, confirmed via reverse engineering):
checksum = (mac_address[0] + mac_address[1] + mac_address[2]) & 0xFF
if mac_address[0] != 0x00 and mac_address[1] != 0x17 and mac_address[2] != 0xAB:
    checksum &= 0x7F
The first three bytes of a MAC address is the "Organizational Unique Identifier" (OUI), and the specific one checked (00:17:AB) is called "scFirstMakerCode" within the RFL code. If the OUI is not set to that value, then the most significant bit will be cleared from the checksum.
An OUI of 00:16:AC, which has a sum of 0xC2, would result in a checksum of 0x42, while an OUI of 00:17:AB, which also has a sum of 0xC2, would result in a checksum of 0xC2. Slp32 (talk) 17:26, 5 February 2024 (CET)