Hi everyone!

I noticed there was a project called switch-nfp-mitm, which had lots of forks, but none of them properly working (people reported it barely worked, and with some games), thus I decided to try to fix it, or to improve it as much as I could. Well, the results were that good, that I've just managed to get it working perfectly, even with a nice system of combos for Amiibo swapping, in just 2 days.

So, well, here's the result:

emuiibo

emuiibo is a virtual amiibo (amiibo emulation) system for Nintendo Switch!​

It consists on a background process (and service), which intercepts Nintendo Switch's internal NFC/NFP services to support virtual amiibo emulation, plus an overlay to easily control it.

• For more detailed information, check emuiibo's GitHub repository: https://github.com/XorTroll/emuiibo​

• Releases: https://github.com/XorTroll/emuiibo/releases/latest​

Have fun playing around with custom virtual amiibos!

 

[aur0n]

I'm having a weird problem with Mario Odyssey: I could load and switch all Amiibos (using AmiiSwap), but the wedding ones are recognized as standard. For example, when I load Wedding Bowser, the NPC tells me it's just "Bowser" and no costume unlocks. Same for Mario Wedding and Peach Wedding.

Also Mario Gold is not unlocking, it's being recognized as "Mario". I downloaded from different sources, same result, just with them. Anybody might know why?

 

[AD2076]

I'm having a weird problem with Mario Odyssey: I could load and switch all Amiibos (using AmiiSwap), but the wedding ones are recognized as standard. For example, when I load Wedding Bowser, the NPC tells me it's just "Bowser" and no costume unlocks. Same for Mario Wedding and Peach Wedding.

Also Mario Gold is not unlocking, it's being recognized as "Mario". I downloaded from different sources, same result, just with them. Anybody might know why?

My guess is those variation are in saved data area of amiibo like in wolf link with 20 hearts and emuiibo still have issues in recognizing those data

 

[AileenLumina]

When trying to emulate the Ganondorf Smash Amiibo in SSBU, the game tells me it "Couldn't find a controller that supports NFC." I tried with a first party Switch Pro Controller and with a regular right Joy-Con. What am I doing wrong? My folder structure looks like this:

| sdmc:
| - emuuibo
| - - ganondorf
| - - - amiibo.bin
| - atmosphere
| - - titles
| - - - 0100000000000352
| - - - - exefs.nsp
| - - - - flags
| - - - - - boot2.flag

I can confirm emuiibo is running because the HOME button lights up when pressing the right control stick and right or up on the D-pad (however, it does not light up when pressing left or down on the D-pad instead).

Edit: Solved, apparently, emuiibo doesn't automatically create an amiibo.json and fails to emulate an amiibo if there isn't one, which means I had to create the structure according to the "old format" for emuiibo to automatically convert it to the new format.

 

[lordelan]

@XorTroll
Two questions:

1. You wrote you support saves for multiple games on the same Amiibo now. Do you do that automatically?
   So I can just go ahead and save to my Luigi.bin from game A and then save something else from game B without having to worry about that by myself?
2. If I dump my real Link Amiibo which already has save data for Smash Bros. on it with TagMo (Android) to a bin, that save data won't be usable with emuiibo/AmiiSwap right now ... it's a "vanilla" Link instead, I guess?

 

[thaikhoa]

It seems that emuiibo is broken on Atmosphere 0.9.1 and/or Switch firmware 8.1. Does anyone encounter frozen screen with Switch logo when booting?

 

[mrdude]

It seems that emuiibo is broken on Atmosphere 0.9.1 and/or Switch firmware 8.1. Does anyone encounter frozen screen with Switch logo when booting?

Yes, if you're using Atmos and 8.1.0 - emuiibo stops the switch from booting. You'll need to delete that from the titles folder for the switch to boot - and if you need emuiibo - downgrade back to 8.0.1 firmware.

 

[cucholix]

Yes, if you're using Atmos and 8.1.0 - emuiibo stops the switch from booting. You'll need to delete that from the titles folder for the switch to boot - and if you need emuiibo - downgrade back to 8.0.1 firmware.

I can confirm this, in fact every system module to date is broken in 8.1.0.

 

[XorTroll]

I've just released 0.2.1, supporting 8.1.0 fine (just needed to rebuild everything with everything up-to-date)
Enjoy! https://github.com/XorTroll/emuiibo/releases/tag/0.2.1

 

[cucholix]

I've just released 0.2.1, supporting 8.1.0 fine (just needed to rebuild everything with everything up-to-date)
Enjoy! https://github.com/XorTroll/emuiibo/releases/tag/0.2.1

It still doesn't allow atmosphere to boot normally for me :c

 

[mrdude]

I've just released 0.2.1, supporting 8.1.0 fine (just needed to rebuild everything with everything up-to-date)
Enjoy! https://github.com/XorTroll/emuiibo/releases/tag/0.2.1

Thanks, it's working fine for me now - that's my updated to 8.1.0 on Atmosphere now, and can confirm it's working brilliantly again and Atmos is booting past the Nintendo screen. Thanks for fixing so quickly.

 

[JonJaded]

It still doesn't allow atmosphere to boot normally for me :c

Do you have the other kosmos sys modules installed?

Freebird, ldn_mitm, sys_ftp or sys_netcheat?

EDIT: Freebird, not FIREbird.

 

[cucholix]

Do you have the other kosmos sys modules installed?

Firebird, ldn_mitm, sys_ftp or sys_netcheat?

I’m not using kosmos but atmosphere I only have game patches (layeredFS)

 

[thaikhoa]

Thanks for the update. It works perfectly fine on atm 9.1 + emummc 8.1.

please keep the project up.

 

[cucholix]

Updated it through hb store, rebooted to paypload and it’s working now, probably made a mistake before somewhere

 

[Krude]

Is there any way to get this working for Hyrule Warriors? I can get it to work on Mario Odyssey or BOTW or Splatoon (sort of), but when i try to read in an amiibo on Hyrule Warriors, it doesn't work.

Maybe it uses a different method to call amiibo functionality? If i use emuiibo in airplane mode with NFC disabled, reading amiibo in Mario Odyssey etc. still works. But Hyrule Warriors throws me a "NFC reading is disabled via system settings" error.

 

[angelo93]

Thanks so much for the awesome work! I'm able to run it for all my titles except for Diablo 3. It's a little finicky and works after like 5-10 tries doing various combinations of launching emuiibo and the title itself. Is it just me or do others have a problem getting it to work with D3, if so what have you done that works best? For me I click on the title so the profile selection comes up and then I start emuiibo and then select a profile and launch.

 

[FuryBaguette]

Thanks so much for the awesome work! I'm able to run it for all my titles except for Diablo 3. It's a little finicky and works after like 5-10 tries doing various combinations of launching emuiibo and the title itself. Is it just me or do others have a problem getting it to work with D3, if so what have you done that works best? For me I click on the title so the profile selection comes up and then I start emuiibo and then select a profile and launch.

Use the toggle combo or the corresponding option in amiiswap before starting the game, you don't have to toggle it anymore after that, just load your game and go to the "amiibo part" and it should emulate your amiibo, just change amiibos when you need

 

[Kirbyyeray]

will be splatoon 2 added soon?

 

[JonJaded]

Is there any way to get this working for Hyrule Warriors? I can get it to work on Mario Odyssey or BOTW or Splatoon (sort of), but when i try to read in an amiibo on Hyrule Warriors, it doesn't work.

Maybe it uses a different method to call amiibo functionality? If i use emuiibo in airplane mode with NFC disabled, reading amiibo in Mario Odyssey etc. still works. But Hyrule Warriors throws me a "NFC reading is disabled via system settings" error.

Yeah, I'm not sure why it doesn't work. Haven't gotten it to work properly there either.

 

[lordelan]

Yeah, I'm not sure why it doesn't work. Haven't gotten it to work properly there either.

Same here. Works for MK8 and BotW just fine but not for Diablo III.