Package Details: epsxe 2.0.5-24

Git Clone URL: (read-only, click to copy)
Package Base: epsxe
Description: Enhanced PSX emulator
Upstream URL:
Keywords: emulator playstation
Licenses: unknown
Replaces: bin32-epsxe
Submitter: None
Maintainer: hav3lock
Last Packager: hav3lock
Votes: 220
Popularity: 1.13
First Submitted: 2007-05-02 16:59
Last Updated: 2020-04-27 19:00

Latest Comments

1 2 3 4 5 6 ... Next › Last »

hav3lock commented on 2020-04-29 21:40

In the next few weeks I'll be adding upstream shaders to this package.

Konzertheld commented on 2020-04-27 19:13

@hav3lock Confirmed. Thanks for the change!

hav3lock commented on 2020-04-27 19:05

@tallero Issues with the actual emulator itself should be reported to upstream. I only maintain the AUR package for epsxe.

hav3lock commented on 2020-04-27 19:02

Epsxe no longer requires ncurses5-compat-libs. This package also now supports i686 again.

Konzertheld commented on 2020-04-27 16:44

Workaround: Build ncurses5-compat-libs yourself.

  1. Clone the ncurses5-compat-libs git repository
  2. Check out this commit
  3. Run makepkg -si
  4. Install epsxe

caesarhenrique commented on 2020-04-24 12:43


$ epsxe

/opt/epsxe/epsxe: /usr/lib/ version `NCURSES_5.0.19991023' not found (required by /opt/epsxe/epsxe)

/opt/epsxe/epsxe: /usr/lib/ no version information available (required by /opt/epsxe/epsxe)

aki42 commented on 2020-04-23 14:24

Same as A.J like below.

$ epsxe

/opt/epsxe/epsxe: /usr/lib/ version `NCURSES_5.0.19991023' not found (required by /opt/epsxe/epsxe)

/opt/epsxe/epsxe: /usr/lib/ no version information available (required by /opt/epsxe/epsxe)

A.J commented on 2020-04-22 10:24

not working with the latest ncurses5-compat-libs

ZimbiX commented on 2020-04-05 02:57

Curiously, I'm getting an error from the find command:

find: The current directory is included in the PATH environment variable, which is insecure in combination with the -execdir action of find. Please remove the current directory from your $PATH (that is, remove ".", doubled colons, or leading or trailing colons)

My $PATH doesn't have anything like that, so that's confusing.

I don't need the docs, so I just commented out the find and then it builds fine.

Edit: Nevermind; user error! I was removing paths programmatically to avoid other path complaints from find, and didn't realise I was ending up with a trailing colon. Here's what worked:

PATH=$(echo -n $PATH | tr : '\n' | grep -vE '(~|/home)' | sed -z '$ s/\n$//' | tr '\n' :) yay -S epsxe

tallero commented on 2020-01-26 04:19

crashing on "Generator room" in Crash Bandicoot.