Package Details: unigine-heaven 4.0-2

Git Clone URL: https://aur.archlinux.org/unigine-heaven.git (read-only, click to copy)
Package Base: unigine-heaven
Description: Unigine Benchmark
Upstream URL: http://www.unigine.com
Licenses: custom:UNIGINE Engine
Submitter: None
Maintainer: xythrez
Last Packager: xythrez
Votes: 159
Popularity: 0.21
First Submitted: 2010-03-24 15:44 (UTC)
Last Updated: 2019-06-21 03:37 (UTC)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

paum commented on 2025-12-21 20:59 (UTC)

Solution for: 'Can't open "../data/launcher/launcher.xml" data folder is not readable for user. cd /opt/unigine-heaven/ && sudo chown -R $USER:$USER .

LinuxLover471 commented on 2025-11-27 13:06 (UTC)

Doesn't build because of sha512sums mismatch. I tried building twice in empty directories by aurutils, gets fixed by executing updpkgsums.

Also the installed binary "unigine-heaven" doesn't work, it fails with 'Can't open "../data/launcher/launcher.xml" config' dialog box.

kode54 commented on 2025-10-15 05:35 (UTC)

Why doesn't this have a .desktop file?

Darian78 commented on 2023-04-09 19:10 (UTC) (edited on 2023-04-09 19:19 (UTC) by Darian78)

Install of all unigine packages in AUR fail with the following error:
"-t: Unknown option":
Unigine_Valley-1.0.run: Zeile 312: exec: -t: Ungültige Option.

Full output:

Erstelle unigine-valley...
==> Erstelle Paket: unigine-valley 1.0-1 (So 09 Apr 2023 21:08:22 CEST)
==> Prüfe Laufzeit-Abhängigkeiten...
==> Prüfe Buildtime-Abhängigkeiten...
==> Empfange Quellen...
-> Unigine_Valley-1.0.run gefunden
-> unigine-valley.desktop gefunden
==> Überprüfe source Dateien mit sha512sums...
Unigine_Valley-1.0.run ... Erfolg
unigine-valley.desktop ... Erfolg
==> Entferne existierendes $srcdir/ Verzeichnis...
==> Entpacke Quellen...
==> Entferne existierendes $pkgdir/ Verzeichnis...
==> Beginne build()...
Unigine_Valley-1.0.run: Zeile 312: exec: -t: Ungültige Option.
exec: Aufruf: exec [-cl] [-a name] [command [argument ...]] [redirection ...]
==> FEHLER: Ein Fehler geschah in build().
Breche ab...

tinywrkb commented on 2021-11-22 22:10 (UTC)

@xythrez you can avoid executing the installer by running something like this:

dd iflag=skip_bytes \
  skip=$(head -n 403 heaven-installer.run | wc -c ) \
  if=heaven-installer.run |
  bsdtar -xf - \
  --exclude='*x86*' \
  --exclude=./heaven \
  --exclude=./bin/x64

PedroSnow commented on 2021-11-02 02:33 (UTC)

Here the issue was with pamac too, it works fine with makepkg. Strange.

Lone_Wolf commented on 2021-07-03 19:44 (UTC)

builds fine with makepkg.

Try building that way to verify if the issue is with pamac or your setup.

Alkaris commented on 2021-06-09 04:59 (UTC)

No idea what is up with this package, but it downloads the package, but then turns around and says it cannot find said package???

==> Validating source files with sha512sums...
    Unigine_Heaven-4.0.run ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
==> Starting build()...
==> Entering fakeroot environment...
==> Starting package()...
/var/tmp/pamac-build-user/unigine-heaven/PKGBUILD: line 27: cd: /var/tmp/pamac-build-user/unigine-heaven/src/Unigine_Heaven-4.0: No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

How do you not find a package that's downloaded and in the /var/tmp/pmac-build-user/unigine-heaven directory, that makes no sense.

LizziAS commented on 2020-12-24 01:47 (UTC)

@xythrez sorry i missed that. will do. i had 3 out of 5 fail to d/l so i got hasty i guess.

1 2 3 4 5 6 7 Next › Last »