Ok I tried the workaround. I’m guessing you are referring to the ConsoleVariables.ini that is located in User>Unreal Engine>Engine>Config folder. Unfortunately I am still having the problem.
I run 4.17 up to the point where it asks you which project to you want to open, since I only have projects prior to 4.17, it asks to create a copy etc etc. On the other hand I can create a new project. No matter what I’ve tried (with dektop quality), no matter which project I chose it crashes at about 91% into loading.
Please let me know If I edited the wrong ConsoleVariables.ini.
The ConsoleVariables.ini file that you edited is the correct one. I just wanted to confirm that after uncommenting that line (removing the semi-colon), no existing projects or new projects are successfully opening in the Editor. This may be a silly question, but did you make sure to save the change to the file before trying to open a project in the Editor?
No question is silly. I did ask myself that too. I will run some further test and see if I can get it to work. Maybe a whole system reboot (windows habits) will make it work. I’ll get back to you tomorrow as it’s getting late here.
I was unable to reproduce the crash that you described on a Mac. Is there a specific template that you are using when you create a new 4.17 project? I tried with both a Blank Blueprint project as well as a Basic Code project, and they both opened fine in the Editor.
I do not think that this would cause the issue that you are experiencing, but we are aware of an existing conflict between the Nvidia driver and Metal. Since your Mac has a Nvidia card (mine is using an AMD card), try opening the ConsoleVariables.ini file and remove the semi-colon ( at the beginning of the following line: ;r.Shaders.Optimize=0
This will disable Metal, but may allow you to open the project if that conflict is actually what is causing the crash that you are seeing. If it does resolve the crash, you will be able to continue working on your project at the expense of some rendering efficiency. Once the conflict is resolved, you can replace the semi-colon and regain the benefits of Metal.
If that does not resolve the issue, could you please provide any additional specific information you may have about your repro that may help us to reproduce it here?
I was able to run some tests on a MacBook that has an Nvidia card, and I was able to reproduce the crash that you described there, as well as verify that the workaround that I mentioned above does seem to provide a temporary resolution while the conflict between the Nvidia driver and Metal is investigated.
Hi
The first three times I opened a level it crashed.
After your response I tried it again for the call stack and everything went fine!
Probably your response was magic…
That is somewhat strange. I was able to get the exact same crash that you described on a Mac with an Nvidia card, and making that adjustment to the ConsoleVariables.ini file allowed me to open projects again.
Are you still seeing the same callstack when the crash occurs, now?
I am also experiencing the same problem, but I’m really new to unreal (haven’t even made a project yet) so I don’t know where to go to edit ConsoleVariables.ini file. Where would I be able to edit it?
So I tried various things. I cleaned up my Mac freeing up space plus all the maintenance scripts, I restarted the OS, tried to create new projects, tried to run the created projects off an external HDD but nothing. I even reinstalled 4.17. I also confirm that ConsoleVariables.ini is properly edited.
4.17 will just not run, I got up to 96% loading and that’s the highest it got. Let me know if I can provide you with any more information.
Sorry for the delayed answer. Well I got some strange results. 4.17 now sometimes reaches 96% and stays there for hours without crashing and without hanging. When it crashes I get the following :