I read somewhere that the gameoverlayrenderer.so errors are not to be worried about. The problem is clearly that Steam uses a mixture of system libraries in /usr/lib64 and Steam-bundled libraries. After a bit of research, I found out that openldap was not build with gnutls support. So I did a rebuild but I still get the same errors.

Next, I looked into libcurl-gnutls. I found out that by installing the libcurl-debian package, I got symlinks for libcurl-gnutls.so.4 and libcurl-nss.so.4 poiting to libcurl.so.4. However, these are located in /usr/lib64/debiancompat rather than /usr/lib64, so Steam cannot find them and still tries to use the bundled libraries.

I created new symlinks in /usr/lib64 and finally, Steam is now using the system libcurl-gnutls rather than the bundled version. But otherwise, still the same errors.

So, I found out that curl is build with openssl instead of gnutls. After setting CURL_SSL="gnutls" in my make.conf, this is the new output:

This time the splash screen comes up, the game appears to start but crashed with a box saying "Materials database was not correctly initialized. Please make sure that the global_*.mp files are present in Assets_XXX (platform specific) folder or in build Data folder."

I am not sure what to make of the above message, but it is clear that I solved some major problems by forcing the Steam-bundled libraries. The question is now: How do I setup Steam to use the bundled libraries by default?

Thanks in advance

Last edited by pvh1987 on Fri Sep 21, 2018 3:40 pm; edited 1 time in total

Somehow I managed to get the game started using the same command in the terminal, forcing the bundled libraries. I did not change anything. I am not sure why it suddenly works...

Furthermore, the next day, when I started Steam again, it updated itself. Now I can launch the game from within Steam as well and it appears to use the bundled libraries now. So I guess the issue is solved, at least for now