When I try to start the game, it crashes immediately, before going to any splash screen (windows error 'wrath.exe has stopped working). In the user subfolder there's only a player.log and a player-prev.log,of which the full contents of the first are -

Mono path[0] = 'D:/Pathfinder Wrath of the Righteous/Wrath_Data/Managed'
Mono config path = 'D:/Pathfinder Wrath of the Righteous/MonoBleedingEdge/etc'
Initialize engine version: 2019.4.26f1 (e0392c6b2363)
[Subsystems] Discovering subsystems at path D:/Pathfinder Wrath of the Righteous/Wrath_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
d3d11: QueryInterface(IDXGIFactory5) failed (80004002).
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce GTX 1070 (ID=0x1b81)
Vendor:
VRAM: 8105 MB
Driver: 27.21.14.6627
Begin MonoManager ReloadAssembly
- Completed reload, in 0.100 seconds
D3D11 device created for Microsoft Media Foundation video decoding.
<RI> Initializing input.

<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 0.548186 ms


I'm running windows 10 on a intel i5 7600k cpu, a geforce 1070 gpu, with 32gb ram, and running the game off an NVME SSD.

There's no apparent change even with the update. I still get the same 'wrath.exe has stopped working' error. I should have specified that when I created the thread, I was on the then-current version, but this latest player.log is from 1.2.2a.

Mono path[0] = 'D:/Pathfinder Wrath of the Righteous/Wrath_Data/Managed'
Mono config path = 'D:/Pathfinder Wrath of the Righteous/MonoBleedingEdge/etc'
Initialize engine version: 2019.4.26f1 (e0392c6b2363)
[Subsystems] Discovering subsystems at path D:/Pathfinder Wrath of the Righteous/Wrath_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
d3d11: QueryInterface(IDXGIFactory5) failed (80004002).
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce GTX 1070 (ID=0x1b81)
Vendor:
VRAM: 8105 MB
Driver: 27.21.14.6627
Begin MonoManager ReloadAssembly
- Completed reload, in 0.082 seconds
D3D11 device created for Microsoft Media Foundation video decoding.
<RI> Initializing input.

<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 0.453131 ms

So, some experimenting found a not-really workaround. Normally, I keep my singleplayer games firewalled because they have no reason to need to access the internet, and this is no exception. However, when I relaxed that and allowed it to phone home, it started working.

This is not the first game I've come across that exhibits this behavior, and while this is still something that absolutely needs to be fixed, it is something more to go on.

This was still on 1.2.2a.

Putting up another addition to this, I just came back to test the new patch, hearing of some weird issues, and the game stalled on the loading screen for me as well, also it was asking to be allowed through my firewall.

I allowed the game through the firewall but it continues to refuse to load, simply stalling on the loading screen without crashing. Task Manager tells me the game is not responding until I click anywhere, at which point the 'not responding' marker disappears, but nothing changes and it still will not load.

Also, why is the game suddenly asking for firewall access? What is going on here?

I think your problem is different. When I had the game firewalled, I never even got to a loading screen - I saw it appear on my taskbar for a moment, then the error 'wrath.exe has stopped working'. Once I unfirewalled it, it started normaly - and I could refirewall afterwards as long as I didn't close the game.

...Though the game does seem extremely memory-hungry. I've left it running for a day and it's sitting at 28.53gb memory usage (out of 32gb installed)

The 1.3 update doesn't fix the crash-on-start problem. This is extremely disappointing, because reproducing this is about as simple as it gets. Firewall the game, it doesn't start. Unfirewall it, and it does. But more then that, there's no legitimate reason whatsoever for a noncompetetive singleplayer game like this to ever, EVER require phoning home.

Several patches on, now on 1.3.3. This problem is *still* not fixed.