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

Ah, I had actually made a typo with creating the folder you were missing

That aside, I corrected the sed command and fixed that typo

pkgrel=20 Errors:

sed -i "s/InstalledLocationPlaceholder/${_install_dir}/" "${pkgdir}/usr/share/applications/com.unrealengine.UE5Editor.desktop"

sed: -e expression #1, char 36: unknown option to `s'
==> ERROR: A failure occurred in package(). Aborting...
$

It is this line sed -i "s/InstalledLocationPlaceholder/${_install_dir}/" "${pkgdir}/usr/share/applications/com.unrealengine.UE5Editor.desktop".

BEFORE line that says install -Dm755 ../unreal-engine-5.sh "${pkgdir}/usr/bin/", I had to add mkdir -p "${pkgdir}/usr/bin/" for it to work, otherwise it fails too.

It should be fixed; I'm creating that folder sooner now

It shouldn't have been an issue in the first place in the code but I'm just making that folder as soon as possible now to get it out of the way

pkgrel=18 More errors:

==> Starting package()...
--2022-11-23 13:52:30--  https://raw.githubusercontent.com/EliverLara/candy-icons/master/LICENSE
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.109.133|:443... connected.
Saving to: ‘LICENSE’
LICENSE                                                    100%[========================================================================================================================================>]  34,33K  --.-KB/s    in 0,002s  
2022-11-23 13:52:31 (20,2 MB/s) - ‘LICENSE’ saved [35149/35149]


install: cannot create regular file '/home/juan/code/unreal-engine/pkg/unreal-engine/usr/bin/': Not a directory
==> ERROR: A failure occurred in package(). Aborting...
$

It is after wget'ing the LICENSE.

@juancarlospaco I wrote line 135 differently to prevent that error and reported the logic bug in bash upstream | Edit: it seems it's just how bash handles that line, rather than a bug

That aside,I see that you're having a similar issue as @coolitic with the file path being incorrect... I think I see where the logic is going wrong with it now; I hadn't considered a certain possibility before and I've taken a step to resolve the issue

What was happening was that ${srcdir} was being called twice even though it should not have been at all; this might just be how bash handles loop code, so I re-wrote how it's handled

pkgrel 17

Also error mv: cannot stat '/home/juan/code/unreal-engine/src/unreal-engine//home/juan/code/unreal-engine/src/unreal-engine/*': No such file or directory.

I am using git and makepkg on bash only, no AUR helpers.

@juancarlospaco What version is line 10 for you? Line 135 is considered valid in bash but I have seen an odd issue like this before, so I need to confirm

Some errors PKGBUILD: line 135: [: false: integer expression expected., it is the boolean conditional in the if.

${_install_dir} is explicitly defined in the PKGBUILD here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=unreal-engine&id=c866141788f5c52cd32ddfaea3e8f5f5ca57b3ae#n48

As you can clearly see in the package() function later, I never call this variable more than once, nor do I call any absolute path twice in the way you're experiencing. Again, the code's logic is sound; if you don't believe me, either ask someone else who knows bash and/or use https://shellcheck.net

I'm not usually one to adamantly defend my work when criticized, but I know what I do and don't do in the script, so I can't help you with an issue that isn't clearly defined in code. As such, you can try filing an Arch Linux bug (https://bugs.archlinux.org) and find out if it's actually a problem with makepkg, but there's absolutely nothing I can do for you if you can't prove there's a problem in the written logic of this file.

I can confirm that I personally am not using an AUR helper...

The reason I mentioned ${_install_dir} is because it looks like the script is adding the absolute path twice, and it's always used together w/ ${pkgdir}, which is why I asked if it may have been the culprit.