Package Details: cemu 1.26.2-6

Git Clone URL: (read-only, click to copy)
Package Base: cemu
Description: Wii U emulator (via wine). Includes the Cemuhook plugin
Upstream URL:
Keywords: emulator nintendo wii-u wiiu wine
Licenses: custom
Submitter: chris_l
Maintainer: chris_l
Last Packager: chris_l
Votes: 27
Popularity: 0.56
First Submitted: 2017-12-14 02:53 (UTC)
Last Updated: 2022-02-18 03:32 (UTC)

Latest Comments

DigitOtter commented on 2022-05-15 10:00 (UTC)

Thanks for package!

The newer builds of lutris's wine also support Vulkan on cemu. So if you're looking for Vulkan support but don't want to replace your local wine package with wine-ge-custom, add cemu as a locally installed game to lutris and set it to use wine lutris-fshack-7.2 or newer.

Megacubo commented on 2022-04-14 23:21 (UTC)

Thanks for the package. With gamescope the emu run flawlessly without any screen tearing

acpcalin commented on 2022-04-07 14:17 (UTC)

Does anybody know why even though I have two Xbox Series S controllers connected via Bluetooth, and Wine sees both of them in wine control, when I try to configure both of them in cemu I can only configure one of them, the other doesn't even show up?

chris_l commented on 2022-02-12 04:07 (UTC)

@joeleg ok, its fixed now.

joeleg commented on 2022-02-12 03:42 (UTC) (edited on 2022-02-12 04:17 (UTC) by joeleg)

Hey, I think the checksum may have changed. I'm getting the sum as e905d5c441e8d64d02c1b4adc1a58019 for whereas the pkgbuild has 726dc9328e42e4db934ea24aba511ec7. Could you have a look at that? Thanks

EDIT: Thanks for fixing that :)

chris_l commented on 2022-02-12 01:07 (UTC) (edited on 2022-02-12 01:31 (UTC) by chris_l)

I found the problem. It seems it was cemuhook what was causing it to freeze, even when on the cemuhook website says the latest version is supposed to support this version of cemu.

And since cemu 1.26.2 includes a new software decoder for H264 videos, it seems cemuhook is no longer required.

So the new version of this package no longer has cemuhook. It may be included again in the future if a new version that doesn't freeze under wine comes out and if it has features that are not present by default on cemu.

chris_l commented on 2022-02-12 00:11 (UTC) (edited on 2022-02-12 01:07 (UTC) by chris_l)

The new version 1.26.2 is out now, but it freezes under wine.

So I'm not gonna update it until a new version that doesn't have this problem is released, or a solution is found.

If you want to try it, here is the PKGBUILD:

chris_l commented on 2022-01-01 04:57 (UTC) (edited on 2022-01-05 08:11 (UTC) by chris_l)

If you want to use Vulkan on Cemu, install wine-ge-custom.

patlefort commented on 2021-12-25 23:19 (UTC)

Do they have a way to notice users of new releases? (email and such)

chris_l commented on 2021-12-25 23:11 (UTC)

...and right after update it to 1.26.0b, they just released 1.26.0c

chris_l commented on 2021-12-25 22:39 (UTC)

@patlefort Yes, the reason is what I mention inside the PKGBUILD file. The Cemu team unfortunately uploads the minor revisions by replacing the file, instead of creating a new url that includes the revision letter.

That is, in this case, both the 1.26.0 and the 1.26.0b version (which was just released) have the same exact url,

So the md5 from the original 1.26.0 is not the same as the one from 1.26.0b, and of course its going to fail.

And if they release a 1.26.0c, is going to happen again. But I'll update it again as soon as I can if that happens.

patlefort commented on 2021-12-25 20:44 (UTC) is failing validity check.

chris_l commented on 2021-11-07 23:01 (UTC)

@uumas Yes. Unfortunately, wine is not compatible by default.

You'll need to patch wine. Check this post, it deals specifically with the error you mentioned:

But, since I don't use cemu with vulkan, I haven't tried following those steps.

uumas commented on 2021-11-07 13:43 (UTC)

I'm getting "Error when initializing Vulkan renderer: Cannot create win32 Vulkan surface: -9" when trying to launch a game with Vulkan. In console it says "0120:fixme:vulkan:X11DRV_vkCreateWin32SurfaceKHR Application requires child window rendering, which is not implemented yet!"

Also, trying to set the game or mlc directory gives error "The selection contains non-folder object". Tried with both wine 6.20-1 and the latest wine-staging. Nvidia 495.44-3, tried with gtx980 and 1060.

chris_l commented on 2021-11-06 00:30 (UTC) (edited on 2021-11-06 01:13 (UTC) by chris_l)

I've just updated to the 1.25.6 version. I don't know why, but now it works correctly, even when the package hasn't been updated.

Probably is thanks to the latest wine and/or nvidia drivers. For reference, in this moment I'm using nvidia 495.44-3, and wine 6.20-1.

chris_l commented on 2021-10-15 22:08 (UTC) (edited on 2021-10-15 22:08 (UTC) by chris_l)

The latest release 1.25.6 for some reason, in my tests, is really slow.

So, I'm not going to update the package until a new version comes out and fixes the speed.

If you want to test it, here is the PKGBUILD:

chris_l commented on 2021-10-03 20:34 (UTC)

If you are using yay, make sure to do a cleanBuild. Or don't use yay and manually download and build the package.

maykin-99 commented on 2021-08-30 19:25 (UTC)

You just need to check in if $HOME/.cemu exists and move it. And then use the new path instead of $HOME/.cemu.


if [ -d "$old_cemu_path" ] ; then
  mv "$old_cemu_path" "$cemu_path"

export WINEPREFIX="$cemu_path/wine"

// replace other occurrences of "$HOME/.cemu" or "~/.cemu" with "$cemu_path"

And then after same grace period until most have updated of a few weeks or months you can remove all referenced of old_cemu_path (or keep it if you want).

chris_l commented on 2021-08-21 07:04 (UTC)

That would have been a nice detail when I had just created the package, but right now it would only break the existing installations. And while I agree it would had been nice, well, I don't think its important enough right now.

Ta180m commented on 2021-08-19 18:03 (UTC)

Can the maintainer modify the script to use a directory like ~/.local/share/cemu instead of creating an unnecessary hidden folder ~/.cemu in the user's home directory?

chris_l commented on 2021-08-17 07:16 (UTC)

@linskun Yes it did! I just updated the package.

linskun commented on 2021-08-15 09:25 (UTC)

wxWidjet warning fixed on latest cemuhook 1251c_0575

chris_l commented on 2021-08-07 01:19 (UTC)

Updated to cemu 1.25.1c, which includes the new version of cemuhook for 1.25.1

Now with this version, I get the following message:

But after pressing Cancel, it works fine. So just press cancel and ignore it.

bigbruno commented on 2021-08-02 16:49 (UTC) (edited on 2021-08-02 16:54 (UTC) by bigbruno)

Modification suggestion for, inform winetricks that it is to use 32-bit vcrun, without it the cemu would not open on my PC.

Another point is a prettier method of using zenity, like a pulsating progress bar.

From this:

if [ ! -f "$HOME"/.cemu/wine/drive_c/windows/syswow64/vcruntime140.dll ]; then
  if [ -n "`whereis zenity|grep bin`" ]; then
    zenity --info  --title 'Cemu' --text 'Installing wine dependencies.\n\nThe process may take a few minutes'
  winetricks -q vcrun2017
  winetricks settings win7

To that:

if [ ! -f "$HOME"/.cemu/wine/drive_c/windows/syswow64/vcruntime140.dll ]; then
  if [ -n "`whereis zenity|grep bin`" ]; then
    winetricks arch=32 -q vcrun2017 | zenity --title 'Cemu' --text 'Installing wine dependencies.\n\nThe process may take a few minutes' --progress --pulsate --no-cancel --auto-close
  winetricks settings win7

guttles commented on 2021-06-15 17:44 (UTC)

After updating to 1.23.0c I am getting terrible stutter, would you know anything about that or how to fix it?

chris_l commented on 2021-05-12 06:20 (UTC) (edited on 2021-05-12 06:25 (UTC) by chris_l)

Since I got many reports after I updated the package, and that I have just test it again, and it works fine for me, maybe some of you are using a aur helper that is causing problems.

Try to do it manually:

cd ~
rm cemu.tar.gz
tar xzvf cemu.tar.gz
cd cemu
sudo pacman -U cemu-1.22.12-2-x86_64.pkg.tar.zst

I just did it, it works fine.

(yay in particular keeps a cache, including the old zip files here: ~/.cache/yay/cemu/. It will try to use those files when recompiling.)

chris_l commented on 2021-05-12 06:13 (UTC) (edited on 2021-05-12 06:16 (UTC) by chris_l)

@lucian I did saw your report yesterday, and I updated the package.

It is working now.

Edit: The report wasn't yours, my bad.

lucian commented on 2021-05-12 06:01 (UTC)

Validating Files failes - looks like they got updated ...

chris_l commented on 2021-03-22 08:45 (UTC)

@Toadfield Yes, pretty much every package in AUR that uses wine, will use whatever wine version you have installed.

Read the PKGBUILD, and it will have in depends just 'wine'. That means it uses whatever package you have installed that provides the "wine" dependency.

That means is up to you that the version you have installed is compatible.

Most of the time, the official default version is going to be compatible, but every once in a while, a wine update has broke cemu. In those cases I've downgrade wine, until a new working version comes out.

Toadfield commented on 2021-03-22 08:24 (UTC)

Which Wine version does this program use? Or does it just use my default wine version?

chris_l commented on 2021-02-02 04:16 (UTC)

@joserebelo Ok. It's done.

joserebelo commented on 2021-01-31 14:06 (UTC)

@chris_l Would you consider replacing Exec=/usr/bin/cemu with Exec=cemu, so that it can be easily overridden without editing the desktop entry? I believe that the same could apply to the Icon, so that it can be themed.

chris_l commented on 2020-11-24 02:14 (UTC) (edited on 2020-11-24 02:17 (UTC) by chris_l)

I just updated the package. It seems it got to 1.22.0k and its stable now. But, if later the package fails on the md5 checksum, just mark this package as out-of-date, and I'll fix it.

chris_l commented on 2020-11-22 00:29 (UTC)

Just to let you know, I did receive the out-of-date notification. But since yesterday, the Cemu team has released at least FOUR updates.

It was at 1.22.0g when I first checked, and now its at 1.22.0j. Those updates are, according to the changelog: Fixed even more race conditions which could lead to low performance, softlocks or crashes

So I'm planning to wait until it becomes more stable, and passes like a day or two without new releases.

chris_l commented on 2020-09-17 05:09 (UTC)

@raulcraveiro wine is not compatible by default. You'll need to patch wine. Check this post:

But, I don't use it with vulkan, so I haven't tried doing that.

raulcraveiro commented on 2020-09-17 04:18 (UTC)

How can I make the "Async compile (Vulkan)" work? I use a NVIDIA graphics card.

chris_l commented on 2020-07-15 06:02 (UTC)

@NBonaparte: Yep, me neither. I'm stuck with wine 5.11

NBonaparte commented on 2020-07-06 09:01 (UTC)

This probably isn't a problem with the AUR package itself, but does wine 5.12 work with Cemu? When I tried to run it, the window appears and immediately disappears.

chris_l commented on 2020-05-18 20:27 (UTC)

@chabad360, wine is not compatible by default. You'll need to patch wine for that. Check this post:

chabad360 commented on 2020-05-18 19:57 (UTC)

Every time I try to use Vulkan, I get:

Error when initializing Vulkan renderer:
Cannot create a Win32 Vulkan surface: -9

Any ideas?

chris_l commented on 2020-05-11 04:03 (UTC)

Well no.

The entire idea of this package is to provide an script (/usr/bin/cemu), that calls wine and uses the game data as if they were data files that wine will interpret, on its own wine environment. Its created following the "Wine package guidelines" (you can find it in the wiki). And if wine its not installed, executing /usr/bin/cemu will fail.

But, for your local installation, you can edit the PKGBUILD and manually remove the line:

depends=('wine' 'winetricks')

And after doing that, it will build it, without requiring you to install wine.

By the way, I tested cemu under proton, but I didn't get any improvement over running it under wine. Actually, it was slower, with stutters. Why are you running it like that?

alkazar commented on 2020-05-10 23:54 (UTC)

I run cemu with proton. Can the dependency on wine and winetricks be made optional?


Gathama commented on 2020-05-10 02:31 (UTC)

Thank you for the speedy and almost immediate fix. On a Sunday no less! Thanks alot man, I look forward to emulating some quality games

chris_l commented on 2020-05-10 02:22 (UTC)

@Gathama Yes, it seems the cemuhook author stopped offering a download to sharedFonts.7z. I replaced the url to a webarchive backup. Try again, it should work now.

Gathama commented on 2020-05-10 00:57 (UTC)

Hey, sorry I'm a noob but when attempting to install and access the file from the server. I believe there is an issue with this:

chris_l commented on 2020-04-08 03:06 (UTC) (edited on 2020-04-08 03:38 (UTC) by chris_l)

Updated to 1.18.0.

While this version includes many things that cemuhook provides, I'm still including it, because it seems the included H264 still doesn't work correctly. (on videos I get sound but no image, just a green screen)

If you want to try running cemu without cemuhook, just delete the symbolic link:

$ rm ~/.cemu/dbghelp.dll

If you later change your mind and want to restore it:

$ ln -sf /usr/share/cemu/dbghelp.dll ~/.cemu/dbghelp.dll

hbsbh81 commented on 2020-02-05 07:55 (UTC)

Also Pamac here. But only problem with cemu?

Did it manually, now it works. Thank you!

son_link commented on 2020-02-05 07:47 (UTC)

I use Pamac, but it's work with other AUR helper, pikaur.

chris_l commented on 2020-02-05 06:00 (UTC)

Well I'm sorry, but it works for me. I get ... Passed

How are you downloading the package? Are you using an aur helper? That may be the problem.

Try to do it manually:

curl ''|tar xzv && cd cemu && makepkg && sudo pacman -U cemu-1.17.0-2-x86_64.pkg.tar.xz

hbsbh81 commented on 2020-02-05 04:55 (UTC) (edited on 2020-02-05 04:55 (UTC) by hbsbh81) ... FAILED ... Passed
sharedFonts.7z ... Passed

==> ERROR: One or more files did not pass the validity check! Failed to build cemu

chris_l commented on 2020-02-04 22:44 (UTC)

@son_link: Can not replicate. I see that you flag it out-of-date and you said that it gives you an md5 checksum error. But I just download it and rebuild it with no problems.

vectro commented on 2019-12-25 03:07 (UTC)

@dnmodder Thanks!! Works great. Wish I knew about wine-tkg sooner, what a painless configuration.

Oh and I accidentally deleted my original question, for those wondering dnmodder gave a solution for vulkan compatibility.

dnmodder commented on 2019-12-25 02:07 (UTC)

@vectro you need to use wine-tkg with the vkchildwindow patch activated

chris_l commented on 2019-12-24 02:19 (UTC) (edited on 2019-12-24 02:20 (UTC) by chris_l)

@dnmodder Fixed!

But, I didn't had any problems with mlc01, only with hfiomlc01.

dnmodder commented on 2019-12-23 15:20 (UTC)

mlc01 and hfiomlc01 do not exist

chris_l commented on 2019-12-22 00:10 (UTC) (edited on 2019-12-22 00:27 (UTC) by chris_l)

@Neros fixed. However, I would like to mention that I did tested the package before submitting the change, and it worked fine for me.

So I assume they recently changed the zip file giving it the same name (which is something cemuhook used to do a lot in the past)

EDIT: And if you check the "About" dialog, it says it was compiled today, at 14pm. So yeah, thats what they did.

Neros commented on 2019-12-21 13:16 (UTC) (edited on 2019-12-21 13:17 (UTC) by Neros)

md5sums not valid for

==> Validating source files with md5sums... ... Passed
    cemu.xpm ... Passed
    cemu.desktop ... Passed ... FAILED ... Passed
    sharedFonts.7z ... Passed
==> ERROR: One or more files did not pass the validity check!

amathadius commented on 2019-10-10 16:50 (UTC) (edited on 2019-10-10 16:52 (UTC) by amathadius)

Speakers buzz, Cemu crashes and "/usr/bin/cemu : ligne 36 : 61381 Erreur de segmentation (core dumped)wine Cemu.exe "$@"" appears in terminal when I want to launch Zelda BOTW. I never managed to make it works.

chris_l commented on 2019-10-10 03:42 (UTC)

@Devorlon No, is not possible. Cemu is not being compiled for this package, it only packages the windows binaries.

However, you could try to run it from a terminal like this:

WINEDEBUG=warn+all cemu

to get a more verbose output.

Devorlon commented on 2019-10-09 11:36 (UTC) (edited on 2019-10-09 11:36 (UTC) by Devorlon)

@chris_l Is it possible to enable a verbose output? I'm getting random crashes and would like to know the reason?

dack commented on 2019-10-04 04:54 (UTC)

@chris_l That totally works, thanks! I was looking everywhere in the config for some settings relating to cemuhook H264 - never thought to check the debug menu.

dnmodder commented on 2019-10-02 00:22 (UTC)

I have been able to notify the best audio quality using XAudio, but since I use wine-tkg I don't need it, because it is already integrated with FAudio to meet that need.

chris_l commented on 2019-09-29 00:03 (UTC) (edited on 2019-09-29 01:31 (UTC) by chris_l)

@quebin31 I have tried it, but I didn't see any difference. I'm not sure about adding an extra dependency, but you can manually install the support for it on your installation with:

WINEPREFIX="$HOME/.cemu/wine" winetricks xact

Why you want to use XAudio?

chris_l commented on 2019-09-28 23:58 (UTC)

@dnmodder Ok, done.

chris_l commented on 2019-09-28 23:55 (UTC)

@dack Go to Debug->Use Cemuhook H264

dack commented on 2019-09-28 19:13 (UTC)

Anyone else getting green screen during botw cutscenes? It also spits out this to the console when a cutscene starts:

005b:err:d3d:wined3d_context_gl_init Failed to set pixel format 27 on device context 0x120078.

Maybe some tweak to the wine environment is needed? Usual advice for botw green screen cutscenes is "install cemuhook", but that's already in there.

dnmodder commented on 2019-09-28 18:40 (UTC) (edited on 2019-09-28 18:41 (UTC) by dnmodder)

Can you add this to the desktop file?:



This is for the icon in the task manager, in the panel, I tried it in Plasma 5.

quebin31 commented on 2019-08-30 23:33 (UTC)

Can you add support for XAudio?

chris_l commented on 2019-08-10 04:07 (UTC) (edited on 2019-08-10 04:08 (UTC) by chris_l)


nice! Sorry, my monitor don't go to that resolution, so I have no idea.

vectro commented on 2019-08-10 03:02 (UTC) (edited on 2019-08-10 03:02 (UTC) by vectro)

@chris_l, I'm actually running at 1440p using the graphics packs, yet I get extreme blur when the window size is set any larger (in my case 3840p). My only workaround is to set my xrandr resolution to 1440p before launching CEMU. Any idea why this would be needed?

chris_l commented on 2019-08-10 02:47 (UTC)

@vectro, it sounds like you aren't using the community graphic packs.

Install them, and activate botw->graphics->resolution and set as active preset the resolution of your monitor. You'll get better quality than letting your monitor to upscale the default low resolution of the game.

vectro commented on 2019-08-10 01:07 (UTC)

For anyone getting blurry graphics in BOTW: Set your xrandr resolution to match exactly the resolution set in CEMU, and then run the game full screen. I tried changing the wine settings to avoid this as well as the CEMU settings, with no luck. It seems wine doesn't upscale nicely. Hope this helps.

dnmodder commented on 2019-08-01 16:12 (UTC) (edited on 2019-08-01 16:21 (UTC) by dnmodder)

I understand what you mean, but those variables are not there because they are, they are there to get the maximum performance possible. If you want more information about GL Threaded Optimizations I leave these links:

mesa_glthread is the equivalent for AMD / Intel and it is recommended to have the vsync disabled, but I don't know how well it works, also a detail is that apparently GL Threaded Optimizations can decrease performance if your CPU is 100%, in my case I get these results:

chris_l commented on 2019-07-29 19:43 (UTC)

I found a good reason for R600_DEBUG=nohyperz. It allows users of AMD Polaris cards to play botw. So I'm going to add at least that one the next version.

Still checking about the other two.

chris_l commented on 2019-07-29 19:19 (UTC) (edited on 2019-07-29 19:23 (UTC) by chris_l)

Well no, I'm not going to blindly copy everything cemutil does, I need to know whats the purpose of adding them.

Particularly, I don't agree the inclusion of vblank_mode=0.

That flag disables vblank, and disabling it can produce tearing. Someone with a weak video card can benefit from that, but the people with more capable cards could get unnecessary tearing.

That is, if someone wants to play with that flag on, they can apply them themselves.

But, if you know what the other flags do, and they are useful, let me know, and I will check them.

dnmodder commented on 2019-07-29 14:07 (UTC) (edited on 2019-07-29 14:08 (UTC) by dnmodder)

You should also add the environment variables __GL_THREADED_OPTIMIZATIONS=1, mesa_glthread=true, R600_DEBUG=nohyperz and vblank_mode=0 to the file, so it would be on par with the Lutris and Cemutil script

chris_l commented on 2019-07-29 09:51 (UTC)

@barfin, in my previous comment I mentioned that I was working on the shared fonts part.

It took me a while because I wanted to download the fonts from an official source and I had to find a link for that (that script its just getting the fonts from a zip file in their own repo)

Anyway, its done now.

commented on 2019-07-28 20:44 (UTC)

exactly shared fonts cannot be downloaded in cemu using wine and this script does that i wish you could just add them so i would use this aur package instead of that script

dnmodder commented on 2019-07-28 20:20 (UTC)

well, another thing, can you add the shared fonts too?

chris_l commented on 2019-07-26 00:05 (UTC)

hehe, actually I have started to test vcrun2017 for a while.

Why vcrun2015? Because its the one that was suggested for cemu, back when this package was new, and it worked fine.

Then I noticed that the cemutil script was using vcrun2017 instead, so I decided to try vcrun2017 in my local installation, and then play for a few hours.

So far so good, so I probably will submit a new version using it soon.

dnmodder commented on 2019-07-25 13:18 (UTC)

Why vcrun2015 instead vcrun2017?

chris_l commented on 2019-07-23 21:44 (UTC)

@pepper_chico, removed the winetricks check.

@barfin, gameProfiles is no longer a symlink, now is a copy instead.

pepper_chico commented on 2019-07-23 17:45 (UTC)

@barfin game profile editing doesn't work because the profiles directory put in your home folder is simply a symbolic link to a system folder that needs root access for writing. Maybe this needs to get fixed in (besides fixing the winetricks list-installed|grep vcrun2015 check).

commented on 2019-07-17 13:38 (UTC)

edit game profile does not work also there is no shared fonts take a look at this script

chris_l commented on 2019-07-10 02:19 (UTC)

And yes, I also had to downgrade wine. :/

chris_l commented on 2019-07-10 02:11 (UTC)

It takes a lot of time? In my system takes 3 seconds to do that.

Now, in a failed, or old installation of this package, the .cemu dir could exist, without having vcrun2015 installed, that's why I'm explicitly checking for it.

But, maybe I can look for the presence of the file itself, instead of asking winetricks. So, yeah, I'm gonna try that change.

pepper_chico commented on 2019-07-10 01:42 (UTC) (edited on 2019-07-10 01:46 (UTC) by pepper_chico)

I've noticed that the wrapper adds a check winetricks list-installed|grep vcrun2015 which takes considerable time. This add an increase in the loading time of cemu on every execution, while this test is needed solely in the first time it's executed. Maybe deps should be assumed installed if "$HOME"/.cemu exists?

notice: wine 4.12-1 is broken for me (wine: Unhandled page fault on write access to 0x00000000), I had to downgrade to 4.11-1.

amathadius commented on 2019-06-30 00:19 (UTC) (edited on 2019-06-30 00:25 (UTC) by amathadius)

It works for everybody, but I've never been able to launch any game : Cemu compile shaders and crash.

chris_l commented on 2019-06-27 01:59 (UTC)

Finally updated! Sorry for the time, and thanks @pepper_chico for the patch

laichiaheng commented on 2019-06-18 18:37 (UTC)

Out of date!

ivanmlerner commented on 2019-05-30 00:59 (UTC)

Graphics pack can now be installed directly from Cemu gui, no need to install it with Cemu.

pepper_chico commented on 2019-05-14 21:58 (UTC)

I'm not sure gameProfiles should be linked in the home folder instead of copied, because if you need to change a specific one, you'll need root access.

pepper_chico commented on 2019-04-29 07:21 (UTC) (edited on 2019-05-12 19:12 (UTC) by pepper_chico)


I've discovered that in latest cemuhook you have to have h264 decoder turned on in debug options, that fix BOTW green screen cut-scenes.

I've emailed the cemuhook author about the debug assert popup issue, I'm not sure it was due to that but now in 1155_0572 this is solved, there's no controller issue anymore. So the above patch have all those issues fixed.

pepper_chico commented on 2019-04-15 15:33 (UTC)

@Hengi I play ZBOTW without any of those flags.

Hengi commented on 2019-04-13 09:46 (UTC) (edited on 2019-04-13 09:48 (UTC) by Hengi)

consider adding the necessary wine args to the cemu launch script. Games like Breath of the Wild don't work without R600_DEBUG=nohyperz

R600_DEBUG=nohyperz __GL_THREADED_OPTIMIZATIONS=1 mesa_glthread=true vblank_mode=0 WINEESYNC=1

These should be added to wine Cemu.exe "$@"

also, cemuhook will still be needed, as the native cemu h264 doesn't and might never work on Wine.

Also, it is recommended to build wine-tkg for yourself.

BrianAllred commented on 2019-04-02 19:35 (UTC)


Ah, my mistake. I didn't have a controller plugged in, so I didn't make the connection. But I had the xboxdrv service running, which says there's a controller present even when there's not. Stopping that service fixed the issue.


pepper_chico commented on 2019-04-02 15:31 (UTC)

@SilverMight @BrianAllred

Check previous messages where that issue is explained. One fix is to not have controller connect before launching cemu, the other is downgrading.

SilverMight commented on 2019-04-02 02:47 (UTC)

@BrianAllred Getting the same thing now

BrianAllred commented on 2019-03-31 19:24 (UTC)

I get the following segfault when running cemu. Any ideas?

pepper_chico commented on 2019-03-30 06:15 (UTC)

@chris_l I've replaced one Cemu.exe binary for the other older one, but graphical quality dropped a lot. Seems not worth.

chris_l commented on 2019-03-30 02:52 (UTC) (edited on 2019-03-30 02:52 (UTC) by chris_l)

Well, the advice they give is basically to stick to cemu 1.15.0

You guys can do that, by cloning the repo of this package and resetting the commit to that version:

git clone

cd cemu

git reset --hard 6dd239bf8931


pepper_chico commented on 2019-03-30 02:30 (UTC)

It looks like this thread has shown how to fix the controller issue:

pepper_chico commented on 2019-03-30 02:22 (UTC)

@chris_l regarding actually solving the cemuhook bug, I think we can have that fixed for good reporting upstream, it seems it's some trivial fix about avoiding asserts on release.

pepper_chico commented on 2019-03-30 02:18 (UTC) (edited on 2019-03-30 02:19 (UTC) by pepper_chico)

@chris_l thanks for that info, I was suspecting that.

I'm interested in avoiding such issues because I want to setup to start games from inside Steam, I want to use cemu -f -g "Z:/<game path>.rpx" to start games without invoking any Wine GUI.

So, may I ask on another issue I'm having? I'm using xbox 360 controllers, and all is fine if I start cemu before connecting the controller, but if I have the controller already connected, cemu crashes on launching. Any idea how to avoid that?

I need these two fixed to have a game launch without problems.

chris_l commented on 2019-03-30 01:41 (UTC)

@pepper_chico Yes, I know. That bug is caused by cemuhook. If you stop using the dbghelp.dll library, the error will go away... and you wont be using cemuhook anymore!

If someone knows how to use cemuhook AND prevent that error, I gladly change the package for that. But in the meantime, is not a big deal.

pepper_chico commented on 2019-03-30 01:05 (UTC)

Anyone knows how to fix the "wxWidgets Debug Alert"? It shows up anytime I start cemu, I have to cancel to proceed.

chris_l commented on 2019-02-12 20:57 (UTC)

@GeoffreyFrogeye Ok then, I have changed those lines. I hope its going to be at last the end of that bug. Thanks for your contribution!

GeoffreyFrogeye commented on 2019-02-12 17:46 (UTC) (edited on 2019-02-12 17:46 (UTC) by GeoffreyFrogeye)

So I dig up a bit this ../../ ../ issue, because I did try without any aur helper and on different installations and I was fed up with removing it for every update :D. Turns out that what the installations on which it fails have in common is the fact that the BUILDDIR variable is set in makepkg.conf. So if it is set, it works for ../ and if it is not set (I can't remember if it is the default or not) it worjs for ../../. There is a simple fix however, you just need to give the full path for the bsdtar arguments, and it works in both cases, see the following diff:

chris_l commented on 2019-01-21 05:08 (UTC)

For some reason, cemu 1.15.1e gives me a seg fault. If anyone want to try it, I'll leave the PKGBUILD here:

I'll update the package as soon as I manage to get it to work.

chris_l commented on 2019-01-05 22:59 (UTC)

@Enverex Is not the first time I get a comment reporting that. The problem is that I cannot replicate it; it works for me. I have tried on at least 3 different arch installations and I never get that error.

On the other hand, if I remove the "../", then it stops working. Are you using an AUR helper? Have you tried to do it manually?

Try it, manually download the snapshot, untar it, and execute makepkg.

Enverex commented on 2019-01-05 15:33 (UTC) (edited on 2019-01-05 15:33 (UTC) by Enverex)

You've got too many "go up a level" entries in the PKGBUILD file. Removing one "../" from each of the two bsdtar commands results in a successful build. The files are only one level above the current directory so I'm not sure why the script tries to go back up two levels in each case.

agapito commented on 2018-11-30 11:13 (UTC)

I have the same problem.

bsdtar: Error opening archive: Failed to open '../../'

chris_l commented on 2018-11-03 02:12 (UTC) (edited on 2018-11-03 02:13 (UTC) by chris_l)

I don't know why you have that problem. It works for me.

The way I tested it was like this:

  • Downloaded it by clicking on the "download snapshot" link.
  • tar xzvf cemu.tar.gz
  • cd cemu
  • makepkg
  • sudo pacman -U cemu-1.14.0-1-x86_64.pkg.tar.xz

And it just works. I didn't have to change anything on the PKGBUILD. Then I also tried to do it with yaourt. It also worked.

GeoffreyFrogeye commented on 2018-11-02 21:23 (UTC)

I could only build the package by changing ../../cemuhook_${cemuhookver}.zip byr ../cemuhook${_cemuhookver}.zip (same for graphicPacks) in the PKGBUILD, is this only me?

On an unrelated note if the package size droped by ~200 MiB that's normal, if I understand correctly the graphic packs got optimized a lot.

IMHO cemu, the graphics packs and cemuhook should be split in three different packages, to follow the Arch guidelines.

Yosh commented on 2018-11-02 18:53 (UTC)

1.14 is out.

Yosh commented on 2018-10-20 19:33 (UTC)

Can't built it anymore

chris_l commented on 2018-04-22 07:35 (UTC)

@DocMAX: Yes, but that line is what allows the emulator to use the cemuhook plugin. (if you remove it, it no longer uses cemuhook. You can see if the plugin is loaded on the status bar)

DocMAX commented on 2018-04-22 07:26 (UTC) (edited on 2018-04-22 07:27 (UTC) by DocMAX)

dbghelp.dll=n,b ...causes wxWidget error.

chris_l commented on 2018-02-04 00:13 (UTC)

And now is updated to Cemuhook (which has ec369cdf61ce3b6becce584c5c976939 as md5 at this moment, btw)

chris_l commented on 2018-02-03 23:46 (UTC) (edited on 2018-02-03 23:47 (UTC) by chris_l)

@thelongdivider about the ../ on the build commands, well, that is something I can't replicate. It works for me without removing them, and actually, it stops working if I remove them.

chris_l commented on 2018-02-03 23:26 (UTC) (edited on 2018-02-03 23:42 (UTC) by chris_l)

@thelongdivider Oh, every once in a while the cemuhook team releases something that I call "silent updates"; What they do, is they replace the cemuhook plugin with a new version, but under the same filename and the same url.

That new file has, of course, a different md5. Even if the name and url is the same.

So when that happens, the package stops working and I have to manually adjust it to the new md5. It would be ideal if they create a new file version for each change. I guess they do it like this because the changes must be minimal or something.

Anyway, I just adjusted it again.

But also, I have notice there is a new version of the cemuhook plugin, so in a few minutes I will update the package to that new version.

thelongdivider commented on 2018-02-03 16:23 (UTC) (edited on 2018-02-03 16:47 (UTC) by thelongdivider)

Does this package actually build naturally for anyone? My errors include md5sum errors, directory errors, etc.

The easiest fix is to manually edit the md5 for the to '79649bafa0457c83ab938114cbad8ecf', and then to remove one of the ../ in each of the build() commands.

NBonaparte commented on 2018-01-06 08:07 (UTC)

Seems to work fine, thanks for the changes!

chris_l commented on 2018-01-05 01:32 (UTC)

Btw, thanks a lot for the tip about QPC, the MM timer and the link to the reddit guide. It really improves the experience! :D

chris_l commented on 2018-01-05 01:31 (UTC) (edited on 2018-01-05 01:33 (UTC) by chris_l)

Ok, the new version uses winetricks to install vcrun2015 and after that it sets the windows version as win7. (btw, that also means that winetricks is now a dependency)

It works perfectly for me, but could you test if it works correctly on your system? (you could temporally rename you ~/.cemu for that. Because if vcrun2015 is already installed on your .cemu, it wont be installed again)

NBonaparte commented on 2018-01-02 06:55 (UTC)

With the dual/triple core recompiler loading times can be slow, so changing the custom timer to QPC fixes this. With FPS++ stuttering can be fixed by changing MM timer to Highest or 1ms. (both found from the guide

chris_l commented on 2018-01-02 06:50 (UTC)

ohh, I see! Is just that I have never used those options myself before. Why do you use those options? (maybe I should be using them myself!)

And I'll check about the possibility of including vcrun2015 somehow.

NBonaparte commented on 2018-01-02 06:33 (UTC) (edited on 2018-01-02 06:46 (UTC) by NBonaparte)

cemu gives fixme:msvcp warnings and crashes when changing the timer and MM timer accuracy when vcrun2015 isn't installed. Apparently, when installing vcrun2015 through winetricks the version changes to XP (run winetricks vcrun2015 win7 to fix this).

chris_l commented on 2018-01-02 06:26 (UTC)

About why the .cemu dir is created on the, the reason is on multi-user systems, every user should have their own settings. If user Bob install cemu, and later a new user Alice executes cemu, she should have her own .cemu directory.

You can see the example for the /usr/bin script on the Wine package guidelines:

chris_l commented on 2018-01-02 06:22 (UTC) (edited on 2018-01-02 06:27 (UTC) by chris_l)

About the vcrun2015 and the windows version, I can't replicate that problem.

I don't have vcrun2015 installed on the local ~/.cemu/wine directory and cemu works fine for me. Also, the version of wine is automatically set as windows 7, not XP. Is your Arch fully updated?

chris_l commented on 2018-01-02 06:15 (UTC) (edited on 2018-01-02 06:19 (UTC) by chris_l)

Sigh. About the md5 of cemuhook, yes is not the first time cemuhook developers change the file, but conserve the name. That is, yesterday, they released the new version under the name "", and today they changed the file, but they are still using the same filename. A different file, with the same name. So, as long the cemuhook devs continue to do that, every once in a while the aur package will break.

NBonaparte commented on 2018-01-02 05:39 (UTC)

vcrun2015 should be installed through winetricks or some other method, as it is a dependency of cemu. Also, the Windows version should probably be set to Vista or higher. For me the cemuhook options show up as blank with the version set to Windows XP.

Shouldn't creating .cemu be done in cemu.install rather than in

chris_l commented on 2017-12-15 03:24 (UTC)

Sorry! fixed now.

Zacharybinx34 commented on 2017-12-14 19:47 (UTC)

Same issue as Conspiracy - Error opening archive: Failed to open '../../../'

Conspiracy commented on 2017-12-14 11:33 (UTC) (edited on 2017-12-14 11:33 (UTC) by Conspiracy)

I tried to update to 1.11.2-1 and recieved an error:

bsdtar: Error opening archive: Failed to open '../../../'