Package Details: dolphin-emu-git 4.0.2.r8743.3a12dcc-1

Git Clone URL: (read-only)
Package Base: dolphin-emu-git
Description: A GameCube / Wii / Triforce emulator
Upstream URL:
Licenses: GPL2
Conflicts: dolphin-emu
Provides: dolphin-emu
Submitter: None
Maintainer: alucryd
Last Packager: alucryd
Votes: 76
Popularity: 2.817619
First Submitted: 2011-08-20 13:05
Last Updated: 2016-01-21 07:32

Latest Comments

nicman23 commented on 2016-05-06 11:35

is there any reason performance or stability wise, to compile with clang?

Neros commented on 2016-04-15 23:18

Dolphin-emu is still super slow with the new Nvidia driver 364.16 (it was all good months ago).
Does anyone know why? Is there a solution?
Because now, sadly, I have to run dolphin on Windows if I want to play :(

Martchus commented on 2016-03-16 17:57

I'm also using NVIDIA and noticed that the performance is very impaired in some cases. I don't know since when exactly, because I'm not playing regularly.

I switched from the regular package to this Git version and it actually helped. However, I am still using the version which has pie enabled because I accidentally used an older version of the PKGBUILD. Because this is working for me, I'm currently not rebuilding.

Additionally, the compositor seems to have a big impact on the performance. Under Plasma 5 with KWin I just get around 20 FPS playing Wind Waker with the best settings. Disabling the compositor doesn't help (alt + shift + F12) and just causes the Plasma shell to stop updating so the Plasma shell is more or less unusable. However, when starting a plain Open Box session, I can play with the same setup with almost 60 FPS. This is also the case when playing other games without emulation, e.g. Talos Principle.

But Dolphin is always using 2 cores for me.

SuperIce97 commented on 2016-03-16 04:45

@Neros: You're not the only one. I literally just bought a Gamecube to USB adapter to play Metroid Prime and I tried the game again and it's running much slower than it did a month ago. I tried reverting to nvidia-352 but it ran the same. I even tried an older kernel and that didn't help. I'm not quite sure how to fix this, but one thing I noticed is that dolphin is only using one CPU thread, when it should be using 2. Does anyone have any ideas on what this could be or how to fix it?

Neros commented on 2016-03-09 17:14

It seems that dolphin doesn't work good with the last nvidia driver 361.28. All the games are as slow as if I was using the Intel card...
Am I the only one?

Martchus commented on 2016-02-29 14:34

Thanks for the reply. Seems I accidentally used an old version of the PKGBUILD.

I also read the comment from the Dolphin dev about the pie flag. Seems I'm luckily not immediately affected by the bug.

That the Qt GUI is currently broken is not a big deal since there haven't been a lot of features implemented yet.

rubic commented on 2016-02-29 07:18

Those changes appear to already be in the PKGBUILD.

However, DolphinQt2 is broken in the latest PKGBUILD as -fno-pie is enabled.
Qt requires pie and we are waiting on a pull request that ensures the -fno-pie flag is not applied to it.

Martchus commented on 2016-02-28 22:23

Dolphin devs seem to call the Qt GUI now Qt2.

and Binaries/dolphin-emu-qt is now Binaries/dolphin-emu-qt2
which has to be removed within package_dolphin-emu-git():
rm -rf "${pkgdir}"/usr/bin/dolphin-emu-qt2

linkmauve commented on 2016-02-26 11:24


Please remove the -DENABLE_SDL=TRUE, as it’s been deprecated on Linux, so libevdev will be used instead.

Also, have a run of namcap on the generated packages, you are missing things like hicolor-icon-theme or a .install script to run xdg-icon-resource.


Yann.O commented on 2016-02-02 21:39

Thanks for adding the "-fno-pie" flag. I've been relying on customize-pkg to patch the PKGBUILD for a while now seeing as this modification was previously refused.

Now Dolphin-git can be compiled and run without this annoying bug.

All comments