Sorry guys, @EA_Darko and @holger1405 - will switch my OS lang to ENG and resend (probably tomorrow). Thanks for the initial
replies.Great support guys! To respond to your questions:
1. I saw the crashes with the audio device (it's the built-in soundchip, which I'm not using), but disabled that again and still no luck. I had a feeling it might be caused by my multiple audio devices connected/enabled as one of the config files mentions "Headphones" as the default audio device. I then turned off ALL audio devices (NVIDIA HD Audio, Oculus Rift Audio) to no avail; it's not a sound issue then.
2. Microsoft signed off the latest Fast Ring build as "RTM" a few days ago. The game didn't work on the latest stable RTM of Fall Creators Update, so I thought that switching to the new release might do something. Didn't.
3. I haven't tried the DPI 100%, good idea, but I've also got my DPI set to 200% on my MacBook 2016 and it's not causing any issue there ;( But I'll try tomorrow and let you know.
4. To respond to the last question: I did try windowed mode (see my post) and that didn't work.
By the way, in parallel I opened a support ticket yesterday and finally found someone knowledgeable to chat with. The support agent told me that in fact the developers have seen similar crashes on this forum (meaning they ARE looking at it luckily; at least occasionally) but can't really pinpoint it to one cause. He said the likeliest cause is this:
https://unreal-engine-issues.herokuapp.com/issue/UE-51650 - a bug in Unreal Engine which might be what's happening to a lot of people here. The original ticket mentions a few GPUs that are affected, mine (Titan Xp) wasn't listed.
There are five workarounds mentioned in this UE ticket:
But again, that was his and his teams GUESS, so they don't know. I tried the dx12 and opengl4 switch (no result; although opengl4 spits out a shader error).
My gut feeling: it's an UE bug, but given that there is no error code or anything, it's a bit of a stab in the dark.