Package Details: unreal-engine 5.5.0-0

Git Clone URL: https://aur.archlinux.org/unreal-engine.git (read-only, click to copy)
Package Base: unreal-engine
Description: A 3D game engine by Epic Games which can be used non-commercially for free.
Upstream URL: https://www.unrealengine.com/
Keywords: 3D engine game ue5 Unreal
Licenses: GPL3, custom:UnrealEngine
Submitter: acerix
Maintainer: Shatur
Last Packager: Neko-san
Votes: 76
Popularity: 0.045758
First Submitted: 2016-05-01 18:37 (UTC)
Last Updated: 2024-11-16 03:10 (UTC)

Dependencies (29)

Required by (1)

Sources (6)

Pinned Comments

Neko-san commented on 2022-11-01 02:32 (UTC) (edited on 2023-06-25 01:19 (UTC) by Neko-san)

@juancarlospaco this is easily done on your own system, not in a PKGBUILD, given that building packages runs as root:

sudo groupadd unrealengine-users
sudo usermod -aG unrealengine-users (your-username)
sudo chown -R root:unrealengine-users /opt/unreal-engine
sudo chmod -R 775 /opt/unreal-engine

Permission issues like this are already mentioned on the UE Arch wiki page: https://wiki.archlinux.org/title/Unreal_Engine_4#Installing_from_the_AUR

This is a user system problem; I already did what I could without needing users to do the above by giving the 777 permissions. If it still gives you trouble, you'll have to use the example to solve it or change the install location to somewhere you have user permissions by default (as I cannot do this for you).

zerophase commented on 2021-05-27 08:15 (UTC) (edited on 2021-05-30 08:41 (UTC) by zerophase)

Will update to 5.0 when it is released.

Latest Comments

« First ‹ Previous 1 .. 66 67 68 69 70 71 72 73 74 75 76 .. 82 Next › Last »

zerophase commented on 2017-04-21 10:38 (UTC)

@pepper_chico It's probably you running out of ram. If I'm recalling correctly using yaourt I needed about 40 gigs of ram (maybe even more) to build Unreal in ram. You can assign yaourt a temp directory on disk through the config file, and then you shouldn't have any issues with building from yaourt.

pepper_chico commented on 2017-04-16 14:58 (UTC)

Managed to build after some tries. It's better to clone the package and makepkg it yourself than rely on yaourt since build may fail at some point for a random reason but may success next.

pepper_chico commented on 2017-04-16 02:42 (UTC)

Error when downloading some file: ==> Starting prepare()... patching file /tmp/tmp.IkA8qeHQu6/yaourt-tmp-francisco/aur-unreal-engine/src/UnrealEngine/Engine/Build/BatchFiles/Linux/Setup.sh Hunk #1 succeeded at 156 (offset 3 lines). patching file /tmp/tmp.IkA8qeHQu6/yaourt-tmp-francisco/aur-unreal-engine/src/UnrealEngine/Engine/Source/Programs/UnrealBuildTool/Linux/LinuxToolChain.cs Hunk #1 succeeded at 387 (offset -6 lines). Registering git hooks... (this will override existing ones!) Github build Checking / downloading the latest archives Checking dependencies (excluding Win32, Win64, Mac, Android)... Updating dependencies: 0% (901/26282), 23.2/4067.6 MiB | 0.00 MiB/s... Failed to download 'http://cdn.unrealengine.com/dependencies/3151125-2ad56d47a97a48549bcd92c9e0cadff4/05fce820dac2128b1d1976aff55e0c4a49c49471': Can't read from pack stream (CorruptPackFileException)

zerophase commented on 2017-04-14 18:38 (UTC)

Manjaro isn't Arch. I have absolutely no problems installing this package on Arch.

Olorin.Narya commented on 2017-03-30 02:12 (UTC)

Hi, I got an error about file not found. only /Engine/Binaries/DotNET/IOS/IPhonePackager.exe I realize that could be the flags to wipe windows/mac related files, so I commented again this, and run yaourt. The package built and installed, but other errors of files not found were reported, like 30 (just guessing), but they didn't stop the building this time. Nvidia/bumblebee/intel i5 - Manjaro xfce4

CAPTNCAPS commented on 2017-03-16 17:16 (UTC)

Well I don't know what kinda fancy drivers you're using but last time I checked (which is just like a few months back) the nvidia drivers conflicted with all mesa packages... because the proprietary driver brings it's own OpenGL implementation! Maybe you could let me know how that's supposed to work, because I sure didn't find anything about Mesa + Proprietary anywhere! Anyway, this is getting offtopic. It was officially confirmed that Mesa 13+ is NOT supported, see the link. It is NOT an AMD issue.

zerophase commented on 2017-03-15 19:27 (UTC)

@CAPTNCAPS It still needs mesa installed for the opengl functionality it uses. It just doesn't use their implementation. Use the proprietary drivers, not nouveau.

CAPTNCAPS commented on 2017-03-13 12:52 (UTC)

@zerophase If you aer using Nvidias proprietary drivers, then you are not using Mesa, that's the whole point behind the proprietary driver. And yes I do have an Nvidia card to test with, but nouveau is so unstable it can't even run my Desktop (KDE) and as you said, the proprietary driver works.

zerophase commented on 2017-03-04 13:50 (UTC)

@CAPTNCAPS I think it's an AMD issue. I'm running Mesa 17, and Unreal uses opengl 4.3 without issue. I'm on an NVidia card using their proprietary drivers. Do you have an NVidia card to test with?

CAPTNCAPS commented on 2017-03-04 13:18 (UTC)

Just a note in case you don't know yet: Unreal Engine 4 does currently NOT SUPPORT MESA 13+! Officially confirmed: https://answers.unrealengine.com/questions/540613/ue4editor-not-starting-when-using-mesa-13.html

« First ‹ Previous 1 .. 66 67 68 69 70 71 72 73 74 75 76 .. 82 Next › Last »