Package Details: dolphin-emu-git 2409.r37.g6851ed73f4-1

Git Clone URL: https://aur.archlinux.org/dolphin-emu-git.git (read-only, click to copy)
Package Base: dolphin-emu-git
Description: A Gamecube / Wii emulator - git version
Upstream URL: https://dolphin-emu.org
Keywords: dolphin emu emulator game gamecube gui nintendo remote revolution triforce wii wiimote
Licenses: GPL-2.0-or-later
Conflicts: dolphin-emu
Provides: dolphin-emu
Submitter: None
Maintainer: dpeukert
Last Packager: dpeukert
Votes: 122
Popularity: 0.41
First Submitted: 2011-08-20 13:05 (UTC)
Last Updated: 2024-09-17 18:04 (UTC)

Dependencies (54)

Required by (3)

Sources (8)

Pinned Comments

dpeukert commented on 2020-04-10 12:34 (UTC) (edited on 2020-09-26 17:48 (UTC) by dpeukert)

The PKGBUILD for this package is hosted here (contributions are welcome!): https://gitlab.com/dpeukert/pkgbuilds/tree/main/dolphin-emu-git

Latest Comments

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 56 Next › Last »

SuperIce97 commented on 2016-03-16 04:45 (UTC) (edited on 2016-03-16 04:45 (UTC) by SuperIce97)

@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 (UTC) (edited on 2016-03-16 22:39 (UTC) by Neros)

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 (UTC)

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 (UTC)

Martchus: 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. https://github.com/dolphin-emu/dolphin/pull/3612/files

Martchus commented on 2016-02-28 22:23 (UTC)

Dolphin devs seem to call the Qt GUI now Qt2. Hence -DENABLE_QT='TRUE' is now -DENABLE_QT2='TRUE' 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 (UTC)

Hi, 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. Thanks.

Yann.O commented on 2016-02-02 21:39 (UTC)

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.

alucryd commented on 2016-01-21 14:20 (UTC)

Thanks for the explanation, we do have ASLR enabled by default, I guess my play sessions were just never long enough to trigger the error.

Sonicadvance1 commented on 2016-01-21 08:21 (UTC)

Due to how memory allocation works, especially on a system without ASLR enabled. You may get lucky up until a point and it would be allocating memory in the virtual memory space <4GB. Eventually this memory space will be exhausted and then at that point Dolphin will spit out an error. So there is a variety of factors that can cause it to break immediately or still take a decent amount of play time due to luck.

alucryd commented on 2016-01-21 07:33 (UTC)

Thanks for the info. I still can't help but wonder, if it completely breaks CPU emulation, why is it I have never experienced the issue nor got any bug report for the stable package in [community]? Does it really affect everyone or only a subset? FTR, I have never explicitely enabled PIE, it's on by default, you might want to consider disabling it by default on everything not AArch64. Anyway, just pushed an updated PKGBUILD.