Arch Linux User Repository

I currently recommend building 5.6.1 over any version of 5.7 as this branch holds a notoriously broken Vulkan RHI implementation, leading to unexpected VK_ERROR_DEVICE_LOST crashes due to a race condition. Just modify pkgver on your end with the aformentioned version and you should be good to go.

A discussion here goes into detail about the issue, but no proper fix is currently planned by Epic.

A merge request has also been proposed here, but the fix itself was in the end apparently not very effective.

The Vulkan crashes were recently fixed in 5.8, check here.

You can still try on your own if you still insist on using 5.7.x, especially if you're motivated to fix this issue on your side. If so, don't hesitate to send a comment with your patch, I could add you as a contributor to this package if you are interested.

Reducing crashes can be done by doing the following two steps:

• Add these lines in DefaultEngine.ini (either in your project or the editor's installation dir, /opt/unreal-engine/Engine/Config/DefaultEngine.ini by default)

[/Script/Engine.RendererSettings]
r.Vulkan.WaitForIdleOnSubmit=1
r.Vulkan.EnablePipelineLRUCache=1

• Add these two lines as well in the editor's ConsoleVariables.ini file (/opt/unreal-engine/Engine/Config/ConsoleVariables.ini by default):

Slate.EnableToolTips=0
Slate.bAllowNotifications=0

Do note that using Wayland for Unreal Engine is currently not recommended as half of the UI interactions are broken. This is due to a recent upgrade to SDL3 which defaults the use of Wayland protocols over X11 when launching on a Wayland-based session.

You can work around this (or at least improve your experience) while still being on Wayland by opening a separate Xorg windowed server:

export DISPLAY=:1

Xwayland ${DISPLAY} -decorate -geometry 1920x1080 &
kwin_x11 &
unreal-engine 

You can, of course, replace kwin_x11 with your desktop environment window manager (GNOME is mutter for example).

@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).

Just decided to do that part a different way; it'll work now, sorry for the inconvenience

Give me a minute to figure this out; I'll update again when I have a solution

I tried recovering from line 194 w/ the latest changes, but I get this:

==> Starting package()...
install: omitting directory 'Engine'
==> ERROR: A failure occurred in package().
    Aborting...

@fhajii Sorry about that, I might've been half-asleep when I typed out line 194 and I had forgotten to correctly write that install statement; I just corrected the PKGBUILD to account for this

Your current state is recoverable but doing so might be a bit odd; from line 194 going forward in the PKGBUILD (reference the new file for doing this), you can run these same commands (almost) as-is (cd into unreal-engine and use ../pkg instead of ${pkgdir} instead) in your terminal and finish the file organization setup

However, you'll also need to compress the contents of your pkg folder into a pacman archive (.pkg.tar.zst) as well if you want the package to be installed by pacman

Otherwise, you can just move its contents to where you want it to be installed and it should work just fine as-is but doing that won't have it tracked by your package manager

If for whatever reason you can't adapt the rest of the script from line 194 going forward (in the event you don't understand it), I'd advise just having it re-compile overnight and have it automate it for you

Build 5.1.0-0 successful, but then this happens:

Saving file list to /opt/yay/unreal-engine/src/unreal-engine/Engine/Saved/BuildGraph/Make Installed Build Linux/Tag-Make Installed Build Linux.xml
Saving file list to /opt/yay/unreal-engine/src/unreal-engine/Engine/Saved/BuildGraph/Make Installed Build Linux/Tag-Installed Build Linux Files.xml

BUILD SUCCESSFUL
AutomationTool executed for 4h 13m 10s
AutomationTool exiting with ExitCode=0 (Success)
==> Entering fakeroot environment...
==> Starting package()...
install: missing destination file operand after '/opt/yay/unreal-engine/pkg/unreal-engine/opt/unreal-engine/Engine'
Try 'install --help' for more information.
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: unreal-engine

Building the package like this:

$ yay --builddir /opt/yay unreal-engine

Any way to fix this manually, without having to compile everything again? Thanks.

The PKGBUILD and script edits the .desktop file dynamically to solve that, which should be done after a working package is installed (make sure you don't already have one in your ~/.local/share/applications folder)

As for those configure errors you mentioned, I'll take care of that today after I get some sleep; for now, just remove the bits in the PKGBUILD where those 3 are mentioned and it should be fine

Some errors from line https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=unreal-engine#n160

Unknown argument 'WithWin32'
Unknown argument 'WithLumin'
Unknown argument 'WithHTML5'

This line https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=unreal-engine#n194 complains install: missing destination file operand after 'unreal-engine/pkg/unreal-engine/opt/unreal-engine/Engine'.

I got no icon on my system, I think its because the icon and .desktop still says unreal engine 4?.

I'll implement this when I have a moment tomorrow; thanks for letting me know

I'll set this up for UE4 package as well, while I'm at it

This package needs to add the dependency openssl-1.1 and steam, for "Turnkey" thats like an internal program to detect Clang targets to compile to, otherwise it only compiles to Linux x86_64 or nothing, meaning you can not compile your game into a binary.

Steam needs to be added as dependency too, because it searchs for Steam SDK and .so binaries at startup in a broken symlink at $HOME/.steampath, error says Warning: Cannot determine whether '/home/juan/.steampath' is a directory - stat() failed with errno=2 (No such file or directory), the symlink also needs to be created.

It also needs to run these:

ln -s $HOME/.steampath $HOME/.steam/bin
mkdir -p $HOME/.config/Epic/UnrealEngine/5.0/Intermediate/
mkdir -p $HOME/.cnfig/Epic/UnrealEngine/5.0/Intermediate/
chmod +x /opt/unreal-engine/Engine/Binaries/ThirdParty/Mono/Linux/bin/xbuild
chmod +x /opt/unreal-engine/Engine/Binaries/ThirdParty/Mono/Linux/bin/mcs
mkdir -p /opt/unreal-engine/Engine/Binaries/Android/

You can try yourself what I am saying by running /opt/unreal-engine/Engine/Build/BatchFiles/RunUAT.sh Turnkey -utf8output -WaitForUATMutex -command=VerifySdk -ReportFilename="$HOME/.cnfig/Epic/UnrealEngine/5.0/Intermediate/TurnkeyReport_0.log" -log="$HOME/.config/Epic/UnrealEngine/5.0/Intermediate/TurnkeyLog_0.log" -platform=all and /opt/unreal-engine/Engine/Build/BatchFiles/Linux/Build.sh -Mode=QueryTargets -Output="/opt/unreal-engine/Engine/Intermediate/TargetInfo.json" -progress.

@Neko-san I have /root and /home with separate partition.

so /home need 200-300 GB free space for compilation. (which i dont have this much free space left xD) and /root need 60+ GB free space for Installation directory (/opt/UE). right?

Can it actually being installed in /home partition tho like Unity Editor does?