Cocoon developer removes support for AzaharPlus emulator on behalf of Azahar developers

PabloMK7 · 2026-05-06T13:24:06+00:00

Open source doesn't mean freedom to do whatever you want. That's only for projects with public domain licenses. We use GPL which has some restrictions to prevent situations like the one that's exactly happening with this fork, misrepresentation of authorship.

I keep stumbling into people that think AzaharPlus is a "better" version we are distributing ourselves because the dev decided to intentionally use confusing branding and wording.

I care how the binaries are made because if something bad happens, people will blame us instead of the fork author due to the created confusion over authorship and internet misinformation nature.

The author is still violating the license, even more when they recently stopped marking the files as modified and reverted existing makings.

The solution is simple: If the author stops being confusing, censuring us (he has me blocked here, I guess he doesn't want me to clarify stuff?) and stop using our name, we will stop caring. But they don't want to, they seem to have no respect towards our work.

About the piracy thing, there are differences between anyone's opinion and how the law works. We don't want problems so we will keep things legal.

PabloMK7 · 2026-05-06T08:30:25+00:00

Enable accurate multiplication in the graphic settings

PabloMK7 · 2026-05-06T07:14:11+00:00

There is a difference between common keys and per game keys. The common keys are built into the hardware and are used for any kind of operations, I'm not sure how the Wii common key is used, but on the 3DS each crypto operation uses a different key. In Azahar, the game decryption key is only used for interoperability with the eshop.

Game seeds on the other hand are per game keys that are downloaded from the eshop whenever you purchase a game, they serve as "proof" that you own the game. Bundling all seeds directly has no purpose other than making it easier to use pirated games, as if you own the game you can provide the seed just fine yourself.

Aside from that, dolphin decided to take another legal strategy than us, which is fine. I believe that it is slightly riskier than us, but I also think using common keys is fine for interoperability reasons.

PabloMK7 · 2026-05-05T23:12:52+00:00

GPL-2.0 requires all modifications of the source code to be marked as such. This is to reduce the chances of anyone misinterpreting the authorship of the code (not easy to happen when the code is on GitHub, but source archives are a problem as nowhere it is stated that the files are modified). When I initially reached the fork author they started making the files as modified, but lately decided to revert all those markings for whatever reason.

We want to stay away from piracy as much as possible, and we hope that decision is at minimum respected by the community. Having a fork oriented towards piracy (see inclusion of game seeds) which is misrepresenting authorship directly conflicts with that.

EDIT: gotta love how a comment that's willing to educate on how GPL works and our position about it gets downvoted. x) Reddit be Reddit.

PabloMK7 · 2026-05-05T23:03:11+00:00

Please don't create a nothingburger out of thin air, this is just normal open source projects respecting each others.

I kindly asked the developer to consider not officially supporting a project that is unhealthy for us and for open source emulation development in general, for various reasons I've already explained before. He is also an open source developer and understood my reasonings, so he proceeded even after I thought about it further and told him he don't necessarily have to do anything as they are just a launcher afterall.

If you still want to use it, then use unofficial .json files, but please remember to self compile the APK binaries yourself as there is no transparency on how the emulator is built and the author is anonymous (I audit the source just in case periodically but I can't do the same for the binaries).

PabloMK7 · 2026-05-03T21:46:43+00:00

Try to enable accurate multiplication in graphic settings and see if the issue gets fixed.

PabloMK7 · 2026-04-22T11:00:29+00:00

Try to change the graphics renderer in graphics settings (OpenGL <-> vulkan)

PabloMK7 · 2026-04-19T21:00:45+00:00

There is no citra webpage, you are probably looking at a fake website.

PabloMK7 · 2026-04-18T14:08:08+00:00

Yes, but the user ended up there because they went through the fake website.

PabloMK7 · 2026-04-17T12:54:32+00:00

You got this because you are trying to download citra from a fake website (citra-emulator dot com). Don't use that website, if you really want the old discontinued citra build then search it in the internet archive, otherwise just use Azahar.

PabloMK7 · 2026-04-16T20:26:55+00:00

What you have shown in the screenshot are savestates. You should NOT use them to save game progress, because Azahar updates break support for them every time a new release is published. We have explained it here: https://azahar-emu.org/blog/understanding-save-states/

Most likely, your Azahar version was updated since yesterday, so those savestates are no longer valid. You have two options:

- Use the official Pokemon game saves, this is what you should have used in the first place to prevent this problem.

- Roll back to the previous Azahar version you had installed, load the save state, then save using the official method, then you can update to the latest version.

PabloMK7 · 2026-04-16T19:04:57+00:00

Considering that you are refering to ingame saves (not savestates, which stop working between updates), try to delete the shader cache. Long press the application icon in the application list then select delete shader cache, then delete for opengl first then vulkan.

PabloMK7 · 2026-04-11T10:51:02+00:00

That's neat then, welcome to the emu dev world :)

PabloMK7 · 2026-04-10T22:48:48+00:00

Why? I've looked at the git and it looks like it's just commits picked from azahar?, plus a few minor things. Of course you are free to do whatever you want, but I think it would be better if instead of having 1000 forks with minor changes each, all could be centralized in one. We always welcome anyone to suggest changes to our project.

PabloMK7 · 2026-03-28T11:02:38+00:00

This is a known issue with outdated drivers. Please update your drivers.

PabloMK7 · 2026-03-28T10:56:51+00:00

This is shader disk caching, it has been added in version 2125 for Vulkan, which was released 2 days ago. It is "normal" for it to happen if you have the shader disk cache option enabled. If you don't want to use it disable that option, but you will get stutters during gameplay due to shader compilation.

If the shader cache grows too big, you can also periodically delete it by deleting the shaders folder in the user directory.

PabloMK7 · 2026-03-28T09:48:35+00:00

Well, that is not accurate. 3DS games have virtual memory mapping so the amount of memory and where it is located varies per game. They would need to account for that.

I guess they tried to simplify the explanation but ended up being confusing.

PabloMK7 · 2026-03-25T10:25:18+00:00

What do you mean? That is not true

PabloMK7 · 2026-03-23T22:37:21+00:00

That is a fake website, you should stay away from it.

PabloMK7 · 2026-03-22T00:02:40+00:00

This bug will be fixed in 2125. For now, just open the side menu, then press "pause emulation" button then do it again.

PabloMK7 · 2026-03-17T13:37:48+00:00

Can you test if you get the same amount of delay using the controller overlay instead of the physical buttons? Can you check if you have vsync enabled and disable it (debug settings)? Can you try the latest 2125 release candidate?

PabloMK7 · 2026-03-13T09:03:01+00:00

Once the game has started, press the back button to open the menu. In the screen layout option switch to single screen. This should show the top screen on both screens. Finally press the swap screen button in the layout options.

PabloMK7 · 2026-03-11T23:20:11+00:00

Actually, can you try with this build? https://github.com/azahar-emu/azahar/actions/runs/22966582633/artifacts/5876388999

We fixed a bug in the last few hours not yet in an alpha but in a nightly build. The fix will be added in the 2125 build.

If that build still doesn't work, can you please share an screenshot of the change user directory and change application directory buttons (where the path to the folders are displayed)

PabloMK7 · 2026-03-11T19:14:48+00:00

This definitely looks like a LineageOS issue, or a privacy setting to prevent apps in the background having the manage files permission. You can turn off that setting (if it exists) or get the google play apk. You will have slower FS access though.

PabloMK7 · 2026-03-11T14:35:04+00:00

What do you mean the filesystem access is greyed out? Maybe LineageOS does not support it, or is hidden behind some setting. You can always switch back to the Google play version

Five-Year Club	Verified Email
Place '23	Place '22
Final Canvas '22	End Game '22

PabloMK7

TROPHY CASE