There are a few extra questions I’d like to ask to help with understanding your problem. At what point does this failure occur? Is it while running Setup.sh or GenerateProjectFiles.sh or another step? Are you downloading/installing the engine to the desktop (or another folder on the desktop)? If so I would try moving the folder to another location on the computer, such as into the Documents folder, and try again.
My crash is not occuring while generating project files or executing setup, everything compiled fine with clang 3.5.
The crash occurs while launching the editor.
So I did a modification in the source code to be able to work :
In MeshUtilities.cpp, I modified CVarTriangleOrderOptimization to have a value of 2 (No triangle order optimization. (least efficient, debugging purposes only)).
Option 0 and 1 makes the editor crashes on load with SEGFAULT (signal 11).
0 being NvTriStrip
1 being ForSyth
Now, the editor works fine and I am currently building my first game. However, I know that my static meshes are not optimized so I may not get the performance I would have it they were.
I tried finding the bug with gdb, however, since I am not really comfortable with the code yet, I was not able to find anything except the function where the segfault occurs. (CacheOptimizeIndexBuffer)
The last console message before the segfault is :
Building static mesh EditorSphere…
Also, to answer you question my binaries are compiled in the Document folder :
AMD doesn’t even look like the same company they were years ago. I’ve been using ATI/AMD cards for 10 years and I’m giving up too. Their first drivers were amazing and some games ran faster on Linux than on Windows, but now I don’t even have drivers anymore (for an old HD3870) because they don’t compile at all on newer kernels. While I could install the oficial drivers, I always had problem with stuff that worked nicely on Nvidia cards but on mine didn’t even work.
At least Mesa is holding up, I’m clearing my huge gaming backlog and it’s still fine for low poly 3D modelling.
This year I’m going for a GTX 980.
You can work around the crash by editing ConsoleVariables.ini and adding a line
It is unclear what exactly is broken and at some later point we plan to look into that. The fact that it only happens with mesa drivers (on NVidia & AMD, but not Intel) may or may not be a red herring.
No; this only happens with certain Mesa drivers which we don’t normally use (we run NVidia binary + occasionally Intel and both those don’t have that problem). While we don’t rule out that we will try to repro that problem locally at some point to check why drivers are a factor here at all, we haven’t yet had time to do that.